Migrate from OneDrive to Nextcloud: what the move involves
Moving from OneDrive to a self-hosted Nextcloud is a documented per-user file import, plus three decisions that the import cannot make for you: how people sign in, which sharing is preserved, and which editor handles Office documents. The effort depends mainly on data volume, user count and how much sharing must be preserved. DeployOpen plans and runs this work inside your own infrastructure, and the figures and effort are set in a written scope agreed before work starts, not on this page. Each OneDrive library belongs to an individual account, so the import runs user by user, and the OneDrive integration app is the documented path for that work. Before the first pilot, confirm with the app's current documentation which Microsoft Entra app registration, permissions and consent steps it requires in your tenant, and who in your organization is allowed to grant them. Those approvals often take longer than the copy itself, so raise them early in the scope.
Identity is the decision that shapes every later step. Nextcloud can read users from LDAP or Active Directory and let them log in with directory credentials, and it documents OpenID Connect and SAML as user authentication backends. Choose the source of truth before the import starts, then check that the attribute users log in with matches the account identity used during migration. If a Microsoft 365 email address does not match the directory attribute, users may land in duplicate accounts, and the files in those accounts will look missing. Decide also how migrated accounts map to existing Nextcloud users, including any accounts created during a pilot. Ask the team delivering the work to list every mapping rule in writing so it can be reviewed by the identity owner and the data owners.
Sharing is where most of the unplanned work hides. A OneDrive library can contain links shared outside the organization, folders shared with named colleagues, and files that a former employee owns. Build an inventory of shared items per user before the cutover, and confirm which shares, group permissions and external links the app carries across and which must be recreated by hand. Decide who owns shared content after the move, and whether shared project folders should become group folders in Nextcloud instead of copies in individual accounts. Keep the inventory with the cutover plan. It gives the business owners a list they can sign off, and it gives the engineers a measure of how much re-sharing the first wave of users will need.
Office editing changes the user experience more than the file copy does. People who opened Word, Excel or PowerPoint files in a browser on OneDrive will expect a similar editor in Nextcloud. The main options are Nextcloud Office, which the official All-in-One installation can include, and Collabora Online, which connects to Nextcloud as a WOPI host. Each needs its own hosting, routing and sizing decisions, and both should be tested with the document types your teams actually use, including macros and large spreadsheets. When you request a quote, ask for the editor choice, the expected number of concurrent editing sessions, the pilot group size, the cutover waves, and the verification steps used to confirm that files, metadata and shares arrived intact.
What maps cleanly from OneDrive to Nextcloud and what does not
This table compares each OneDrive capability with its Nextcloud counterpart and marks whether the migration carries it, requires manual recreation, or needs a decision. Confirm each behavior against the OneDrive app's own documentation and your Microsoft 365 tenant settings before the pilot. The main takeaway is that folders and file content are the parts most likely to move with the import, while sharing, co-authoring and retention need planning.
| OneDrive capability | Nextcloud equivalent | Migration notes |
|---|---|---|
| Personal folders and file hierarchy | User Files area with nested folders | Carried by import: folder structure and file content move per user. Confirm name length and character limits in both systems. |
| File versions | File versions kept per file | Decision: confirm whether the import brings OneDrive version history. Decide whether older versions go to an archive folder. |
| Sharing with internal users | Shares with users and groups | Must be recreated: permissions should not be assumed to transfer. Export a share list before cutover and check group membership first. |
| External sharing links | Public share links with optional password and expiry | Must be recreated: new links are issued, so each recipient needs the new URL. Decide how and when owners notify recipients. |
| Co-authoring in Office files | Nextcloud Office with Collabora Online, or Office clients through WebDAV | Decision: choose the editor before migration. Test co-editing with pilot users and confirm supported formats in each editor's documentation. |
| Retention and deleted items | Trash bin with configured retention | Decision: OneDrive recycle bin and retention policies do not map one-to-one. Set Nextcloud trash and backup retention explicitly with your tenant admin. |
| Modified dates and owners | File modification time and file owner | Confirm whether the import keeps original modified timestamps. Owners may default to the importing account, so plan ownership reassignment. |
How the OneDrive integration app brings files across
The OneDrive integration app copies files from each user's OneDrive into that user's Nextcloud files, one account at a time. Treat the import as a series of user batches. Each batch needs its own sign-in, its own consent state and its own verification window, so the administrator decides which accounts are in scope and when each batch runs. Nothing moves until the Microsoft side grants the app permission to read files and the Nextcloud side is configured to call Microsoft on the user's behalf. Plan the batches before the first run, because they determine the maintenance windows, the support load and the order in which users lose access to their old storage.
On the Microsoft side, create an app registration in Microsoft Entra ID for the Nextcloud instance. Record the client identifier and the credential the app requires, set the redirect address exactly as the app documentation specifies, and request only the file permissions the import needs. Then decide who grants consent. A tenant administrator can approve the permissions once for every account in scope, which suits a bulk migration, but that administrator must understand what the grant allows. Per-user consent places the decision with each person and slows the batch. Confirm the exact permission names, the consent flow, and which OneDrive account types the app supports (work or school accounts, personal accounts, or both) against the app's documentation and Microsoft's current guidance. This page does not supply those details.
Each user's account must be able to sign in to Microsoft and read its own OneDrive content through the granted permissions. During the import the app reads the folder tree, file contents and the metadata it supports. Items it cannot read need a plan before cutover. These include files protected by restrictive sensitivity labels, locked or checked-out files, and items in folders shared with the user that the user does not own. Ask the app's maintainers how shared items, previous file versions, and file names containing characters Nextcloud rejects are handled. Also confirm whether sharing links are carried across. Users should know which of their items will need manual attention so they can review the results on their first day in Nextcloud.
Microsoft applies throttling to its APIs, and the app may impose its own maximum file sizes or batch limits. Neither figure is supplied here. Ask the app's maintainers for the documented values, check Microsoft's current service limits for the account types in scope, and size each batch and maintenance window from those numbers. Run a test import with a pilot user whose folder structure resembles the largest accounts, then measure throughput in your own environment. Check that each user's Nextcloud storage quota can hold the imported data plus the existing files, and that the Nextcloud server has enough free disk space for temporary copies during the transfer.
Which documented import paths move OneDrive files
OneDrive files can reach Nextcloud through three documented routes, each suited to a different scale and level of user involvement. The right choice depends on how many people are moving, whether each person can copy their own files, and whether the team needs a transfer it can repeat. Read each card for what it carries and what to confirm before committing a migration wave.
Per-user imports with the integration app
The Nextcloud OneDrive integration app connects a Nextcloud account to a user's OneDrive so that files can be imported one user at a time. It suits a staged cutover in which the team moves a small pilot group first, checks results, and then opens the remaining accounts. Confirm that the app version matches your Nextcloud major version, which Microsoft 365 permissions the connecting user needs, how folder structure and file names are handled, and how the import behaves when it is interrupted.
Sync clients from a local folder
The Nextcloud desktop and mobile sync clients can copy files from a local OneDrive sync folder into Nextcloud when each user chooses which folders to move. This suits users with moderate amounts of data who already keep a complete local copy. Files that exist only as online placeholders in the OneDrive folder will not be copied until they are downloaded locally, and sharing settings and version history should be assumed not to move. Confirm that each local copy is complete and current, and that every user knows the target location in Nextcloud before copying starts.
WebDAV for bulk transfers
Nextcloud exposes files through its WebDAV interface, so an administrator or the migration team can copy content in bulk, either by hand with a WebDAV-capable client or with a script they write and test themselves. This route suits large volumes, service-owned content and cases where per-user imports are impractical. Scripts built on WebDAV are your code, so the team owns retries, error logging and checksum verification. Confirm the user quotas and upload limits on your server, the account that will own imported files, and how each copy will be verified against the source.
What no path preserves
Whichever route you choose, plan for sharing links, Microsoft 365 permissions, co-authoring state and version history as separate work items. None of them should be assumed to move automatically with the file bytes. Use the reporting your Microsoft 365 tenant provides to inventory shared OneDrive content before the first import, then decide which links will be recreated in Nextcloud and which recipients need notice. Confirm what each documented path carries, and schedule the recreation work before cutover, since recipients usually notice missing links first.
How the parallel run and cutover are sequenced
The sequence moves users in controlled groups so each stage produces a named output and a go or no-go decision, and OneDrive stays available as a fallback until the stabilization period in the scope has passed. Each step closes with the output you receive and the decision you need to make.
Inventory users, data and sharing
DeployOpen works with your Microsoft 365 administrators to list every account holding OneDrive content, the size and file types of each library, internal and external sharing links, and any group or retention settings that affect who can see what. The inventory also proposes the pilot group and the later migration waves. You receive a written inventory with a per-user list, sharing exceptions and open questions. You decide which users and content are in scope, which content stays behind, and who approves the wave plan.
Stand up the target instance
DeployOpen builds the target Nextcloud instance in infrastructure you control on a current supported release. Confirm the release at the time of planning, because supported versions and end-of-life dates follow Nextcloud's published maintenance schedule. The build covers the database, PHP, web server, storage, and the identity integration you chose, followed by configuring the OneDrive integration app and a test import of sample files. You receive a documented build with versions, configuration and a test record. You decide the sign-in method for users and where the data is stored.
Pilot with a small user group
A small group of users, selected to include different sharing patterns and at least one owner of a shared library, imports into Nextcloud and works there for the pilot period agreed in the scope. DeployOpen records failed or skipped files, broken shares, sync client errors and how the pilot devices behave against the new instance. Fixes are applied and retested before the next group. You receive a pilot report listing each issue, its cause and its resolution. You decide whether the import results and the process for recreating shares are acceptable before any wider wave begins.
Import while both systems run
During the parallel run, content for each wave is imported from OneDrive while the source stays live and users keep working there. Because files keep changing, DeployOpen repeats the import to pick up edits made after the first pass, provided the integration app supports this in the version you deploy, which you should confirm during the pilot. Each pass ends with a reconciliation of file counts, sizes and any checksums the tooling exposes. You receive a reconciliation report per wave. You decide how long each group runs in parallel and what gap between sources is acceptable before cutover.
Cut over one group at a time
Users move in the waves defined in the inventory, one group at a time. For each group, DeployOpen runs a final import pass to capture recent changes, confirms the final reconciliation, redirects sync clients and shared links to Nextcloud, and sends users the instructions you approve. Users who need extra help receive it during the window. You receive a cutover record for each group that lists the reconciliation result and any exceptions. You decide the go or no-go for each group against the exit criteria set in the pilot.
Keep OneDrive as fallback
After the final wave, OneDrive remains available for the stabilization period defined in the scope, and users are directed to Nextcloud for all new work. DeployOpen monitors sync errors, support tickets, backup jobs and access activity, and resolves issues found during that time. Any content that needs a business decision is listed separately. You receive a stabilization report with open items. You decide when stabilization is complete and approve the start of decommissioning.
Decommission OneDrive after sign-off
After you approve the end of stabilization, DeployOpen removes user access to OneDrive, revokes the integration app's permissions, and carries out the data retention or disposal steps your policy requires. The team confirms that no sync clients, shares or scheduled jobs still point to OneDrive and keeps the final reconciliation and backup records. You receive a decommissioning record that lists each step and its verification. You decide how long exported records are retained and who approves their deletion.
Deciding identity and Office editing before the migration starts
Identity has to be settled before the first import runs, because files land under whichever Nextcloud account the import targets. A file that arrives under the wrong user is hard to move later without breaking shares, quota history and the owner's view of their own folders. Before the pilot, decide which identity source Nextcloud will use for each person in scope, then produce a written mapping from each OneDrive account to the Nextcloud username that will receive its files. Include the exceptions in that mapping: former staff whose files will be archived, shared team folders with no single owner, and service accounts that should not own personal storage. The mapping is the reference the import will be checked against, so the data owners should sign it off, not only IT.
If your users already sit in Active Directory or another LDAP directory, the documented LDAP user backend is the usual starting point. Nextcloud's LDAP app lets directory users appear in Nextcloud and log in with their directory credentials, so migrated users do not need a second password. Confirm with your directory team which attribute will serve as the Nextcloud username, how group membership maps to the Nextcloud groups used for sharing and quotas, and whether disabled directory accounts should be disabled in Nextcloud on the next sync. These choices shape the folder paths the import creates, so changing them after the import means renaming or re-owning data. Test the bind account with read-only rights before the pilot begins.
If the organization already runs an identity provider or federation service for Microsoft 365 and other applications, the documented OpenID Connect and SAML user authentication backends may be the better fit. Both let users sign in through the identity provider, while Nextcloud still needs a stable user identifier and a way to assign groups from the claims or assertions it receives. The right backend depends on what the organization already runs, who owns that identity provider, and whether it can supply the attributes Nextcloud needs. Ask the identity and security owners to document the chosen backend, the session lifetime and how offboarding removes access, because offboarding determines who can still open the files the import has placed.
Office editing is a separate decision with its own support and cost questions. Migrated Word, Excel and PowerPoint files can be edited in the browser only when an office editing service is connected to Nextcloud. Two routes are commonly considered. The first is a separate document server that Nextcloud calls through the WOPI protocol, such as Collabora Online, which DeployOpen can deploy in infrastructure you control. The second is Nextcloud's own office options, which the All-in-One installation can include as an optional component. Choose the route before the pilot, because it changes the hostnames, certificates, sizing and update cadence you must plan for. Confirm the current licensing and support model directly with the vendor, including any Enterprise terms, since these can change and determine who you call when editing fails.
Before the pilot, write down three decisions: the identity backend, the account mapping rules and the Office editing route, each with a named owner. Then test one imported account from end to end. Sign in with the intended credentials, open a migrated Office file, and confirm the file appears under the correct owner with the expected sharing. A pilot that passes only with an administrator account does not prove the mapping works for everyone else. Treat a failed login or a file under the wrong owner as a reason to pause the full import until the mapping or the backend configuration is corrected.
What drives the cost and duration of a OneDrive import
This table lists the drivers that change the cost and duration of a OneDrive to Nextcloud import, why each one changes the work, and what to request in a written quote. Read the one-time rows for planning, import and cutover effort, and the recurring rows for hosting, maintenance, upgrades and support tier. The main takeaway is that file volume is only one input, and sharing, identity, editing and the number of rounds often set the schedule.
| Driver | One-time or recurring | Why it changes the effort | What to ask for in a quote |
|---|---|---|---|
| Total data volume and file count | One-time (import) | Transfer time and error handling grow with bytes and object count, and many small files cost more to process than a few large ones. | A file and size inventory from the OneDrive tenant, the import method and the throughput assumptions used. |
| Users and shared libraries | One-time (import) | Each account and each shared library needs its own mapping, import run and verification step. | Counts of user accounts, personal drives and shared libraries, and the mapping approach for each. |
| Sharing to recreate | One-time (cutover) | Sharing must be reviewed and rebuilt in Nextcloud, and the import app may not migrate every share type. | Which share types the import covers, how external links are handled, and who approves changes. |
| Identity integration | One-time (build), recurring if kept | Matching OneDrive users to Nextcloud accounts depends on whether LDAP, OpenID Connect or SAML is used, and each path adds configuration and testing. | The authentication backend to be built, user matching rules, and test cases for sign-in and account mapping. |
| Office editing requirements | One-time (build), recurring (hosting) | Browser editing needs a separate document server, such as Nextcloud Office or Collabora Online, that is sized and updated apart from the file import. | Editor choice, hosting location, sizing assumptions, and who maintains the editor service after handover. |
| Pilot and parallel-run rounds | One-time (cutover) | Each round repeats import, comparison and user checks, and parallel running keeps two file stores active until users switch. | The number of pilot rounds, the parallel-run length, and the acceptance checks that close each round. |
| User communication and training | One-time (cutover) | Users need to know where files now live, how sync clients change, and how shares behave after the move. | The communication plan, training materials, session count per user group, and help desk support during cutover. |
| Hosting and maintenance model | Recurring | Servers, databases, backups and monitoring carry ongoing effort, whether your team or a partner runs them. | Who operates the instance, the backup scope, the monitoring scope, and the recurring responsibilities in writing. |
| Upgrades and support tier | Recurring | Upgrades cannot skip major releases, and Enterprise tiers differ in maintenance length and support hours, according to Nextcloud's pricing page. | The upgrade cadence, supported major versions, the Enterprise tier if chosen, and the response terms in writing. |
What usually goes wrong in a OneDrive to Nextcloud move
Most failed OneDrive moves trace back to a few decisions made too late, not to the import itself. The cards below cover six patterns that recur in these projects, and each names the decision to settle before any file moves and the role that should own it. Work through them as a checklist before the first import.
Sharing links and permissions
OneDrive sharing links, guest access and inherited permissions do not map one to one onto Nextcloud shares, so links that teams rely on can stop working after cutover. Before import, decide which share types will be recreated, which external guests keep access and who approves each recreated share. Data owners of each folder should confirm the list, and the migration lead should test a sample link from outside the company before the cutover date. Confirm exactly what the OneDrive integration app transfers, since sharing metadata may not come across.
Divergent copies during parallel running
During a parallel run, people who keep editing in OneDrive either create files that never reach Nextcloud or make edits in both places that conflict. Before import, decide whether OneDrive becomes read-only during the parallel period, for which folders, and set a freeze date after which the old location stops receiving changes. The business sponsor owns this decision and must communicate it to each team, because a technical lock alone rarely stops people from saving to the old location.
Identity mismatches and duplicate accounts
If Nextcloud accounts are created from a different identifier than the Microsoft 365 sign-in, one person can end up with two accounts, and imported files can land in an account that user cannot see. Before the first import, decide the canonical identifier, such as directory username or email address, and whether accounts come from LDAP or Active Directory, OpenID Connect or SAML. The identity lead owns this decision. Check that a test user's OneDrive content maps to exactly one Nextcloud account.
Storage sized too low for imported data
Imported OneDrive content, file versions and any duplicates created during the transition can exceed the quota planned for the target. Before import, inventory OneDrive usage per user, set per-user and group quotas, and reserve headroom for the parallel period and for the backup target. The infrastructure owner and the budget approver should sign off together. Confirm how the import counts file versions and whether trash retention adds to usage on your storage backend.
Office and third-party app incompatibility
Office integrations and third-party apps may not support the Nextcloud release you deploy, and an incompatible app can break after import. Before import, list every app and Office option that users depend on, check each against the compatibility notes for the target release, and decide whether to replace, pin or drop it. Nextcloud's upgrade guidance advises disabling third-party apps until they are confirmed compatible. The platform owner decides, with each app's business owner consulted. Test document editing with real files from each team.
Unplanned upgrades during cutover
A security or platform upgrade that lands in the cutover window can change behavior mid-import, break an app or require a database change. Nextcloud publishes a new major version every four months and does not allow skipping major releases, so a server that falls behind must move one major version at a time with a backup before each step. Before import, fix the target release and a change freeze for the cutover window. The platform owner owns the freeze, and change management approves any exception.
Questions buyers ask before moving from OneDrive
How much does a OneDrive to Nextcloud migration cost?
Cost follows the written scope, and the main drivers are total data volume, the number of users, and how much of the identity and tenant setup needs work first. Fixed-scope engagements are quoted from an agreed list of deliverables, so compare quotes on what each one includes. Ask every bidder to separate one-time work from recurring costs. One-time items usually include discovery, the target build, identity and Microsoft tenant setup, pilot batches, user communication, cutover and decommissioning. Recurring items include hosting, storage growth, backups, Nextcloud maintenance and any support subscription. Ask whether the quote covers rework after a failed pilot, and whether the price is based on per-user work or per-batch work. If you want Nextcloud Enterprise support, Nextcloud's pricing page lists its Standard tier from 71.29 euros per user per year for 100 or more users, so ask whether that subscription is included in the quote or priced separately.
How long does a OneDrive migration to Nextcloud take?
Duration depends on total data volume, the number of user batches, how clean the OneDrive data is, and how much identity work must finish first. No timeline applies to every tenant, so ask for a schedule built from your own inventory of users, files and sharing. Sizing drivers include the share of data in very large folders, long file paths, file names that cause import errors, and the number of sharing links that need review. Identity readiness also sets timing: if directory accounts or single sign-on are not ready, pilot batches wait. Ask the bidder to state their assumptions about throughput, the number of pilot rounds, the user communication window and the change freeze period. Confirm the Nextcloud release line as well. Nextcloud publishes a new major version every four months, and Nextcloud 35 was released on 16 September 2026 with end of life in September 2027, so build any upgrade into the plan.
What do we need from our identity and Microsoft admins?
You need a named identity owner, a Microsoft 365 tenant administrator who can approve the app registration and consent, and a sponsor who approves user communication. The identity owner decides how Nextcloud accounts are created and how people sign in, whether through directory accounts over LDAP or Active Directory, or through OpenID Connect or SAML. The tenant administrator confirms which accounts and licenses are in scope and checks that conditional access and consent policies will not block the import. The sponsor owns the message to staff, the schedule for each batch, and the escalation path when someone's files are missing. Ask the bidder which roles they expect you to fill, how much time each role needs during the project, and who signs off the cutover list. Raise tenant policy questions early, because they are the most common reason a pilot stalls.
Can our own IT team migrate OneDrive to Nextcloud?
Your team can migrate OneDrive data to Nextcloud if it has hands-on experience with both Microsoft 365 administration and a production Nextcloud platform, and if it has time for the work alongside existing duties. Internal staff know the users, the data and the approval chain, which helps with decisions. The hard parts are usually at the edges: permission mapping, sharing links that must be recreated, large or unusual files, parallel run and rollback. Ask who will run the import, who will verify results against a sample, who will handle exceptions, and who will keep the platform patched during the project. Nextcloud's upgrade rules add work here: administrators must upgrade one major version at a time, back up before every upgrade, and disable third-party apps until they are confirmed compatible. A practical test is whether your team can complete a pilot batch, document it, and repeat it without the same few people on call.
What does not transfer from OneDrive to Nextcloud?
Some OneDrive behavior will not carry over as-is, so get the exact list in writing from the bidder and check it against the current documentation for the import app. Typical gaps to review include sharing links and their expiry settings, version history depth, activity records, co-authoring sessions in Office, and anything tied to Microsoft licensing or retention policies. Some items must be recreated by hand, such as shares, group membership and external guest access. Other content may be excluded by design, such as the personal files of leavers, which needs a decision from your records owner. Ask for a list that states what is migrated, what is recreated, and what is excluded, with a named owner for each category. Also ask how skipped files will be reported and why each one was skipped, because that report is the basis for user support and your audit trail.
How are the parallel run and decommissioning handled?
A parallel run keeps OneDrive and Nextcloud both available for a defined period while batches move over, and decommissioning starts only after written sign-off. Agree in advance who approves each batch, how users report problems, how changes made in OneDrive during the run are reconciled, and what the rollback path is. Ask how incremental syncs handle files that change after the first copy, and how the final pass is timed with the user change freeze. Decommissioning should follow a checklist: confirm the final sync, archive what your records policy requires, remove user access, revoke app registrations and licenses that are no longer needed, and record the outcome. Confirm retention obligations for OneDrive data with your legal and compliance owners before any deletion. The migration does not decide those rules, and deleting data too early can create problems that are hard to reverse.
What checks should run before the first OneDrive import?
Run a short set of checks on a sample account before any production batch starts, and record the results. Confirm that the import app version works with your Nextcloud release, and that the release is one you intend to keep for the planned period. Verify tenant consent and the account used for the import, and test that it can read the sample user's files without broader rights than the plan allows. Check storage quotas, free space and backup status on the Nextcloud side, and take a verified backup before the first run. Review file names, path lengths and unusual file types in the sample, then decide how each class will be handled. Finally, test a sample user's login through the identity method you chose. Ask the bidder to show these results in writing before the pilot batch begins, so that the go or no-go decision rests on evidence.
How DeployOpen scopes, delivers and supports the migration
DeployOpen plans and runs the move from OneDrive into Nextcloud inside infrastructure you control, starting with a written scope that names the users, folders and sharing rules in play. Engagements are fixed-scope, so deliverables and timelines are agreed in writing before the migration work begins.
How we scope
- The written scope lists which OneDrive accounts, shared libraries and folder trees move, and which stay behind.
- We inventory file counts, total storage and sharing links so the cutover plan and target sizing reflect your real data.
- The scope records how identities map from Microsoft 365 to Nextcloud users, including whether directory login is in or out of scope.
How we build
- We configure the OneDrive integration app on a test instance and run pilot imports against a representative set of accounts.
- Each pilot is checked for file integrity, folder structure, modification dates and permissions before wider batches run.
- We document which items the import does not carry over, such as version history and co-authoring state, so expectations are set in advance.
How we hand over
- You receive runbooks for each import batch, the cutover sequence, rollback steps and the user communication plan.
- Verification reports list migrated users, mismatches found and how each was resolved, so your team can audit the result.
- Administrators are trained on the Nextcloud settings, apps and maintenance tasks they will own after the migration closes.
How we support
- Post-migration support covers user questions about moved files, sharing links and sync clients during the stabilization period.
- Ongoing support, upgrades and continuous testing are available as a retainer, scoped in writing separately from the migration.
- Confirm with us before the engagement whether you need support hours that match your business day and escalation path.
