How to export your data from Dropbox

How to export your data from Dropbox: what moves and what stays behind

Files can be copied out of Dropbox through the browser for small folders or through the desktop app for large ones, but sharing links, permissions, comments and version history do not carry over as-is. If your renewal, a pricing change, a data residency requirement or lock-in is pushing you to leave, treat this as a file copy, not a platform migration. Dropbox lets you download a folder from dropbox.com as a .zip file only when it is under 250 GB uncompressed and holds fewer than 10,000 files, and Dropbox recommends the desktop app for large downloads. Those documented limits decide the method: sort your folders by size and file count before you start, and assign the large ones to the desktop app sync rather than the browser.

Browser downloads give you a point-in-time snapshot. Dropbox notes that a downloaded copy does not update when the original changes, unlike files synced through the desktop or mobile app, so freeze writes to the source folders or run a final delta sync before cutover. Shared links, folder invitations, per-person permissions and comment threads are not exported as files, and version history is not in the folder download either. Before you delete anything, record who has access to each shared folder, which links are public, and which file versions your compliance or legal team needs to keep, and confirm with Dropbox how your account's version history and deleted files can be retrieved during the window you plan to use.

Plan the rebuild as a separate task. Your target platform will need its own sharing model, group membership, retention rules and user accounts, and someone must recreate them from the inventory you took. Ask any implementation partner for a written list of what the export will and will not carry, and verify a sample folder end to end by checking file counts, sizes, modified dates and permissions on the destination before you migrate the next team.

Which Dropbox data can be exported and by which method

This table compares the main ways to get files out of Dropbox, with the format and documented limits for each. Read it by matching your data type to a row, then checking the limit column before choosing a method. A downloaded copy does not update when the original changes, so re-export or re-sync if files are still being edited in Dropbox.

Data type	Export method	Format	Documented limits
Single files or small folders	Browser download from dropbox.com	Original file or .zip for folders	Folders must be under 250 GB uncompressed and hold fewer than 10,000 files
Large folders or full team data	Desktop app sync or copy to local disk	Original files and folder structure	No folder size or file count limit is documented for the desktop app; Dropbox recommends it for large downloads
Folders above browser limits	Split into subfolders, then download each as .zip	.zip per subfolder	Each subfolder must still meet the 250 GB and 10,000 file limits
Files available offline on mobile	Mobile app offline copy or share to device storage	Original file format	Covers only files you have marked for offline access; confirm coverage in your Dropbox plan
Files already synced to a computer	Copy from the local Dropbox folder	Original file format	Limited to what has synced locally; check for files still marked online-only
Downloaded copies	Any browser or app download	Point-in-time copy	Does not update when the original in Dropbox changes, unlike files kept in sync through the desktop or mobile app
Sharing links and permissions	Not included in file downloads	Not exported	Recreate shares, link settings and member access in the destination system
Version history	Not included in standard downloads	Not exported as versions	Only the current version of each file is typically copied; confirm retention needs with your Dropbox admin before cutover

Choosing between browser download and the desktop app

Browser downloads suit a folder that is small enough for Dropbox to package on request. On dropbox.com, a user can download a folder as a .zip file when the folder is under 250 GB uncompressed and holds fewer than 10,000 files. Dropbox packages the archive on its side, so the work is a single download with no client software to install. The trade-off is that the result is a snapshot, not a synchronized copy.

Speed to first result: A single folder can be pulled in one step, which suits a quick handover or a one-off archive.
Snapshot behavior: A downloaded copy does not update when the original changes, so later edits in Dropbox will not appear in the archive.
Limit checks: Check both the 250 GB and 10,000 file thresholds before downloading, because a folder over either limit cannot be exported this way.
Archive handling: Large zip files can be slow to finish and fail partway, so verify the file count and size after download.
Sharing context: The zip holds file contents only, not sharing links or permission settings.

Before relying on a browser download, confirm the folder's current size and file count in Dropbox and compare them with the archive contents.

What does not carry over from Dropbox and how to handle it

A downloaded copy keeps the bytes but not the context around them. Sharing links, permissions, comments, version history and admin settings all live in Dropbox's service, so they need their own export step. Record them before you cut off access, or the team will find out after the migration.

