How a ShareFile to Nextcloud migration works in practice
If your ShareFile renewal, a pricing change or a residency requirement is forcing a decision, plan for this: the move is mainly a data copy plus an access rebuild, and it is usually led by the internal IT team with an implementation partner handling the Nextcloud build, integration and cutover checks. The copy is the easier half. Folders, file versions and timestamps have to land in Nextcloud with the right owners, and the access model has to be recreated for employees through groups, folder permissions and, where you use directory sync, the LDAP or Active Directory integration that Nextcloud documents. Start by inventorying which ShareFile content sits in the vendor's cloud and which sits in storage zones you control, because the copy route differs for each. Confirm with ShareFile which export options your contract and admin role allow, and measure total size and file counts per top-level folder before you pick a tool or a transfer window.
The effort and risk concentrate in the client-facing side. Internal users can be mapped to Nextcloud accounts in a few steps, but client share links, upload requests and portal workflows are the main points of friction. Those links do not carry over as-is, so you need a list of every active external share, its owner, its expiry and its password policy, then a decision for each: recreate it as a Nextcloud public share, convert it into a guest account, or retire it with a notice to the client. Agree the notice period, the cutover date and the fallback process for clients who upload files during the switch. Test a pilot group of clients end to end before you retire the old links, and confirm that the Nextcloud version you deploy is one you can keep upgrading, since major releases must be applied one at a time with a backup before each. When the copy is verified and the last share is moved, decommission the storage zones controller only after you have confirmed that no workflow still reads from it.
Which ShareFile capabilities map cleanly to Nextcloud and which need rework
This table maps common ShareFile capabilities to Nextcloud equivalents and marks each as clean, needs rework or gap. Treat the marks as starting points: confirm each feature against current Nextcloud documentation and your own pilot tests before committing, especially branding, portal customization and audit detail. The main takeaway is that folder structure and internal sharing usually move cleanly, while client portal branding and storage zone design need planning.
| Capability | Nextcloud equivalent | Status |
|---|---|---|
| Folder structure and team folders | Folders, group folders and shared spaces with per-folder permissions | Clean: map ShareFile folders to Nextcloud folders and confirm group folder limits in your version |
| Employee access via directory | LDAP or Active Directory user sync, with OpenID Connect or SAML as alternatives | Clean: confirm group mapping and login behavior in a pilot with your directory |
| Client shares and external links | Public share links with passwords, expiry and download limits | Needs rework: rebuild each client share and reissue links, since ShareFile links do not carry over |
| Upload requests from clients | File request shares that let outside users upload without an account | Needs rework: confirm the exact behavior you rely on, such as notifications and folder targeting |
| Browser document editing | Nextcloud Office with Collabora Online for .docx, .xlsx and .pptx | Needs rework: test co-authoring and format fidelity with your own templates |
| Audit logs and activity history | Activity app and server logs, with optional audit logging apps | Needs rework: confirm the log fields, retention and export your compliance evidence requires |
| Client portal branding | Theming and custom branding options, which vary by edition and app | Gap until verified: confirm branding and portal customization against current Nextcloud documentation and your tests |
| Customer-managed storage zones | Self-hosted primary storage on your own servers or object storage | Needs rework: no direct storage zone controller; plan storage backends and retire the Windows controller |
What data and integrations need to move and how to get them out
A ShareFile move touches more than files. Folder trees, version history, identities, client accounts and share links each follow a different path, and the integrations around them need their own owners. Inventory each category first, then decide what Nextcloud should hold and what stays in the source system until cutover.
Folder contents and structure
Start with a full inventory of the folders your teams and clients use, including storage zone locations if you run them. Record folder depth, file counts, total size and any files that ShareFile holds in ways a plain copy will miss. Confirm with Progress or your ShareFile administrator which bulk export or API options your tenant and storage zones provide, since the documented export paths differ by deployment. Plan the target layout in Nextcloud before copying, because folder moves are hard to reverse once users begin working in them.
Version history and metadata
Decide early whether prior file versions must come across or whether only current versions are needed for the migration. Confirm with your ShareFile administrator whether version history can be exported and in what form, because that answer determines whether history is copied, archived separately or left in the source. Record file timestamps, owners and any retention holds, since Nextcloud will assign new modification times and owners to copied files unless you handle them deliberately.
Employee identities and groups
Map which ShareFile users and groups must exist in Nextcloud and who owns each folder. If your directory is LDAP or Active Directory, Nextcloud's LDAP app lets directory users appear in Nextcloud and log in with their directory credentials, which avoids creating local accounts by hand. Nextcloud also documents OpenID Connect and SAML backends, so check which one matches your identity provider before you design group-based folder access.
Client accounts and portal access
Client users in ShareFile are often guest-style accounts with their own permissions and notification settings. List every external contact, the folders each can reach and whether they need a named login or only a link. Nextcloud handles external access through share links and guest accounts, so decide which clients should be recreated as accounts and which should only receive new links. Tell clients about the change before cutover, because their saved bookmarks and passwords will not carry over.
Share links and expiry settings
Export a list of active share links with their recipients, expiry dates, passwords and download limits, where your ShareFile tenant allows that export. Links cannot be moved as-is, so every active link must be reissued from Nextcloud and sent to its recipient. Prioritize links that a client or partner uses for regular deliveries, and close expired links rather than recreating them. Keep a log of who received each new link to support later access questions.
Email, SSO and line-of-business integrations
List every system that calls ShareFile or receives its notifications, including outbound email templates, SSO connections, scanners, document workflows and line-of-business applications with API connectors. Each integration needs a decision: point it at Nextcloud's WebDAV or sharing interfaces, rebuild it, or retire it. Confirm with your administrator which APIs and webhooks your ShareFile plan exposes, and test each replacement with a non-production folder before changing live workflows.
Migration sequence from inventory to decommission
This sequence moves ShareFile folders, permissions and client shares into Nextcloud in controlled stages, so each stage produces evidence that the next one can rely on. It ends with retired storage zones and a documented record of what moved and who can reach it.
Build the inventory register
List every ShareFile folder, storage zone, owner, employee group and external client share, and record the data volume, file count and retention requirement for each. Pull share and permission exports from the ShareFile admin console and confirm with the business owners which folders are still active. The output is an inventory register that assigns each folder a target path in Nextcloud, a named owner and a migrate, archive or delete decision. The step is done when every folder has a decision and an owner has signed it off.
Stand up the target Nextcloud environment
Deploy Nextcloud in your own infrastructure, choosing a supported Nextcloud 35 install method and the recommended database and PHP versions from the system requirements. Connect directory authentication through the LDAP app or an OpenID Connect or SAML backend, and confirm the server runs its own backup routine. Check the current release and end-of-life dates in the maintenance schedule before you choose the version. The output is a documented build record and a passing backup restore test.
Validate a pilot group
Choose a small group of employees and a few external clients whose folders are low risk and well understood. Copy their data, recreate their groups and shares in Nextcloud, and have each pilot user open, edit and upload files from the desktop client, mobile app and browser. Record every failed login, missing file or permission gap in an issue log. The output is a validated pilot report that lists the fixes made to the target design before any bulk copy begins.
Copy bulk data from ShareFile storage
Copy the approved folders from ShareFile-managed storage or your storage zones into Nextcloud, working from the inventory register in batches. Use a copy method that preserves file names, timestamps and folder structure, and run checksum comparisons on sample files where possible. Keep copy logs for each batch and do not modify source data during the copy window. The output is a reconciliation report that matches source and target file counts, sizes and exceptions for each folder.
Rebuild employee and client access
Recreate employee access through directory groups, and rebuild client access as Nextcloud guest accounts or share links with expiry dates and passwords set according to your policy. Confirm that every permission in the inventory has an equivalent in Nextcloud, and document any permission that does not map cleanly, such as a ShareFile feature that Nextcloud handles differently. Have each folder owner review their access list. The output is an approved access matrix that is signed by the owners and stored with the migration records.
Run the parallel period and cut over
Run ShareFile and Nextcloud side by side for the agreed period, with users told which system is authoritative for each folder. Track any new uploads or edits made in ShareFile during this window and copy the deltas into Nextcloud before the cutover. Switch each group to Nextcloud, set ShareFile to read-only for migrated folders, and monitor support requests closely. The output is a cutover log listing the date each folder moved and the final delta copy confirmation.
Reissue links and retire the storage zones controller
Send clients new Nextcloud links through a controlled communication, and confirm the old ShareFile links are disabled or expired. Once no active users depend on the storage zones controller, shut down the Windows and IIS controller, revoke its service accounts, and archive the final configuration and logs according to your retention rules. Keep ShareFile source data only as long as your retention policy requires. The output is a decommission record that confirms no active shares point to ShareFile.
Apply the upgrade rule after go-live
After go-live, plan every Nextcloud upgrade one major version at a time, because the upgrade documentation does not allow skipping major releases. Take a full backup before each upgrade, disable third-party apps until their compatibility is confirmed, and test in a staging copy first. Confirm your support route, whether community or an Enterprise subscription, before each upgrade window. The output is a written upgrade runbook and a recorded backup for each version step.
How to run ShareFile and Nextcloud in parallel and cut over safely
Decide the cutover model before the first folder moves: one writable system per folder at any moment. In practice that means choosing which folders stay writable in ShareFile during the parallel-run period and which are frozen for copying. Shared client folders are usually the hardest, because clients upload into them from outside your network. Keep those writable in ShareFile until their last migration pass, then switch them to read-only and announce the switch. Internal project folders can often move in waves by department. Record each decision in a single migration register with folder path, owner, wave number and the date its ShareFile permissions were last changed, so nobody has to reconstruct the state from memory.
Run delta copies on a schedule and reconcile them against the source rather than trusting the copy job's exit status. After each pass, compare file counts, sizes and modification times for each folder, and check that version history and deleted-item expectations match your policy. Confirm with your storage team how files are read out of ShareFile-managed storage or storage zones, since that path determines throughput and whether the copy runs from inside your network. Keep a list of files that fail or conflict, and resolve them by owner before the final pass. Tell users which system is authoritative for each folder in plain language, through a single notice that names the folders and the Nextcloud URL.
Pick the cutover date by the slowest dependency, not the easiest folder. Clients holding old ShareFile links need a communication window: send them the new link pattern, confirm which share types you will reissue, and agree a date after which old links stop working. Check your ShareFile plan terms and portal settings with your provider before you promise a date to clients, because link behavior at expiry is a configuration question you should confirm in your own tenant. Retire the storage zones controller only after you hold evidence that the data matches, that access logs for the migrated folders are retained in a location you control, and that the audit requirements your compliance team set are met. Keep the controller in read-only standby until an agreed review signs off, and remember that retiring it is a change to your control environment, not only a server decommission.
How the migration differs by size and starting point
When all files live in ShareFile's cloud, the extraction step is the main unknown. You download content through ShareFile's own clients or APIs, then upload it into Nextcloud folders that match the structure you choose. Nothing on your side needs to be decommissioned beyond the tenant itself, which makes this the simplest path, but it still depends on how much data you hold and how consistently it is organized.
- Extraction through ShareFile clients: Confirm which download methods your ShareFile plan and admin settings allow for bulk export, and test them on one folder before scaling up.
- Folder mapping: Decide whether Nextcloud folders mirror ShareFile folders one for one or are restructured by team or client. Write the mapping down before copying.
- Account matching: Map each ShareFile user to a Nextcloud account, ideally through LDAP or Active Directory, so that group memberships carry over.
- Client access: Rebuild client shares as Nextcloud public links or guest accounts. Existing ShareFile links will stop working, so clients need the new links.
- Decommissioning: Once data is verified, export audit history you need to keep and cancel the subscription at the end of its term.
Before you start, ask your ShareFile administrator for a current inventory of folders, users and active client links, and confirm what your contract allows you to export.
Where ShareFile storage zones run on your own servers, part of the data sits in infrastructure you already operate. The storage zones controller, typically a Windows Server host running IIS, is the component you must plan to retire. Extraction can read directly from the storage zone location, which avoids a slow download, but you must verify that the copied files are complete and that their paths and metadata are understood before you cut over.
- Direct copy from storage: Work with your storage team to copy files from the storage zone location, and do not edit or move files in the zone while copying.
- Integrity checks: Compare file counts and checksums between the zone and the Nextcloud target, because ShareFile stores content in its own internal layout.
- Controller dependency: Identify which users, applications and scripts still call the storage zones controller, and move them to Nextcloud before shutting it down.
- Infrastructure cleanup: Plan the removal of the IIS site, service accounts, certificates and the storage zone volume only after the verified cutover.
- Retention: Keep the storage zone in read-only form until your records requirements for old versions and deleted files are met.
Confirm with your ShareFile contact which storage zone components are still tied to the cloud control plane, since some functions may not run on premises.
Firms that run client portals depend on external users, branded workspaces, upload requests and per-client folders. Moving these means rebuilding the client experience, not only the files. Plan for an external user list, a clear way for clients to sign in or open links, and a process for reissuing every share, since links rarely carry over unchanged.
- External user inventory: List each client contact, the folders they reach, and whether they need a password, an expiry date or upload-only rights.
- Upload requests: Recreate request workflows in Nextcloud with file request links, and test that clients can upload without seeing other clients' folders.
- Client communication: Send new links and sign-in instructions in advance so clients do not lose access during the cutover.
- Guest accounts: Decide where guest accounts are needed and whether they should be tied to your identity provider.
- Verification: Test access from a client's point of view for each portal before you retire ShareFile.
Ask the team that manages client relationships to confirm which portals are contractually or operationally critical, since those set the order of the cutover.
Where ShareFile is used mainly to share files between employees, the permission model is the main task. Internal folders usually map to groups and teams, so the work centers on rebuilding those groups and their rights in Nextcloud, then checking that the data was copied with the right owners and sharing settings. Client shares are few and can be handled as a short follow-on task.
- Group-based permissions: Rebuild team folders in Nextcloud and assign rights through groups synced from your directory, rather than user by user.
- Ownership clean-up: Reassign orphaned files from former employees to a team owner before copying.
- Sync clients: Move desktop and mobile users to the Nextcloud client and confirm that local sync folders do not overlap with the old ShareFile drives.
- Short cutover window: Because internal users depend on the new location, agree a cutover date with each department and communicate the change in advance.
- Decommissioning: Remove ShareFile access once internal teams confirm their folders are complete.
Confirm with department owners which folders are still actively used, since archiving unused data first can shorten the copy and verification work.
What drives migration cost and duration
This table lists the main cost components and drivers for moving from ShareFile to Nextcloud, separating one-time migration work from recurring infrastructure and operations. Use it to see which items your own environment will push up or down before asking for a written scope. The main takeaway is that data volume, share link count and identity complexity usually decide the effort, while the Enterprise subscription is a separate, optional decision.
| Driver or component | Why it changes cost or effort | How to keep it down |
|---|---|---|
| Total data volume and file count | Copying from storage zones or cloud-managed storage takes longer as volume and file count grow, and deduplication and verification add checks per file. | Clean up stale folders before export, archive inactive projects separately and confirm which libraries must move at all. |
| Number of users and external clients | Each employee account, guest account and client portal user needs a mapped identity and a folder permission set to test. | Group clients by engagement, migrate in waves and retire inactive client accounts before the move. |
| Share links to reissue | Every active link in ShareFile must be recreated as a Nextcloud share with the right expiry, password and recipient, and clients must be told the new URL. | Export a link inventory, drop expired links and agree a single notification template with the client-facing team. |
| Identity integration complexity | Connecting Nextcloud to Active Directory through the LDAP app, or to OpenID Connect or SAML, adds design, testing and group mapping work. | Document existing groups, decide which directory is authoritative and test one pilot group before wider rollout. |
| Storage zone count | Each storage zone or on-premises location is a separate source to inventory, copy, verify and detach. | Map zones to target Nextcloud paths or external storage mounts early so each source has one owner and one checklist. |
| Custom portal workflows | Upload requests, client onboarding forms and custom branding in ShareFile must be rebuilt with Nextcloud features or add-on apps, which vary in fit. | List each workflow actually used, drop unused ones and confirm which apps are compatible with your target version. |
| Compliance evidence needs | Assessors may ask for access logs, change records, migration sign-off and retention evidence, which adds documentation and test time. | Agree the evidence list before work starts and keep the migration log, checksum reports and approvals as they are produced. |
| Nextcloud Enterprise subscription (optional) | Enterprise tiers are sold per user per year with a 100-user minimum, with list prices starting at 71.29 euros for Standard, 104.99 euros for Premium and 204.75 euros for the top tier, per Nextcloud's pricing page, with lower rates from 200 users. | Compare community support with the required response times, confirm the user count against the minimum and ask for written tier pricing in the quote. |
| Ongoing operations | Servers, storage, backups, monthly maintenance and the one-major-version-at-a-time upgrade path recur every year and depend on staff time. | Budget for the upgrade cadence, automate backups and test restores, and assign a named owner for patching. |
What usually goes wrong and how to prevent it
Most ShareFile to Nextcloud problems come from three places: the links and recipients people rely on daily, the permissions and copies that move with the files, and the upgrade and retirement steps that happen after go-live. Each card below names one failure, why it matters for this migration, and the check that prevents it.
Broken client links and missed recipients
Every ShareFile link a client holds stops working when the old share is retired, and reissuing links by hand tends to miss clients who only ever received a link from a colleague. Build a list of active shares and their recipients from ShareFile's reporting before cutover, and map each one to a Nextcloud share, guest account or upload request. Test each client path with a real external account before you announce the change. Make sure the old links redirect to a page that explains where to go next, so clients do not assume the files were lost.
Permission drift from hand-built groups
When teams recreate folder access by hand in Nextcloud, people end up with rights they never had in ShareFile or lose rights they need. Export the current ShareFile user and group memberships, then define Nextcloud groups from that export, ideally synced from your directory through the LDAP app. Compare effective access on a sample of folders for each department before users receive their accounts. Record who approved each mapping so the change has a trail.
Incomplete copies from storage zones
Files held in ShareFile storage zones or ShareFile-managed storage can be copied with gaps: long paths, unsupported characters, locked files, or versions that were never exported. Run the copy from an account with full read rights, then compare file counts and total sizes per folder against the source. Keep a list of anything skipped and resolve it before the controller is switched off. A copy you have not verified is not a migration.
Third-party apps breaking upgrades
Nextcloud requires that third-party apps are disabled until they are confirmed compatible with the new release, and an app left enabled can block or break an upgrade. Inventory every installed app during the build, record its version, and confirm compatibility with each target major version before scheduling the change. Keep a staging instance that mirrors production so you can test each upgrade there first. Back up the database, data directory and configuration before every step.
Skipping major Nextcloud versions
Nextcloud does not allow skipping major releases during an upgrade, so an instance built on an older release must be moved forward one major version at a time. Teams that delay upgrades for months can find they need several sequential steps, each with its own testing window. Choose a release line that is still supported at go-live and set a calendar for the next upgrade before the migration closes. Confirm the current support windows in Nextcloud's release schedule rather than relying on memory.
Retiring the controller before keeping evidence
Switching off the ShareFile storage zones controller before exporting audit logs, sharing records and access reports removes the evidence an auditor may ask for later. Decide which logs, share histories and permission exports your compliance program needs, and archive them in a read-only location with a retention period set by your policy. Ask your assessor which artifacts they expect for the migration period. Only decommission the controller after that archive has been checked and signed off by the data owner.
Questions buyers ask before moving from ShareFile to Nextcloud
What drives the cost of moving from ShareFile to Nextcloud?
The main drivers are the volume and location of data, how many folders carry custom permissions, how many client shares and portals must be rebuilt, and how much integration work sits around the move. Nextcloud Server is free to self-host under the AGPL, so the recurring costs are infrastructure, storage, staff time for operations and an optional Enterprise subscription. Migration labor is a one-time cost. Ask any implementation partner for a quote built from a written scope that lists data volumes, storage zones, identity sources and client share counts, since those items move the price more than anything else.
How long does a ShareFile to Nextcloud migration take?
The timeline depends on data volume, the number of storage zones and how many permission structures and client shares must be recreated, not on a fixed formula. A pilot with one team and one client portal usually shows the real pace before the full project is scheduled. Plan around your own measurements: time a sample copy from your storage zones or ShareFile-managed storage, then multiply by the full size and add time for permission review, user testing and a rollback window. Ask any partner to state their assumptions and the milestones they will commit to in writing.
What does our internal team need to provide during the migration?
Your team needs to provide a current inventory of folders, owners and permissions, a list of active client shares and upload requests, the identity source that Nextcloud should use, and named owners who can approve access decisions. You also need access to the ShareFile administrator account, to any storage zones and to the servers where Nextcloud will run. Without those inputs, the team will spend time discovering scope during the project. Confirm with your own security and records teams which data may move and which must stay put before the first copy begins.
Can our own IT team migrate from ShareFile to Nextcloud without a partner?
A capable internal team can run a small migration, particularly for a few hundred gigabytes and a limited number of shares, if it has Linux, PHP, database and web server skills. Larger estates with storage zones, complex permissions, client portals and compliance evidence needs usually benefit from an outside implementer. Nextcloud upgrades must move one major version at a time and require a backup before each one, so plan for that operational work even after the migration is complete. Decide based on the skills you have today and the staff hours you can commit.
How are client share links handled when we move to Nextcloud?
Client share links in ShareFile do not carry over as the same URLs, so each active share must be recreated in Nextcloud and the new link sent to the client. Plan a cutover window, a notice to clients and a short overlap period where both systems stay available. Confirm with Nextcloud how public share link passwords, expiry dates and upload-only folders map to your current settings, and test each pattern with a sample client before switching. Keep the ShareFile audit records for the required retention period.
What does Nextcloud Enterprise add beyond the free community edition?
Nextcloud Server is free to self-host, while Nextcloud GmbH sells Standard, Premium and Ultimate subscriptions. According to the Nextcloud pricing page, Standard includes one-year maintenance, Premium adds a maintenance lifecycle of five or more years, extended support hours and clustered instance support, and Ultimate adds support up to 24/7 with response times down to one hour. Enterprise tiers have a 100-user minimum, and list prices start at 71.29, 104.99 and 204.75 euros per user per year for 100 or more users. Confirm current pricing and included features directly with Nextcloud before budgeting.
Which Nextcloud version should we plan to run after the migration?
Plan for a version that is still inside its support window for the full life of the project, and confirm the schedule before you install. According to the Nextcloud maintenance and release schedule, Nextcloud 35 was released on 16 September 2026 and ends in September 2027, while Nextcloud 34 is supported until June 2027. Nextcloud does not allow skipping major releases during upgrades, so you will need a repeatable upgrade routine. Check the system requirements for database, PHP and web server versions before selecting a build.
When a fixed-scope migration makes sense before the renewal date
Start a fixed-scope migration before the renewal date when you can answer three questions with evidence: what data sits in ShareFile and its storage zones, who depends on the client portal, and which integrations would break on cutover. If those answers are still guesses, waiting for the renewal conversation is usually the wrong move, because the renewal will be priced against the vendor's view of your usage rather than your plan. Treat the renewal date as the deadline for a decision, not necessarily for a finished cutover. A common, sensible position is to sign a short extension or a shorter term while the migration runs in parallel, but confirm with ShareFile whether that is available and on what terms before you rely on it.
Measure the inventory before you estimate anything. For each top-level folder, record its size, file count, owner, and whether it lives in ShareFile cloud storage or in a storage zone you operate. Pull the list of active client shares, upload requests and guest accounts, including their expiry settings and the email addresses tied to them, because those are the objects clients will notice when they stop working. Export or review audit logs for the last several months to find which folders are actually used. Note every integration that calls the ShareFile API, every Active Directory group that drives access, and every Windows server running the storage zones controller. Confirm the version and file-type limits you need from your own environment, since the controller and Nextcloud's file handling can differ on large files and special characters. A written scope should name each folder or library that moves, the target path in Nextcloud, and the group or user that will hold each permission, with the source permission recorded beside it. It should list the internal users and external clients by cohort, the channel used to tell each cohort about new links, and the date on which old links stop resolving. It should name every integration, state whether it is rebuilt, redirected or retired, and assign an owner. Acceptance tests should be specific: checksums or file counts matched per folder, a sample of documents opened and edited in Nextcloud Office, a client able to upload through a reissued request, and a restore test from the Nextcloud backup. Agree the sign-off authority in writing before work starts.
How DeployOpen scopes, runs and supports the migration
DeployOpen plans, implements, customizes, integrates, hardens, backs up, documents and supports self-hosted Nextcloud inside your own infrastructure, so the ShareFile move is handled as a defined project. Engagements are fixed-scope, with deliverables and timelines agreed in writing before any work starts.
How we scope
- Inventory ShareFile folders, storage zones, client portals and active share links with you before any data moves
- Agree in writing which employee accounts, client guest accounts and retired storage zones are in scope
- Define the target Nextcloud deployment, identity integration and acceptance criteria for the cutover
How we build
- Build the Nextcloud environment in your cloud account, data center or air-gapped network with your chosen database and PHP versions
- Copy data out of ShareFile-managed storage and storage zones, then verify file counts, sizes and folder structure
- Rebuild folder permissions and client access in Nextcloud, and test them with representative employee and client accounts
How we hand over
- Document the target architecture, folder and permission model, and the steps used to reissue client share links
- Provide a cutover runbook covering user communication, link replacement and the decommissioning of the storage zones controller
- Hand over administration notes, backup procedures and upgrade steps so your team can run Nextcloud without us
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer after handover, scoped separately in writing
- Plan each Nextcloud major upgrade one version at a time, with backups taken before every upgrade
- Confirm with you which Enterprise subscription tier, if any, your support needs call for before go-live
