Migrate from Dropbox to Nextcloud

How to migrate from Dropbox to Nextcloud without losing team folders

Moving from Dropbox to Nextcloud is a project in three parts: moving the files, rebuilding the permissions and sharing, and rolling out the desktop and mobile clients. It is not a single export. Teams usually arrive here after a renewal, a licensing change, a data residency requirement or a wish to reduce lock-in, and the work is normally led by IT or platform engineering, often with an implementation partner who handles the server build and the cutover plan. The effort depends far more on how many shared folders, external links and users are involved than on the raw data volume, so the first task is an inventory rather than a copy job.

Start by listing every team folder, its owner, its members and its outside sharing links. Dropbox's browser download only produces a .zip for folders under 250 GB uncompressed with fewer than 10,000 files, according to the Dropbox download guide, so any folder above either limit must move through the desktop app. Plan to sync those folders to a staging machine or a dedicated migration account, then upload them into Nextcloud with a client that preserves folder structure. Expect that sharing links, group memberships and version history will not carry over automatically, and record them in a spreadsheet so each team can confirm what it needs to recreate. Confirm with your Nextcloud partner how file timestamps and special characters in file names will be handled before you start.

Cut over one team at a time. For each team, freeze writes in Dropbox, complete the final sync, recreate shares and groups in Nextcloud, install the Nextcloud desktop client, and verify access with a pilot group before announcing the change. Decide early whether Nextcloud will authenticate users through LDAP or Active Directory, OpenID Connect or SAML, because that choice determines who can log in on day one. Keep the Dropbox account read-only for an agreed period so teams can retrieve anything missed, and confirm your contract's terms for exit and deletion. Ask the partner for a written scope that lists the folders, users, clients and acceptance checks, since that document is what keeps the rollout predictable.

Which Dropbox capabilities map cleanly to Nextcloud and which need rework

This table maps the Dropbox features a team relies on to their Nextcloud equivalents and marks each as clean, needs rework or gap. Read it before scoping a migration so that sharing links, version history and client rollout are planned as work items rather than assumed to carry over.

Capability	Nextcloud equivalent	Status and what to confirm
File sync to desktop	Nextcloud desktop client syncing folders from the server	Clean. Confirm client versions supported by your Nextcloud release and test large folder sync on a pilot group first.
Team folders	Group folders or shared folders with group-based permissions	Needs rework. Recreate each Dropbox team folder as a group folder and map membership to groups, not individual accounts.
Shared links	Public share links with optional password, expiry and download limits	Needs rework. Dropbox links do not carry over automatically. Regenerate links and notify recipients, then confirm the link settings you need.
Sharing permissions	Per-share permissions for read, edit, reshare and upload	Needs rework. Map Dropbox viewer, editor and owner roles to Nextcloud permissions and check inherited access on nested folders.
Version history	File versions kept by the server with a retention policy	Gap to confirm. Version history does not migrate with files copied through clients. Confirm retention settings and decide what history to keep in an archive.
Mobile apps	Nextcloud iOS and Android apps with camera upload	Clean. Confirm app behavior with your mobile device management policy before rollout.
Admin controls and audit	Admin settings, user and group management, and activity logging	Needs rework. Dropbox audit and sharing reports differ. Confirm which logs your compliance team needs and configure retention before cutover.
Single sign-on	LDAP or Active Directory, OpenID Connect or SAML backends	Needs rework. Identity configuration is per deployment. Confirm the authentication backend with your identity team.

What data and integrations move, and which export paths are documented

Dropbox offers a browser download path with documented limits, and a desktop app path for larger transfers. The cards below cover what each path carries, what it leaves behind, and which identity and integration decisions must be made before the first team folder moves.

Browser download limits

Dropbox lets users download a folder from dropbox.com as a .zip file only when the folder is under 250 GB uncompressed and holds fewer than 10,000 files. Any team folder above either threshold cannot be exported this way in one step. Check each shared folder's size and file count before planning batches, and split larger folders by subfolder so every batch stays inside both limits.

Desktop app for large transfers

Dropbox recommends the desktop app for large downloads, so it is the documented route for team folders that exceed the browser limits. Sync the folders to a staging machine or a dedicated migration account, then copy them into the Nextcloud sync folder or upload them with the Nextcloud desktop client. Confirm available local disk space and expect the initial sync to take as long as the data volume requires.