Sharing links

A shared link is a URL that Dropbox resolves on its own servers, so it stops working once the files leave Dropbox. Before you download anything, export or write down the list of shared links, their target folders and their password or expiry settings, using the sharing views in the Dropbox web interface and admin console. Map each link to its new location in the target system so people know where to go. Confirm with Dropbox's current documentation which link metadata, if any, can be exported in bulk.

Folder and file permissions

Who can view, edit or comment on a folder is stored as Dropbox sharing membership, and a copy inherits none of it. The file system copy simply gives the person running the download access to the bytes. Build an access inventory from the admin console and from each shared folder's member list, recording the group, user and role for every folder. Use that inventory to recreate the same structure in Nextcloud, and check for members who left the company but still hold access.

Comments and activity

Comments on files and the activity feed are application data, not file content. A download preserves neither, so a discussion attached to a contract or design file will be lost unless you record it. Decide which threads matter for audit or ongoing work, then export or screenshot them with dates and authors before the source is retired. Confirm with Dropbox what its activity and comment views can export for your plan, since the scope differs between plan types.

Version history

A download gives you the current version only. Earlier versions remain in Dropbox for a limited recovery window that depends on your plan, so older revisions can disappear if you wait. Decide which files need their history kept, download specific prior versions where Dropbox allows it, and store them in a dated archive folder with the version date in the name. Ask Dropbox to confirm the recovery window that applies to your account before you plan the cutover date.

Team and admin settings

Retention policies, device approvals, two-step verification, single sign-on configuration and team membership exist only inside the Dropbox admin console. None of them move with the files. Capture the settings you rely on in a written configuration record, including which SSO provider is connected and which compliance holds are active. Keep the console export or screenshots with the access inventory, and confirm which legal hold or retention obligations must be met before you delete anything.

The sequence for a complete Dropbox export with verification

This sequence moves every folder out of Dropbox into a staging location, confirms the copy matches the source by counts, sizes and sample checksums, and only then allows any deletion. The result is a documented, verified archive you can hand to a migration team or keep as a fallback.

Inventory folders against the download thresholds
Before moving anything, list every top-level folder in the account and record its size, file count and owner. Mark any folder that is over 250 GB uncompressed or holds 10,000 or more files, since those cannot be downloaded from dropbox.com as a single .zip. Ask the account owner or a Dropbox admin to confirm the team's folder list, including team folders the export account may not see by default. The output is a signed-off inventory spreadsheet that every later step checks against.
Choose the transfer path for each folder
Assign each folder to a path. Folders under both thresholds can be downloaded from the web as a .zip, while larger folders should go through the Dropbox desktop app, which Dropbox recommends for large downloads. Record the decision next to each folder in the inventory, along with who will run the copy. Note that a browser download is a one-time snapshot that does not update when the original changes, so folders still in use need the sync path. The output is a path assignment for every folder.
Prepare a staging location with enough free space
Create a dedicated staging directory on storage that is not part of the Dropbox sync tree, and confirm it has free capacity above the total size in the inventory. Keep the path structure identical to Dropbox so later comparisons are straightforward. Check that the storage is encrypted and that access is limited to the people running the export. The output is a staging location with a documented path, owner and free-space figure recorded in the inventory.
Set the cutoff and ask users to pause changes
Choose a cutoff time and tell every team member that edits made after it may not reach the export. Decide whether to freeze writes to the affected folders for the copy window, or to run a second delta pass after the first copy. Record the cutoff time in the inventory and the change log. Remember that sharing links, permissions and version history are not carried in a plain file copy, so capture them separately now. The output is a written cutoff time and a list of folders that were frozen or flagged for a delta pass.
Run the copy and log every failure
Start the browser downloads and desktop app syncs according to the path assignments. Let the desktop client finish its full sync before counting, because a partly synced folder will look like missing data. Keep a log of errors, skipped files, paths longer than the destination supports and files that failed to download. Re-run failed items individually rather than assuming the batch completed. The output is a copy log with a status for every folder and a list of exceptions to resolve.
Verify counts, sizes and sample checksums
Compare the staged copy with the source folder by folder. Match the file count and total byte size against the inventory, then compute checksums on a random sample of files, weighted toward large files and recently edited ones, and compare them with checksums taken from the synced source copy. Any mismatch is re-copied and re-checked. The output is a verification report that states, for each folder, what matched and what was re-run.
Hold deletion until the verification is accepted
Do not remove or deprecate any Dropbox content until the verification report has been reviewed and accepted in writing by the data owner and the person accountable for retention. Keep the staging copy and the report together, and record where the sharing links, permissions and version history inventory lives. Confirm with your legal or records team whether retention rules apply before any deletion. The output is a written acceptance record that authorizes the next step, which is either migration or archival.

