How to Move Your Team from Dropbox to Nextcloud Without Losing a Single File

Dropbox is deceptively simple. Files sync, folders are shared, and everything just works. That simplicity is also what makes migrating away from Dropbox tricky: the real complexity hides in shared folder hierarchies, external links, and years of accumulated folder structures that nobody fully understands. This guide covers the complete process of moving your team from Dropbox to Nextcloud without losing files, breaking shared links, or derailing productivity.

Before diving into the technical migration steps, it helps to understand the full scope of what Nextcloud offers as a Dropbox replacement. The complete guide to replacing Google and Microsoft with Nextcloud covers Nextcloud's capabilities as a comprehensive productivity platform, well beyond simple file sync.

Understanding What You Are Migrating

Dropbox vs. Nextcloud: A Structural Comparison

Dropbox and Nextcloud handle files differently at a fundamental level. Understanding these differences prevents surprises during migration:

Pre-Migration Inventory

Run through this checklist before starting any data transfer:

• Total storage used: Check your Dropbox Admin Console for total team storage. This determines your Nextcloud storage requirements.
• Shared folder map: List every shared folder, who owns it, and who has access. Dropbox's Admin Console provides this under "Sharing" reports.
• External share links: Identify all active external share links. These will break after migration and need to be recreated in Nextcloud.
• Dropbox Paper documents: Paper docs need separate handling since they are not regular files in your Dropbox folder.
• Connected third-party apps: Any apps with Dropbox API access (Zapier, Slack integrations, etc.) will need reconfiguration.
• Dropbox Passwords and Vault: If your team uses these features, plan alternative solutions.

Preparing Your Nextcloud Environment

Server Requirements

Your Nextcloud server needs to accommodate all the data currently in Dropbox, plus growth headroom. For deployment architecture decisions, including whether to use Docker or bare metal, our Docker vs. bare metal deployment guide breaks down the trade-offs for different team sizes.

As a sizing guideline:

• Teams of 5-25: 4 vCPU, 8 GB RAM, storage = 1.5x current Dropbox usage
• Teams of 25-100: 8 vCPU, 16 GB RAM, dedicated database server, storage = 1.5x current usage
• Teams of 100+: Multiple app servers, load balancer, clustered database, object storage backend, storage = 2x current usage

Configure Group Folders Before Migration

Dropbox shared folders typically map to Nextcloud Group Folders. Set these up before migration so you can migrate data directly into the right structure:

1. Install the Group Folders app from the Nextcloud App Store.
2. Create Nextcloud groups that mirror your Dropbox sharing structure (e.g., "Marketing," "Engineering," "Finance").
3. Create Group Folders with appropriate permissions for each group.
4. Set quotas on Group Folders if you want to control storage allocation per team.

Migration Method 1: Rclone (Recommended)

Rclone is the most reliable tool for Dropbox-to-Nextcloud migration. It handles large file sets, supports resume on failure, and can run server-side for better performance.

Step 1: Install and Configure Rclone

# Install rclone
curl https://rclone.org/install.sh | sudo bash

# Configure Dropbox remote
rclone config
# Choose "New remote" > name it "dropbox" > select "Dropbox"
# Follow the OAuth2 authorization flow

# Configure Nextcloud remote (WebDAV)
rclone config
# Choose "New remote" > name it "nextcloud" > select "WebDAV"
# URL: https://your-nextcloud.example.com/remote.php/dav/files/USERNAME/
# Vendor: Nextcloud
# Enter username and password (or use an app password)

Step 2: Preview the Migration

Always run a dry run first to see what will be transferred and catch any issues:

# List top-level Dropbox structure
rclone lsd dropbox:

# Dry run to see what would be copied
rclone copy dropbox: nextcloud:/migrated-from-dropbox/ \
  --dry-run \
  --progress \
  -v

# Check for filename issues (Nextcloud has different character restrictions)
rclone check dropbox: nextcloud:/migrated-from-dropbox/ \
  --dry-run

Step 3: Execute the Migration

# Full migration with progress and logging
rclone copy dropbox: nextcloud:/migrated-from-dropbox/ \
  --transfers 4 \
  --checkers 8 \
  --progress \
  --log-file=/var/log/dropbox-migration.log \
  --log-level INFO