What the export does not carry

A file export carries file contents and folder structure, but sharing links, per-person permissions, comments and most version history do not come across as working objects. Record every shared link and its expiry date, every shared folder and its members, and any file requests before cutover. Recreate these in Nextcloud as shares and link shares, and tell recipients which URLs have changed.

Inventory third-party app connections

Dropbox connections to Slack, Microsoft Teams, Google Workspace, Zoom, Atlassian and other apps are stored in the Dropbox account, not in the files. Export a list of connected apps and the accounts that authorized them, then decide which integrations Nextcloud replaces with a native app, which need a webhook or API call, and which are retired. Each replacement needs an owner and a test.

API integrations to rebuild

Any internal script, backup job or business application that calls the Dropbox API will stop working after the tenant is closed. List every API token, app key and scheduled job, with its owner and the folders it reads or writes. Rebuild each one against the Nextcloud WebDAV or OCS interfaces, and confirm the authentication method for each service account before cutover.

Map identities to directory or SSO

Nextcloud can let LDAP and Active Directory users appear in the instance and sign in with their directory credentials, and it also documents OpenID Connect and SAML authentication backends. Decide which of these matches the organization's identity source before creating accounts, and map each Dropbox team member to a single directory identity. Shares and group folders should be assigned to groups, not to individual accounts that may later leave the company.

Migration sequence from inventory to decommissioning Dropbox

This sequence moves Dropbox team folders into Nextcloud in controlled stages, from an inventory of what exists through a pilot, a parallel run, team-by-team cutover and an archive of the Dropbox data. Each step closes with a named output that the next step depends on.

Inventory folders, sizes and file counts
List every team folder, shared folder and link in the Dropbox team, with its owner, approximate size, file count, member list and whether it holds regulated data. Dropbox's browser download limits apply to folders under 250 GB uncompressed with fewer than 10,000 files, so flag any folder that exceeds either threshold for desktop app transfer. Confirm the inventory with team leads and the compliance owner. The step is done when a signed folder inventory exists and every folder has an owner and a target team.
Build the folder-to-space map
Turn the inventory into a folder map that links each Dropbox folder to a Nextcloud destination, such as a group folder, a team space or a personal space, with its permission groups and sync expectations. Decide where directory groups come from, using the LDAP or Active Directory integration or another supported sign-in method, so accounts are not created by hand. Record which shared links will be recreated and which will be retired. The output is an approved folder map that becomes the basis of the pilot.
Stand up the Nextcloud target and pilot one team
Install the Nextcloud target in your own infrastructure, using the official installation method and the system requirements for the release you plan to run, and configure backups before any data arrives. Choose one team with moderate data volume and a willing lead. Move its folders using the Dropbox desktop app and the Nextcloud desktop client, then compare file counts, sizes and modification dates. The output is a pilot report that lists mismatches, permission problems and user feedback, with fixes applied before the next team.
Run Dropbox and Nextcloud in parallel
Keep Dropbox as the system of record for teams not yet cut over, while pilot and early teams work in Nextcloud. Define which copy wins if a file is edited in both places, and ask team leads to avoid moving files between systems during the window. Track sync errors, shared link recreation and mobile client adoption in a shared log. The output is a dated parallel-run log with an agreed rule for conflicts, reviewed before each cutover.
Plan the Nextcloud upgrade path as a recurring input
Treat Nextcloud major version upgrades as a planning input for the whole migration, not a single event. Nextcloud publishes a new major version every four months, supports each for one year through monthly maintenance releases, and does not allow skipping major releases, so every upgrade moves one major version at a time. Before each upgrade, take a backup, check that third-party apps are confirmed compatible, and schedule the work around cutovers. Ask your vendor or partner which release lines you will run and when each reaches end of life. The output is an upgrade calendar kept with the cutover plan.
Cut over team by team with a checklist
Move each remaining team in turn using a written cutover checklist: final sync from Dropbox, freeze of edits in the old location, confirmation of file counts and checksums where available, reissue of shared links and group permissions, a rollout of the Nextcloud desktop and mobile clients, and a user briefing on where to find files. Sign off each team before the next begins. The output is a completed checklist per team, stored with the folder map.
Archive Dropbox data before decommissioning
Once every team is signed off, take a final export of the Dropbox data you are required to keep, using the desktop app for large folders, and store it in an access-controlled location within your own retention rules. Confirm with legal and compliance what must be retained, for how long and in which format, since sharing links, permissions and version history do not carry over automatically. Cancel the Dropbox team plan only after the archive is verified and the retention owner has approved it. The output is a verified archive with a retention record and a written decommission approval.