How to verify that the copy is complete

A browser zip that opens is not proof of completeness. Dropbox's download of an entire folder only works for folders under 250 GB uncompressed with fewer than 10,000 files, and a zip can unpack cleanly while still missing files, dropping empty folders or carrying the wrong modification dates. Verification means comparing the source and the copy on four things: file count, total bytes, folder structure and modification dates. Run the same count on both sides, for example by listing every file with its size and last-modified time from the Dropbox desktop app's synced folder and from the destination, then sort both lists by path and diff them. Any mismatch in path, size or date is a file to investigate before the source is retired.

Keep a manifest of paths and hashes for every transfer. Generate it once from the source copy, with a checksum such as SHA-256 for each file, and store it outside the destination so it can be checked later. The manifest lets you prove which files were copied and detect silent corruption, which file counts and sizes cannot catch. Confirm with your own administrators where the manifest will be kept and who can access it, because it lists the paths and structure of sensitive business data.

Plan a second sync pass before cutover. Files edited in Dropbox after the copy began will not appear in the first export, and a downloaded copy never updates when the original changes. Repeat the comparison against the manifest for files modified since the first pass, then freeze writes on the team folders for a short agreed window and run one final delta check. Record the result of each pass, including any files you chose to exclude and the reason, so the completeness claim can be reviewed later by an internal auditor or an independent assessor.

What to plan before the Dropbox contract ends

Leaving Dropbox is less about the download itself and more about the decisions that come before it. Each card below is a point where a gap in planning becomes lost links, missing files or a compliance problem, so confirm each item with Dropbox and your own legal team before the notice period starts.

Export window and retention

Ask Dropbox how long your account, deleted files and version history remain available after the subscription ends, and whether that window can be extended for a bulk export. Browser downloads are capped at folders under 250 GB with fewer than 10,000 files, so the desktop app will carry most of the transfer. Plan the export backward from the last day you can still access the account.

Who owns the copy

Decide who on your side is accountable for the exported data once it leaves Dropbox, including who holds the admin role, where the copy is stored and who approves deletion of the original. Confirm with Dropbox which account owns team-owned folders and whether a departed user's files need to be transferred first. Without a named owner, exports tend to end up as unmanaged copies on laptops.

Shared links and permissions

Shared links, folder invitations and group permissions do not carry over to another system. Build an inventory of shared folders and external collaborators from the admin console, and map each one to a target group or share in the destination before cutover. Ask Dropbox what reporting its admin tools provide, since a missing inventory is the most common reason access breaks silently.

Version history expectations

A downloaded file is a point-in-time copy, and older versions are not included unless you retrieve them separately. Decide which version history your teams need, which files are legally significant, and whether the destination will keep history for them. Confirm with Dropbox how far back version history is retained for your plan, because that window sets what you can recover.

Notice to users

Users need written notice of the change date, the cutoff for editing in Dropbox, and what they must move themselves, such as personal folders and links they have sent outside the company. Set the notice period against the contract terms you confirm with Dropbox, not against an assumed date. Name a contact for questions so that late-stage requests do not go to shared inboxes.

Legal and records holds

Check whether any litigation, regulatory or records-retention obligation covers data stored in Dropbox before you delete anything. A hold can require preserving the original files, metadata and version history, and deleting the account may not satisfy it. Ask your legal and compliance teams to confirm the holds in writing, and ask Dropbox how it handles data preservation requests during account closure.

Questions teams ask before exporting from Dropbox

How long does a Dropbox export take?