# For very large migrations, run in a screen/tmux session
tmux new -s migration
rclone copy dropbox: nextcloud:/migrated-from-dropbox/ \
  --transfers 4 \
  --checkers 8 \
  --progress \
  --stats 30s \
  --log-file=/var/log/dropbox-migration.log \
  --retries 3 \
  --retries-sleep 10s

Performance tip: If your Nextcloud server is hosted on MassiveGRID infrastructure, run rclone directly on the server rather than from an external machine. This avoids double-transferring data through your local network. Data flows directly from Dropbox's API to your server's storage.

Step 4: Verify the Migration

# Compare file counts
echo "Dropbox files:" && rclone size dropbox:
echo "Nextcloud files:" && rclone size nextcloud:/migrated-from-dropbox/

# Check for differences
rclone check dropbox: nextcloud:/migrated-from-dropbox/ \
  --log-file=/var/log/migration-check.log

Migration Method 2: Dropbox Export + Upload

For smaller teams or when rclone is not an option, you can export from Dropbox and upload to Nextcloud manually:

1. Download from Dropbox: Use the Dropbox desktop client to sync everything locally, or use the web interface to download folders as ZIP files (limited to 20 GB per download).
2. Upload to Nextcloud: Use the Nextcloud desktop client to sync the downloaded files, or use the web interface for drag-and-drop upload. For large uploads, the desktop client is more reliable.

This method is simple but has significant drawbacks for larger teams: it requires enough local disk space to hold all files, transfers are slower (data passes through the local machine), and there is no automated resume on failure.

Migrating Shared Folder Structures

Mapping Dropbox Shares to Nextcloud

Dropbox shared folders have a flat-ish model: someone owns a folder, shares it, and it appears in everyone's root. Nextcloud offers more options:

• Group Folders: Best for team-wide shared spaces (like "Marketing Assets" or "Engineering Docs"). Owned by the admin, not an individual user.
• User-shared folders: Best for ad-hoc sharing between individuals. Owned by the sharing user.
• External storage: Best for shared network drives or S3 buckets that need to appear inside Nextcloud.

Create a mapping document before migration:

Permission Mapping

Dropbox permissions are simpler than Nextcloud's. Map them as follows:

• Dropbox "can edit" maps to Nextcloud read + write + create + delete permissions.
• Dropbox "can view" maps to Nextcloud read-only permission.
• Dropbox does not have per-subfolder permissions within a shared folder. If you need more granular control in Nextcloud, this is an opportunity to improve your permission structure.

Handling External Share Links

This is the part that catches most teams off guard. Every Dropbox link you have shared externally (with clients, partners, in documentation, on websites) will stop working after migration. There is no way around this.

Strategy for Link Migration

1. Export all shared links: Use the Dropbox API or Admin Console to list all active shared links. The API endpoint /2/sharing/list_shared_links returns all links for a user.
2. Categorize by importance: Not all links need to be recreated. Focus on links shared with external parties, embedded in documentation, or used in automated workflows.
3. Create Nextcloud equivalents: For each important link, create a Nextcloud public share link. Nextcloud share links support passwords, expiration dates, and download-only restrictions.
4. Notify recipients: Send updated links to external recipients. For links embedded in documentation or websites, update those references.

For a feature that directly replaces Dropbox's file request functionality, see our guide on using Nextcloud File Drop as a WeTransfer and Dropbox alternative. This is particularly useful for teams that use Dropbox file requests for client uploads.

Dropbox Paper Migration

Dropbox Paper documents live outside the regular file system and require separate handling:

1. Go to paper.dropbox.com and export all documents. Paper supports export to .docx and Markdown (.md) formats.
2. For teams using Paper as a wiki, Markdown export is usually better since Nextcloud's built-in Text editor handles Markdown natively.
3. Upload exported documents to an appropriate folder in Nextcloud.
4. If you need rich document collaboration, use Collabora Online or OnlyOffice with the .docx exports instead.

Desktop Client Transition

Deploying the Nextcloud Desktop Client

The Nextcloud desktop client is available for Windows, macOS, and Linux. For managed deployments:

• Windows: Deploy via MSI installer through Group Policy, SCCM, or Intune. The client supports /S silent install and can be preconfigured with the server URL.
• macOS: Deploy via .pkg installer through MDM (Jamf, Mosyle, etc.). The client can also be installed via Homebrew: brew install --cask nextcloud.
• Linux: Available through most package managers. AppImage is available for distributions without native packages.

Configuring Selective Sync

If your team used Dropbox Smart Sync (placeholder files), configure Nextcloud's Virtual Files feature. This is available on Windows and experimentally on other platforms. It shows all files in the file manager but only downloads them when opened, saving local disk space.

Removing the Dropbox Client

Do not remove the Dropbox client until the migration is verified and users are comfortable with Nextcloud. A suggested timeline:

1. Day 1: Install Nextcloud client alongside Dropbox.
2. Week 1: Users work primarily in Nextcloud, use Dropbox as read-only reference.
3. Week 2: Pause Dropbox sync (do not uninstall yet).
4. Week 3-4: Uninstall Dropbox client after confirming all files are accessible in Nextcloud.

Mobile App Transition

The Nextcloud mobile apps (iOS and Android) provide file access, auto-upload for photos, and Talk integration. Key differences from the Dropbox mobile app:

• Auto-upload: Nextcloud supports automatic photo/video upload, similar to Dropbox Camera Upload. Configure this during onboarding.
• Offline files: Users can mark files as "available offline" in the Nextcloud app, similar to Dropbox's offline access feature.
• File widget: Both iOS and Android offer home screen widgets for quick file access.

Post-Migration Verification Checklist

After completing the data transfer, work through this verification checklist before declaring the migration complete:

1. File count comparison: Total files in Nextcloud should match Dropbox (minus any intentionally excluded files).
2. Storage size comparison: Total storage used should be within 5% of the Dropbox total (small differences are normal due to metadata handling).
3. Shared folder access: Verify that every team member can access their expected shared folders/Group Folders.
4. File opening: Spot-check that documents open correctly, especially Office files, PDFs, and images.
5. Desktop sync: Confirm the Nextcloud client is syncing without errors on at least one machine per OS type.
6. Mobile access: Verify the Nextcloud mobile app connects and shows files correctly.
7. External shares: Test all recreated external share links.
8. Search: Test Nextcloud's search functionality to ensure the full-text search index has been built.

Common Issues and Troubleshooting

Filename Conflicts

Dropbox allows some characters in filenames that Nextcloud (or the underlying filesystem) may not. Common issues include trailing spaces, leading dots on Windows, and certain Unicode characters. Rclone will flag these during the dry run. Fix them in Dropbox before migrating, or use rclone's --fix-case flag for case-conflict resolution.

Large Files Failing to Upload

If large files fail during transfer, check your Nextcloud server's PHP and web server configuration:

# In php.ini
upload_max_filesize = 16G
post_max_size = 16G
max_execution_time = 3600
max_input_time = 3600

# In nginx.conf (if using Nginx)
client_max_body_size 16G;
fastcgi_read_timeout 3600;

Slow Sync Performance

If the Nextcloud desktop client syncs slowly after migration, the server may be overwhelmed by the initial sync storm (all clients syncing simultaneously). Stagger the rollout: deploy the desktop client to 10-20 users per day rather than everyone at once.

Dropbox Business License Cancellation

Keep your Dropbox Business subscription active for at least 30 days after the migration cutover. This gives you a safety net to recover any files that were missed or verify data. After 30 days, export a final backup (just in case), then cancel. Note that Dropbox retains data for a limited period after cancellation, but do not rely on this as your backup strategy.

Next Steps After Migration

Once your files are migrated and your team is using Nextcloud, you are only getting started. Nextcloud offers capabilities that go well beyond what Dropbox provides. Explore Nextcloud Talk for internal communication, Nextcloud Deck for project management, and Nextcloud Forms for data collection. If you migrated from Dropbox as part of a larger move away from a full productivity suite, our guide on migrating from Microsoft 365 to Nextcloud covers the additional components like email, calendar, and contacts.

The key to a successful migration is not just moving files; it is ensuring your team feels confident in the new platform. Take the time to set up the environment properly, verify everything, and support your users through the transition. The result is a file platform you fully control, with no per-user licensing fees eating into your budget and no vendor making unilateral decisions about your data.