How to run Dropbox and Nextcloud in parallel and cut over by team

The parallel period is where most migrations succeed or fail, so decide before any sync starts which location is authoritative for each team. Dropbox should stay the system of record for a team until its Nextcloud folders have been synced, compared and signed off by the team lead. Write this rule down and publish it in the same message that announces the Nextcloud rollout, because users who edit the same files in both places will create conflicting copies that nobody can easily reconcile later. Confirm with your admins whether Dropbox will be set to read-only for migrated folders during the switch, and whether your Nextcloud server applies any group-level quota or sharing restrictions that could block a team from working.

Shared links do not carry over, so plan to reissue them rather than assume they still work. For each shared folder, create the equivalent share in Nextcloud, set the recipient permissions to match the original Dropbox role, and send the new link to the people who used the old one. Keep a register of old and new links so that external recipients can be redirected, and set expiry dates on any Nextcloud public link that should not stay open indefinitely. Confirm with your security team which sharing defaults apply, especially for external guests, before the first team is moved.

Cut over one team at a time, and only after its folders pass a verification step. Check file counts and total size against the Dropbox export, spot-check version history for a sample of documents, and confirm that every team member can sign in through the Nextcloud desktop and mobile clients with the identity method your organization has chosen. When a team signs off, change the Dropbox folders to read-only and leave them in place for an agreed retention period. That retained copy is your rollback path: if a team cannot work in Nextcloud, it can return to Dropbox while you fix the gap. Confirm with your admins how long Dropbox access will remain on your current plan, since that date sets the real limit on rollback.

What drives migration cost and duration, and how to keep each down

This table lists the main drivers of effort and cost when moving Dropbox team folders to Nextcloud, with the reason each one matters and the lever that keeps it under control. Read each row as a question to answer during scoping, since the size of each driver in your environment determines the quote.

Driver	Why it changes cost or effort	How to keep it down
Total data volume	Transfer time, bulk sync bandwidth and server storage all scale with the bytes moved, and Dropbox browser downloads stop at folders under 250 GB, so large folders need the desktop app.	Measure folder sizes before scoping, move large archives in phases, and use the desktop app for folders above the browser download limit.
Folder count and depth	Each file and nested folder adds sync index work, and folders holding 10,000 or more files exceed the Dropbox browser download limit and slow desktop sync.	Prune stale and duplicate content before migration and flatten deep trees into clearly named team folders.
Sharing links and external sharers	Shared links, expiry settings and guest access do not carry over automatically, so each one must be recreated and tested with its recipients.	Export a link inventory from Dropbox, group links by owner, and have owners confirm which links still need to exist.
Identity integration	Users need accounts and group membership in Nextcloud, and sign-in through LDAP, Active Directory, OpenID Connect or SAML adds configuration and testing before cutover.	Decide the directory source early, map groups to Nextcloud team folder permissions, and pilot sign-in with one team.
Client rollout to desktop and mobile	Each user must install and sign in to the Nextcloud desktop and mobile clients, and sync conflicts appear when old and new clients run on the same folders.	Publish a standard install package, schedule rollout by team, and remove Dropbox clients only after each team confirms its files are in sync.
Customizations and apps	Third-party apps, custom retention rules or office integrations must be checked against the Nextcloud version in use, and unsupported apps may need to be disabled during upgrades.	Limit the app set to what teams need, record each app and its version, and test them on a staging instance before production.
Enterprise subscription tier	Standard, Premium and Ultimate differ in maintenance length, support hours and response times, and enterprise subscriptions carry a 100-user minimum according to the Nextcloud pricing page.	Compare tiers against your support hours and maintenance window, ask for a written quote tied to user count, and confirm the minimum before choosing.
Upgrade and operating discipline	Nextcloud does not allow skipping major releases, so each upgrade is a planned step with a backup, which adds recurring staff time after cutover.	Agree an upgrade cadence and backup test with the operator, and confirm who performs each step in the written scope.

What usually goes wrong when moving from Dropbox to Nextcloud

