Which fits a Dropbox team: Dropbox or self-hosted Nextcloud?
Dropbox fits a team when the priority is a managed service that someone else operates, standard sync across desktop and mobile, and no internal staff time spent on servers, databases or upgrades. If your data can sit in Dropbox's infrastructure under its terms, your team has ordinary sharing needs, and nobody in IT wants to own patching or backups, the managed model is usually the lower-risk choice. A renewal or price change alone does not make a self-hosted move necessary, so start by confirming what the current plan includes for storage, version history and admin controls.
Nextcloud fits when the data has to stay inside your own infrastructure, when sharing and retention rules need local control, or when lock-in and exit terms are a board-level concern. It also fits when your team can run the platform: applying each major release in turn, which the upgrade documentation requires one version at a time with a backup before every step, keeping the database and PHP versions supported, and testing third-party apps before enabling them. Nextcloud Server is free under AGPL-3.0, so the decision is about operating capacity and support arrangements, not license fees. Confirm which support model you would use, because a community deployment and an enterprise subscription carry different response commitments.
The decision turns on four things: team size, data volume, residency rules and available operations capacity. Larger teams and bigger data sets raise the cost of storage, backup and admin time on the self-hosted side, while residency rules may settle the question on their own if files cannot leave your jurisdiction. Ask whether you have people who can own the service every month, not only at launch. If the answer is no, a managed or retained support arrangement may be the realistic middle path, and the cost of that model should be compared with what you pay Dropbox today.
Which option fits which team situation
This table maps common team situations to the better fit between Dropbox team plans and self-hosted Nextcloud, and names the condition that tips each one. Read each row as a starting point: the deciding factor is usually who will operate the service and where the data must reside.
| Team situation | Better fit | Condition that makes it so |
|---|---|---|
| Small team with no dedicated sysadmin | Dropbox team plan | Nobody on staff can own patching, backups, upgrades and certificate renewals on a recurring schedule, so a managed service avoids that operating load. |
| Regulated team that must keep files in its own datacenter | Self-hosted Nextcloud | Policy requires files, logs and backups to stay in facilities the organization controls, and confirming Dropbox's storage options against that policy shows a gap. |
| Team with a large single-folder archive | Self-hosted Nextcloud, with the desktop client for transfers | The archive exceeds Dropbox browser download limits of 250 GB or 10,000 files, so bulk moves depend on sync clients and a planned migration either way. |
| Team needing custom retention or Active Directory single sign-on | Self-hosted Nextcloud | Retention rules must be set by the organization, and the LDAP app or SAML and OpenID Connect backends must match the existing directory design; confirm both in a proof of concept. |
| Team with existing Kubernetes operations | Self-hosted Nextcloud, if the platform team already runs stateful workloads | Clusters, persistent storage, database operators and backup tooling are already supported internally; Nextcloud All-in-One offers a Helm chart to start from. |
| Team that relies on Dropbox sharing links and recovery windows as-is | Dropbox team plan until a migration plan is approved | Links, permissions and version history do not carry over automatically, so workflows need to be rebuilt and tested before cutover. |
Where the data lives and who controls it
Dropbox team data is stored in infrastructure that Dropbox operates, and the storage location is governed by its own terms and regional options. Self-hosted Nextcloud places the server, database and file store wherever your organization chooses: your cloud account, a colocated datacenter or an air-gapped network with no outbound internet path. The choice of location is yours to make and to document.
- Named regions: Ask Dropbox in writing which storage regions are available to your plan and whether they apply to all data types, including previews and backups.
- Your own boundary: With Nextcloud, you select the region or facility and can keep the entire stack inside one network segment.
- Air-gapped operation: Nextcloud can run without internet access, but you must plan for updates, app packages and certificate management delivered by hand.
- Sub-processors: Request Dropbox's current sub-processor list. For Nextcloud, the sub-processors are the hosting provider or datacenter you contract with.
- Backups and replicas: Confirm where copies, snapshots and disaster recovery sites are held, since they often fall under the same residency requirement.
Before deciding, confirm the residency obligation in writing with your legal and compliance teams and check the vendor's current documentation for each data type.
With Dropbox, the vendor operates the platform, so audit logs, retention of deleted files and backup copies are produced and kept by Dropbox under its service terms. With Nextcloud, the server writes logs and your backup tooling creates copies that you control. Access to raw logs becomes an operational task you must staff and monitor.
- Audit trail access: Dropbox exposes admin activity reporting through its admin console. Confirm which events are retained, for how long and whether exports are available for your SIEM.
- Server logs: Nextcloud writes application and access logs to files or syslog that you can forward to your own log platform.
- Backup tooling: Nextcloud All-in-One includes BorgBackup-based backups, but you decide the target, retention and restore testing schedule.
- Recovery windows: Compare the file recovery and version history windows in Dropbox's plan documentation with the retention you configure for Nextcloud backups and trash.
- Restore evidence: Keep records of restore tests. A backup that has never been restored is not evidence of recoverability.
Ask Dropbox for the exact retention periods for your plan and confirm what administrators can export before you compare them with your own log and backup schedules.
Dropbox team sign-in is managed through Dropbox accounts with options for single sign-on configured by an admin. Nextcloud can authenticate users against your existing directory, which means access follows the same joiner, mover and leaver process your identity team already runs. The integration choice affects both security and the workload on your identity team.
- Directory sync: The Nextcloud LDAP app lets LDAP and Active Directory users appear in Nextcloud and sign in with their directory credentials.
- Federated sign-in: Nextcloud also documents OpenID Connect and SAML authentication backends for federated single sign-on.
- Group mapping: Map directory groups to Nextcloud groups and shares so that access removal happens in one place.
- Multi-factor authentication: Confirm which second factors each option supports in your chosen identity provider and in Nextcloud.
- Client access: Desktop and mobile clients must work with your sign-in method. Test token expiry and device revocation before rollout.
Test the identity path end to end, including account deprovisioning, before any production data is moved.
Compliance assessments ask for evidence that controls operate. With Dropbox, you rely on the vendor's independent reports and your own configuration records. With a self-hosted Nextcloud, you produce much of the evidence from your own systems, including configuration baselines, change records, access reviews and restore tests. DeployOpen prepares controls and evidence for compliance assessments but does not issue audit reports, attestations or certifications. Independent auditors and certification bodies perform those functions.
- Control mapping: Map each applicable control to a configuration, a procedure or a log source so an assessor can trace it.
- Vendor reports: Ask Dropbox for its current independent assurance reports and the scope they cover.
- Licensing: Nextcloud Hub is licensed under the AGPL and is free to self-host. Nextcloud GmbH sells optional Standard, Premium and Ultimate enterprise subscriptions for support and additional features.
- Update obligations: Nextcloud publishes a new major version every four months, and each receives monthly maintenance releases for one year. Plan a patch process that your assessor can review.
- Assessor scope: Confirm early which auditor will review the environment and what evidence format they accept.
Ask your assessor to confirm the evidence list before the build starts, since it determines what must be logged and retained.
What the Nextcloud licence and enterprise tiers change
The Nextcloud Hub licence is AGPL, and the server is free to self-host, so a team pays no licence fee to run the software itself. What the enterprise subscriptions buy is support, maintenance length and additional features. Nextcloud GmbH sells Standard, Premium and Ultimate subscriptions with a 100-user minimum, with list prices starting at 71.29, 104.99 and 204.75 euros per user per year for 100 or more users, and lower rates from 200 users. Nextcloud One is a managed hosting option for organizations under 100 users. Confirm current prices, currency, VAT treatment and whether a subscription covers your user count directly on the Nextcloud pricing page, because list prices change and quotes depend on the user count.
The tiers differ mainly in how long a version is maintained, how much support you get and how the instance can be scaled. According to the pricing page, Standard includes one year of maintenance. Premium adds a maintenance lifecycle of five or more years, extended support hours and clustered instance support. Ultimate adds support up to 24/7 with response times down to one hour. A team needs a subscription when its own staff cannot absorb a security issue outside business hours, when its audit or procurement rules require a vendor-backed support contract, or when it needs a clustered deployment and a maintenance window longer than the community cycle. A small team with an experienced administrator may run the community edition without one, but it should price the staff time for upgrades and incident response against the subscription before deciding.
Nextcloud 35 is the current major release according to the maintenance and release schedule, and a new major is published roughly every four months. Each major is supported for one year through monthly maintenance releases. Nextcloud does not allow skipping major releases during upgrades, so an instance on an older major must move through each intermediate version in order, with a backup before every step and third-party apps disabled until confirmed compatible. Plan this upgrade cadence into operations from the start, and check the schedule for the support end dates of the version you deploy, since a Standard subscription's one-year maintenance does not match a five-year Premium lifecycle.
What Dropbox and Nextcloud cost to run, by component
What do you pay Dropbox for, and what is included?
With Dropbox, you pay a recurring per-user team subscription, and the storage, sync, sharing controls and version history that come with the plan are part of that price. Your cost moves with seat count and with any extra storage or admin features your tier requires. Confirm the current per-seat price, minimum seat count, included storage per user, billing term and which admin, retention and compliance features sit in each tier directly with Dropbox, because these terms change and are not set out here. Ask for the renewal uplift in writing, since that is where many teams see cost change.
What does Nextcloud cost if you use the community edition?
The Nextcloud server is licensed under AGPL-3.0 and is free to download and self-host, so the software line item is zero. Your real costs are the infrastructure and people around it: servers, a database (MariaDB or PostgreSQL), a PHP runtime, a web server, storage, backups and the staff time to run upgrades and monitoring. These costs are mostly recurring, except initial setup and integration work, which is one-time. Ask any implementation partner for a fixed-scope quote that lists each component separately so you can compare it with your current Dropbox spend.
Which infrastructure costs recur when running Nextcloud?
Recurring infrastructure costs include compute for the application and database, disk or object storage that grows with data volume, network egress where your users download large volumes, and backup storage and retention. Redundancy raises the bill, since high availability needs more nodes, replicated storage and a tested restore path. Nextcloud's system requirements list supported database versions and PHP versions, so budget for the software versions your platform team will keep current. Ask for the storage growth assumption, the backup retention period and the node count used in any quote.
How does the Nextcloud enterprise subscription change the cost?
Nextcloud GmbH sells Standard, Premium and Ultimate enterprise subscriptions 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, for 100 or more users, with lower rates from 200 users. Standard includes one year of maintenance, Premium adds a maintenance lifecycle of five years or more and clustered instance support, and Ultimate adds support up to 24/7 with response times down to one hour. The subscription is optional, so decide whether you need vendor support, a long lifecycle or clustering before you add this cost.
How much staff time does running Nextcloud take?
Staff time is often the largest recurring cost and is the one most teams underestimate. It covers monthly maintenance releases, planned major upgrades, backups and restore tests, monitoring, user provisioning, client rollout and first-line support. Nextcloud does not allow skipping major releases, so each upgrade is a planned step with a backup and a check that third-party apps are compatible. The effort depends on user count, number of integrations, uptime targets and whether you run the platform in-house or with a partner. Ask for a written split of build effort and recurring operations effort, with the support hours each side covers.
What is one-time and what recurs in a self-hosted file sync move?
One-time costs include architecture and design, installation, hardening, identity integration with LDAP, OpenID Connect or SAML, data migration from Dropbox, client rollout and staff training. Recurring costs include infrastructure, backups, licenses for any enterprise subscription, upgrades, monitoring, security patching and support. Migration effort is one-time, but it is driven by data volume and by how many shared folders and links must be recreated. Ask the vendor or partner to label each line item as one-time or recurring so the annual total is visible.
What should you request in a quote for Nextcloud?
Ask for a fixed-scope quote with written deliverables, separated into one-time and recurring items. Include the user count, data volume at start and at a stated growth rate, redundancy level, backup retention, supported database and PHP versions, identity integration, client rollout, and the support hours and response times. Request the exact enterprise tier and its user-count pricing if you want vendor support. Ask what happens at each Nextcloud major release, how many releases per year the scope covers, and who owns the backup restore test.
What should you confirm with Dropbox before comparing the costs?
Before you compare totals, confirm with Dropbox your current team plan price per user, minimum seat count, included storage, what counts toward storage limits, how version history and file recovery windows differ by tier, any charges for extra storage, and whether the features you need such as admin controls and data location options are in your tier. Ask whether the price is locked for the term and what the renewal increase is. Because Dropbox terms change, use the vendor's current published pricing and your signed order form as the source, not a third-party summary.
What a move from Dropbox to Nextcloud involves
The sequence turns a set of Dropbox team folders into Nextcloud spaces that people can sign in to, sync and share from, with a tested path back if a team's cutover fails.
Scope teams, folders and sharing patterns
Before any data moves, the migration lead lists every Dropbox team, shared folder and external share that people rely on, along with the approximate size and file count of each. Team leads confirm which folders are active and which can be archived. Security and compliance staff record which folders hold regulated data, because those will need their own permissions and retention decisions in Nextcloud. The step is done when the team and folder inventory is signed off by each team lead and the data owners, and each folder has a named target in the new environment.
Export data through the desktop app
Browser downloads from dropbox.com are limited to folders under 250 GB uncompressed with fewer than 10,000 files, and Dropbox recommends the desktop app for large downloads. The migration team therefore copies the larger folders by syncing them to a staging machine or server with the Dropbox desktop client and then copies them into a staging area that Nextcloud can read. Folders that exceed the browser limits are handled this way from the start, not as a fallback. The step is done when file counts and total sizes in staging match the inventory, and a sample of files opens correctly. The exact procedure is covered in the sibling topic on exporting data from Dropbox.
Recreate shared folders, groups and links
Dropbox sharing links, permissions and version history do not carry over automatically, so the team rebuilds each shared space in Nextcloud by hand or with scripts. The administrator creates groups that mirror the Dropbox team structure, assigns folder permissions to those groups, and recreates any public links that are still needed, with passwords and expiry dates chosen again. Teams review each recreated share with its owner. The step is done when every active shared folder has an owner, a group with the right access, and a tested link where one is required, and the list of links that were retired is recorded for the communications step.
Connect identity and directory sign-in
Nextcloud can let LDAP and Active Directory users sign in with their directory credentials through its LDAP app, and it documents OpenID Connect and SAML backends for other identity providers. The identity team decides which source is authoritative, creates a service account for the directory bind, and maps directory groups to Nextcloud groups so that access follows joiner and leaver processes. Multi-factor authentication policy is set at the identity provider. The step is done when a test account from each group signs in through the chosen method, and a user removed from the directory can no longer sign in.
Roll out desktop and mobile clients
Users install the Nextcloud desktop and mobile clients on managed devices, and the endpoint team confirms that the software can be pushed through the existing device management tool. Sync selection is set so that people do not pull whole archives onto laptops. The team also replaces Dropbox shortcuts in desktop and mobile workflows with Nextcloud equivalents and removes the Dropbox client from devices once a user's data is confirmed in Nextcloud. The step is done when a sample of devices per team syncs a folder end to end, and the support queue has a documented path for client issues.
Pilot with one team
A single team that has moderate data volume and a willing lead moves first. The pilot tests the full path: staged data, recreated shares, sign-in, clients and the support process. The team records every problem, such as file name restrictions, sync conflicts or permission gaps, and the fixes applied. The pilot team also tells the migration lead which parts of the runbook were unclear. The step is done when the pilot team has worked in Nextcloud for an agreed period, the lead signs off, and the runbook is updated with every fix found.
Cut over team by team with a rollback plan
Each further team moves in a planned window, with a final delta sync from Dropbox to staging before people switch. Dropbox folders are set to read-only or archived only after the new space is confirmed, and each team has a written rollback plan that names the condition for reverting, the owner who decides, and how Dropbox data is kept intact until the team confirms the move. The step is done when each team signs off on its cutover, Dropbox is retired only after the agreed hold period passes, and the retirement is recorded with the data owner.
Confirm backups, upgrades and ongoing support
Before the last team cuts over, the platform team confirms that backups of the database, data directory and configuration run and that a restore has been tested. The team also schedules Nextcloud upgrades, which must move one major version at a time with a backup before each upgrade and with third-party apps checked for compatibility. The support model is set: internal staff, a support subscription from Nextcloud GmbH, or a DeployOpen retainer, each with its own scope. The step is done when a restore test passes, the upgrade calendar and support owner are documented, and the migration is handed over to operations.
Questions buyers ask before choosing self-hosted file sync
How much effort does running Nextcloud take after go-live?
Expect ongoing operating work rather than a one-time install. Effort is driven by the number of users, the volume of files, how many third-party apps you enable, and how often you apply updates. Nextcloud publishes a new major version every four months and supports each one for a year through monthly maintenance releases, so someone must plan and test upgrades on a steady cadence. Upgrades cannot skip major releases, and you should back up before each one and disable third-party apps until they are confirmed compatible. Ask any implementation partner to write down the upgrade routine, the monitoring you will use, and who owns each recurring task. Confirm the current schedule on the Nextcloud maintenance and release schedule before you plan.
Can our own IT team run Nextcloud without outside help?
Often yes, if the team already runs Linux servers, a web stack and database backups. The deciding factors are whether someone can own upgrades, restore testing and incident response on a fixed schedule, and whether there is cover for holidays and absences. Teams that rely on one administrator tend to find upgrade windows slip. Nextcloud All-in-One is the official installation method and bundles caching, PostgreSQL, optional Nextcloud Office, backups with BorgBackup, ClamAV and full-text search, which reduces the initial build work but does not remove the upgrade routine. Decide whether your team will run it alone, run it with a retainer for support and upgrades, or hand over the whole service. Outside support is available as a retainer or a fixed-scope project, and a written scope is the basis for a quote.
What skills does our team need to operate Nextcloud?
The core skills are Linux administration, a web server such as Apache or nginx with PHP-FPM, a supported database, and backup and restore practice. Nextcloud 35 recommends MariaDB 11.8 or PostgreSQL 18, supports PHP 8.5 with 8.3 and 8.4 also supported, and expects Apache 2.4 or nginx with php-fpm. Add directory integration skills if you connect LDAP or Active Directory through the LDAP app, and identity skills if you use OpenID Connect or SAML. Security staff should know how to review sharing settings, enforce encryption where required, and monitor logs. Confirm the exact platform versions against the Nextcloud system requirements for the release you plan to deploy, since they change between major versions.
How long does a Dropbox to Nextcloud migration take?
No fixed duration can be given here, so treat any number from a vendor or partner as a claim to verify against your own data. The main drivers are total data volume, the number of users and team folders, how many shared links and permissions must be recreated, how many devices need the desktop and mobile clients, and whether teams cut over in waves. Dropbox limits browser downloads of folders to those under 250 GB with fewer than 10,000 files, so large folders usually move through the desktop app, which adds time. Ask for a written plan with a per-team cutover sequence, a test cohort, and a rollback path, and confirm the timeline in the written scope before work starts.
Do we need a Nextcloud Enterprise subscription to run it?
No. Nextcloud Hub is licensed under the AGPL and is free to self-host. Nextcloud GmbH sells Standard, Premium and Ultimate enterprise subscriptions that add support, maintenance lifecycles and extra features, with a 100-user minimum for Enterprise. Standard includes one year of maintenance, Premium adds a lifecycle of five or more years, and Ultimate adds support up to 24/7 with response times down to one hour, according to the Nextcloud pricing page. Whether a subscription is worth it depends on your required response times, how long you need security maintenance on a fixed release, and whether you have in-house capacity to handle issues. Oracle Database is only available with an enterprise subscription. Check current terms on the Nextcloud pricing page and ask any support provider to compare its support hours and response commitments with your own.
What do we need to provide for a Nextcloud project?
The work needs clear inputs before it starts. Provide an inventory of Dropbox team folders, users, groups, external sharing, and retention or legal hold requirements. Provide the target hosting location, network and identity design, including whether users sign in with Active Directory, OpenID Connect or SAML, and the backup and recovery objectives your team expects. Name the business owners who will approve folder mapping and cutover waves, and the staff who will test restores. Access to your cloud accounts, data center or air-gapped network is needed so the deployment stays inside your environment. Ask the provider to list every input it needs in the written scope, because missing inputs are the most common cause of delay.
Will switching break existing Dropbox sharing links?
Yes, you should assume existing Dropbox share links will stop working once the content moves, because links are tied to Dropbox. Recipients will need new links or access granted through Nextcloud. Plan a notice period, a mapping of each shared folder and its permissions to a Nextcloud share, and a message for external recipients. Version history and granular permissions also do not carry over automatically in every case, so confirm how your migration method handles them before the cutover. For the export side, see how Dropbox limits downloads on the Dropbox download help page, and ask your provider to document which metadata moves and which must be recreated by hand.
How DeployOpen scopes a Nextcloud evaluation
DeployOpen plans, implements, hardens, backs up, upgrades and documents self-hosted platforms inside the client's own infrastructure, and a Nextcloud evaluation is scoped the same way. The work runs in your cloud accounts, data center or air-gapped network, so the files, database and logs stay where your security team already controls them. Scope, deliverables and timelines are agreed in writing before work starts, which means the evaluation has a defined end point and a defined set of results rather than an open-ended trial. DeployOpen does not publish a price list, so the practical step is to bring the decision points below to a scoping call and receive a quote that follows from the written scope.
For a Dropbox replacement, the scope usually turns on a short list of decisions: which team folders and sharing patterns must move, which sync clients must be rolled out to which devices, whether directory sign-in through LDAP, OpenID Connect or SAML is required, which recovery window and version history rules the security team expects, and where the storage and backups will live. Each of these should be written into the scope as a named item with an acceptance check, such as restoring a deleted file from a test backup or confirming that a share link expires as configured. Ask DeployOpen to show how each check will be run and what evidence it produces.
Ongoing work is handled separately. Most teams need someone to apply Nextcloud's monthly maintenance releases, plan each major upgrade one version at a time with a backup taken beforehand, and retest third-party apps after each change. These tasks can be covered by a retainer for ongoing upgrades and testing, and the retainer scope should state which Nextcloud release line is covered and who approves a skipped or deferred update. Confirm with DeployOpen whether a retainer is needed from day one or after the initial rollout, and ask which enterprise support tier, if any, your team will rely on for vendor-level response.
How DeployOpen helps you decide and deploy
DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a Dropbox to Nextcloud decision, we start with a written scope that tests whether Nextcloud fits your sync, sharing and recovery needs before any migration work begins.
How we scope
- Map your current Dropbox team folders, sharing links and admin policies to Nextcloud features before committing to a design
- Document which users need desktop sync, mobile access and browser-only access, and which directory source they sign in with
- Agree in writing the storage location, hosting model and recovery expectations, with each item listed as in or out of scope
- Confirm which Nextcloud subscription, if any, your support needs call for, and note that the choice is yours
How we build
- Deploy Nextcloud on your chosen infrastructure, selecting the database, PHP and web server versions the current system requirements specify
- Configure directory login, sharing defaults, quotas and retention settings to match the policies agreed in the scope
- Test sync clients across operating systems, large folder transfers and upload limits against your real team folder structures
- Set up backups and an upgrade runbook that respects Nextcloud's one major version at a time upgrade path
How we hand over
- Deliver architecture, configuration and runbook documentation covering administration, backup restores and upgrade steps
- Run a pilot cutover with selected teams and record the results, issues and rollback steps for the remaining teams
- Train administrators on user onboarding, share audits and recovery requests so your staff can operate the service after handover
- Provide evidence of configuration and controls for your compliance team, noting that independent auditors issue any attestation
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer after handover, with scope agreed in writing
- Plan monthly maintenance and major version upgrades against Nextcloud's published release schedule for your environment
- Retest sharing controls, backups and client compatibility after each upgrade or significant configuration change
- Review your quote against the written scope, since DeployOpen does not publish a price list and fixed-scope work is agreed before start