No single figure applies, because duration depends on total data volume, file count, your upstream bandwidth and how many files change during the transfer. Browser downloads are capped: Dropbox only builds a .zip of a folder under 250 GB uncompressed holding fewer than 10,000 files, and it recommends the desktop app for larger downloads. Before you plan a window, measure the size and file count of each top-level folder, run a test transfer of one representative folder, and time it on the network you will actually use. Ask your team to freeze major edits during the cutover so the copy you verify is the copy you keep.

What effort does an export need from IT and team owners?

IT handles the technical work: installing the desktop app on a machine with enough disk space, running the transfer, checking file counts and sizes, and storing the copy on a target you control. Team owners handle the business side: confirming which folders are current, deciding what to archive, and checking that their files opened correctly after the copy. Effort grows with the number of shared folders, the number of people who own content, and how much history you need to keep. Agree on a named owner for each team before the first transfer starts.

Can our own team export from Dropbox without outside help?

Yes, for a small, simple account. The desktop app and the browser download path are available to any user with access to a folder, so a team with a few folders under the browser limits can usually handle the copy internally. Outside help becomes more useful when folders exceed the browser limits, when you need to verify large numbers of files, when permissions must be mapped to another system, or when the export must be documented for an audit. Ask Dropbox about your plan's administrative export options as well, because admin capabilities differ by plan.

What does a fixed-scope DeployOpen engagement cover for a Dropbox export?

DeployOpen plans, implements, documents and supports self-hosted open-source platforms inside your own infrastructure. For an export project, a fixed-scope engagement would typically define which accounts and folders are in scope, the target storage, the transfer method, the verification steps, and the handover documentation. Scope, deliverables and timelines are agreed in writing before work starts, and the quote follows from that written scope. Ask for the list of deliverables, the verification method, and what is excluded, such as link recreation or client rollout, so the boundaries are clear before you sign.

What happens to sharing links and permissions during an export?

Sharing links and permissions do not carry over when you download files. Dropbox does not export the link structure or who had access, so you must record shared folders, members and link settings before you leave. A downloaded copy also does not update when the original changes, so links and copies can drift apart. Build an inventory of shared folders and their members, decide which people need access in the new system, and recreate those permissions there. Communicate new links to recipients before you retire the old ones.

What about version history and deleted files?

A standard download gives you the current version of each file, not its earlier revisions. If version history matters for legal, compliance or business reasons, decide in advance which versions to keep and how you will retrieve them, because the browser and desktop downloads do not automatically include the full history. Confirm your plan's version and recovery windows with Dropbox, and confirm with your compliance lead whether a copy of the current state is enough. Record the export date and what was included in your retention documentation.

Where should the exported data go, and how do we keep it secure?

Choose a destination you control, such as a managed server or cloud account inside your own boundary, and restrict access to it before transfer begins. Exported files carry the sensitivity of their source, so apply the same access groups, encryption and logging you use elsewhere. Confirm with your security team which storage and encryption standards apply, and check that the destination meets any data residency rules your organization follows. Remove temporary copies from laptops once the transfer is verified.

How DeployOpen scopes and delivers a Dropbox data exit

DeployOpen treats a Dropbox data exit as a fixed-scope engagement inside your own infrastructure. We agree in writing which folders, accounts, sharing links and version histories are in scope, then build, verify and document the transfer so your team can confirm what arrived and what did not.

How we scope

Inventory team folders, personal accounts and folder sizes against the 250 GB and 10,000 file browser download limit
Record which sharing links, permissions and version histories must be rebuilt or archived instead of copied
Agree deliverables, timelines and acceptance checks in writing before any transfer work starts

How we build

Set up the desktop app transfer path and target storage inside your own cloud account or data center
Run test transfers on sample folders and compare file counts, sizes and modified dates with the source
Build a per-folder export manifest that lists owners, paths, checksums and any items that need manual handling

How we hand over

Document the export procedure, known gaps and the list of links and permissions to recreate by hand
Deliver reconciliation reports showing what transferred, what failed and how each exception was resolved
Walk your administrators through the runbook so they can repeat or audit the process after handover

How we support

Offer ongoing support, upgrades and continuous testing as a retainer after the exit is complete
Keep the export evidence and manifests available for your internal audit or compliance review
Confirm with your auditor which records they need, since DeployOpen prepares evidence but does not issue attestations

How to export your data from Dropbox