Most Dropbox-to-Nextcloud problems come from assumptions that hold in Dropbox but not in a self-hosted server: links, permissions, client versions and upgrade paths. Each card below names one failure point, what it looks like in practice, and the check to run before users move over.

Broken shared links and lost guests

Dropbox share links do not carry over to Nextcloud, so every external collaborator and public link needs to be recreated and re-sent. Guests who used a Dropbox account to view a folder will not have a Nextcloud account unless you create one or use a public share. Build an inventory of active links and external users from Dropbox before cutover, then decide per link whether to recreate it, convert it to a password-protected public share, or invite the guest as a named user. Test each recreated link from a signed-out browser.

Permissions that do not map to group folders

Dropbox team folders grant access per member and per folder, while Nextcloud group folders apply group-based permissions with their own rules for sharing and deletion. A user who could edit in Dropbox may land as read-only in Nextcloud, or may gain access to a folder they should not see. Map each Dropbox team folder to a Nextcloud group folder on paper first, list who has which right, and review the result with each team lead before any data is copied.

Sync conflicts during the parallel run

If some teams keep editing in Dropbox while others have started in Nextcloud, the same file can be changed in both places. The desktop clients then create conflicted copies that are easy to miss in large folders. Freeze write access to a folder during its cutover window, or pick one system of record per folder and state it in writing. Check for conflicted-copy filenames after each sync pass and resolve them with the file owner.

Client version drift across desktop and mobile

Users install the Nextcloud desktop and mobile clients at different times, and older builds can behave differently from the server version you run. Without a pinned minimum client version, support tickets become hard to diagnose. Publish the supported client versions alongside the server release you deploy, push them through your endpoint management tooling where possible, and check the client version in the admin view during the first week of each team's rollout.

Upload limits on the server

Large files and folder uploads can fail on the web server or PHP layer long before they reach Nextcloud's own quota logic. A failed 10 GB upload often looks like a sync error on the client, which confuses users and admins alike. Set the PHP upload and post size limits, the web server body size limit, and any reverse proxy timeout together, then test with a file larger than your largest known Dropbox item. Confirm the values in the Nextcloud admin manual for your installation method.

Skipped major upgrades and broken apps

Nextcloud does not allow skipping major releases, so an upgrade has to go one major version at a time, with a backup taken before each step. Third-party apps often block an upgrade until their maintainer confirms compatibility, and an app that is disabled after the fact can remove features users depend on. Keep a written list of installed apps, check each against the target version before upgrading, back up first, and schedule upgrades in a maintenance window that a named owner can roll back.

How the migration differs by team size and starting point

A small team on one Dropbox plan usually has a short list of shared folders, a small number of people who know where things live, and a limited set of sharing links. The migration is mostly a sequencing exercise. Because Nextcloud One managed hosting applies only to organizations under 100 users, a team of that size can compare a managed instance with a self-run server before committing to infrastructure. Self-hosting still requires someone to own upgrades and backups.

Inventory first: List every shared folder, its members and any public links before copying anything.
Move one folder at a time: Sync a single folder through the desktop app, check file counts and sizes, then move the next.
Choose hosting early: Compare Nextcloud One managed hosting, which is limited to organizations under 100 users, with a server in your own cloud account.
Plan the owner role: Name one person to run upgrades and restore tests, since no vendor will do it by default.
Keep Dropbox read-only for a set period: Confirm the cutover date with the team before disabling write access.

Confirm with Nextcloud the current terms of Nextcloud One for your user count and region before deciding.

Questions buyers ask before moving from Dropbox to Nextcloud

What does a Dropbox to Nextcloud migration cost?

The cost is driven by the work your environment needs, not by a fixed fee. The main components are the Nextcloud server and its database, disk or object storage sized for your data, backups, the people who run the platform, and an optional Nextcloud Enterprise subscription. Some costs are one-time, such as planning, data transfer and client rollout. Others recur, such as hosting, storage growth, backup retention, maintenance and support. Ask any implementation partner for a quote built from a written scope that lists the team folders, data volume, user count, identity integration and cutover approach. Do not compare quotes unless each one covers the same items.

How long does moving files from Dropbox to Nextcloud take?

Duration depends on how much data you move, how many folders and users are involved, and how many teams cut over at once. The largest factors are total data volume and file count, because Dropbox limits browser downloads of a folder to folders under 250 GB uncompressed with fewer than 10,000 files, so larger team folders need the desktop app. Sync speed on your network and the number of cutover waves also matter. Plan a pilot team first, then move remaining teams in waves. Your written scope should state the timeline and the assumptions behind it.

What does our internal team need to provide?

Your team needs to supply decisions and access that only your organization can give. This includes a list of team folders and their owners, the users and groups for each team, the identity source they sign in with, and the network and storage location where Nextcloud will run. You also need someone to approve the cutover order, confirm which data can be retired, and define retention for old Dropbox content. Internal staff will usually handle user communication and desktop client rollout. Ask any provider to name these inputs in the scope so gaps are visible before work starts.

Can we run the Dropbox migration ourselves without a partner?

Yes, a capable internal team can run a Nextcloud migration, and the platform is free to self-host under the AGPL. The question is whether your team has time and skills for the work that is not free, including sizing, hardening, backups, upgrades and user support. Nextcloud requires upgrades one major version at a time with a backup before each one, which is an ongoing duty. If you want outside help, a fixed-scope engagement can cover planning, implementation, hardening, backup setup and documentation, while retainers can cover upgrades and ongoing support. Decide based on your internal capacity and risk tolerance.

Do Dropbox sharing links and version history carry over to Nextcloud?

Files and folder structure can be copied through the desktop app, but sharing links, permissions and version history do not transfer automatically, so they must be recreated or accepted as lost. Plan for this with each team. Identify which links external partners rely on, rebuild those shares in Nextcloud, and tell recipients the new URLs before the old Dropbox links are retired. For version history, decide whether only current files are needed or whether older versions must be kept as separate archives. Confirm the exact behavior of your migration method in a test folder before the first wave.

How does the Nextcloud licence and enterprise tier affect cost?

Nextcloud Server is licensed under AGPL-3.0 and is free to self-host, so software licensing is not a per-user cost for the community version. An enterprise subscription is optional and adds support and additional features. Nextcloud sells Standard, Premium and Ultimate tiers with a 100-user minimum. According to Nextcloud's pricing page, list prices start at 71.29 euros per user per year for Standard, 104.99 euros for Premium and 204.75 euros for Ultimate, with lower rates from 200 users. Standard includes one year of maintenance, Premium adds a lifecycle of five or more years, and Ultimate adds support up to 24/7. Check the current pricing page and decide whether your support and maintenance needs justify a subscription.

Who handles security and compliance evidence after the move?

Your organization remains responsible for the controls around the platform, including access, encryption, backups, patching and logging. DeployOpen can plan and implement these controls, document them and prepare the evidence that compliance assessments review. DeployOpen does not issue audit reports, attestations or certifications, which come from independent auditors and certification bodies. Ask for the security scope, including hardening, backup testing and any security testing, to be written into the engagement before work begins.

How DeployOpen scopes, runs and supports the Dropbox to Nextcloud migration

DeployOpen plans, implements, integrates, hardens, backs up, documents and supports self-hosted Nextcloud inside your own infrastructure, so team folders, sharing and client rollout are agreed in writing before any data moves. The work follows the same arc for every team: scope the folders, build the target, cut over by team, then hand over and support.

How we scope

Inventory Dropbox team folders by size, file count and owner, flagging any folder above the browser download limits.
Map each shared folder and link to a Nextcloud equivalent, with the permissions and recipients to recreate by hand.
Agree the cutover order by team, the user groups to load from your directory and the written deliverables and timelines.

How we build

Deploy Nextcloud in your cloud account, data center or air-gapped network, with database, caching and backup components sized to the scoped data.
Configure directory sign-in through the LDAP app or the supported OpenID Connect or SAML backends, and test with pilot users.
Run a test migration through the desktop sync client on a copy of one large team folder, checking file counts, sizes and modification dates.

How we hand over

Document the target architecture, upgrade procedure, backup and restore steps, and the one-major-version-at-a-time upgrade path.
Provide per-team cutover runbooks covering client rollout on desktop and mobile, link recreation and the Dropbox decommissioning date.
Deliver a written record of what was migrated, what was recreated manually and what users must confirm after cutover.

How we support

Ongoing support, upgrades and continuous testing are available as a retainer after handover, agreed separately from the migration scope.
Plan Nextcloud upgrades around its published release schedule, with a backup taken before each upgrade and third-party apps tested first.
Ask any provider, including DeployOpen, to confirm in writing which subscription tier, maintenance window and response commitments apply to your deployment.