Migrate from Dropbox to Seafile

How to migrate from Dropbox to Seafile without losing team access

If your Dropbox renewal, licensing change or data residency requirement has pushed you toward self-hosting, the migration is two jobs at once: a data move and a re-modeling of Dropbox folders and sharing into Seafile libraries and permissions. The file content transfers cleanly. Shared links, group permissions and version history do not follow automatically, so they need a plan before anyone is cut over. In most organizations an IT or platform engineering team owns the work, often with an implementation partner for the server build, the identity integration and the cutover. Effort and risk are driven mainly by how many team folders you have, how much data sits in each, and how many external links are in active use.

Start by inventorying Dropbox before copying anything. Export a list of team folders, their owners, member groups and external shared links, and note which libraries will need their own encryption password. Seafile libraries are the unit of sync, sharing and optional per-library encryption, so a Dropbox team folder that mixes confidential and general material should be split first. For data volume, the Dropbox browser download limits do not apply to the desktop app, so bulk copies should go through the desktop client or a scripted transfer rather than zip downloads. Confirm the copy method, transfer windows and checksum or file count checks with your partner in writing before the first run.

Plan the cutover by team, not all at once. Recreate groups and roles in Seafile, connect LDAP or Active Directory or your SAML 2.0 identity provider if you need single sign-on, and then reissue shared links from the new server. Tell users that Dropbox version history will stay in Dropbox unless you archive it separately, and decide whether a read-only Dropbox period is acceptable. Keep the Dropbox account active until audit and retention needs are confirmed. Check the Seafile admin manual for the current SSO and sharing options, and confirm which Professional Edition features your environment requires before you commit to a licensing path.

Which Dropbox features map to Seafile and which need rework

This table maps the Dropbox capabilities a team relies on to their Seafile equivalents and marks each as clean, needs rework or gap. Read the status column first, then check the notes on libraries, encryption and Professional Edition features, since those decide how much of your current setup carries over.

Dropbox feature	Seafile equivalent	Status and what to plan
Team folders and sync	Libraries synced by desktop and mobile clients	Needs rework: each Dropbox team folder usually becomes its own library, so sync scope and permissions must be re-planned per library.
Shared folders and sharing links	Library sharing to users or groups, and share links	Needs rework: recreate shares by hand or by script, and check link expiry and password settings against your current policy.
Per-folder permissions	Library-level roles and permissions	Clean for basic read and write access; Professional Edition adds role-based permissions for finer control.
Version history and file recovery	Library history and restore from trash	Needs rework: old Dropbox version history does not carry over, so confirm retention settings and export needs before cutover.
Admin controls and reporting	Admin panel and user management	Needs rework: map your Dropbox admin policies to Seafile settings and confirm which audit reports your compliance team requires.
Single sign-on	LDAP or Active Directory, and SAML 2.0 in Professional Edition	Clean with LDAP or AD; SAML 2.0 requires Professional Edition, so confirm your identity provider setup.
Malware scanning	ClamAV virus scanning in Professional Edition	Clean in Professional Edition; Community Edition setup should be confirmed with your own security team.
Online document editing	ONLYOFFICE or Collabora Online integration	Needs rework: Seafile integrates with ONLYOFFICE or Collabora Online, which you install and license separately from Seafile.
Multi-tenancy and clustering	Professional Edition features	Gap for small teams: only needed at scale, and availability depends on your edition and deployment.

Migration sequence from inventory to Dropbox decommission

This sequence moves team files from Dropbox into Seafile in controlled stages, so each library is validated and signed off before its owners stop using Dropbox. Each step produces a written artifact that the next step depends on.

Inventory folders, sizes and owners
List every Dropbox team folder, its approximate size, file count, owner, members and the teams that depend on it. Record which folders hold regulated or restricted data, which have external sharing links, and which are used daily. Ask Dropbox admins to export the membership and sharing reports they can access, and confirm with each owner what must be kept. The output is a folder inventory that becomes the folder-to-library map, with one proposed Seafile library per folder and a named owner for each.
Stand up a pilot Seafile server
Install Seafile Community Edition 12.0.14 on a test host, or choose another supported install path from the Seafile admin manual, such as the Docker single-node setup. Connect the storage backend you plan to use in production, configure HTTPS, and confirm that LDAP or SSO settings match your identity provider if you plan to use them in the pilot. Test an account login and a desktop client sync. The output is a working pilot instance with a documented version, install method and configuration record that the security team has reviewed.
Validate a pilot library set
Choose two or three low-risk folders from the inventory and create a library for each. Where a library needs per-library encryption, set its password and record where the password is stored and who can recover it, because a lost password cannot be recovered by the administrator. Copy the files with the desktop clients, then compare file counts, sizes and modification dates against the Dropbox source. Test sharing, a restore of an older version and a share to an external user. The output is a validated pilot with a written test log and a list of defects to fix before production.
Run the production instance in parallel
Deploy the production Seafile environment with the storage, backup and access controls defined during the pilot. Migrate the libraries from the map in batches, syncing each batch through the desktop clients or a bulk transfer approach that the team has tested. Keep Dropbox read-write during this period and run a daily reconciliation of changed files between the two systems for each library. The output is a production instance and a reconciliation log showing that every library in the first batches matches its source.
Cut over team by team
For each team, schedule a window in which its members stop editing in Dropbox, the final delta sync completes, and the team signs into Seafile with its own accounts or SSO. Recreate shared links and permissions for that team's libraries and tell members which links changed. Keep the Dropbox folder read-only for a fallback period set by the business. The output is a per-team cutover record listing the date, final reconciliation result, recreated shares and the named team lead who confirmed working access.
Verify restores and close access
Before the final cutover, confirm that backups of the Seafile libraries can be restored to a test location and that the restored files open correctly. Confirm the business has accepted any items that did not carry over, such as Dropbox version history beyond what Seafile retains and links that cannot be recreated. Remove users from Dropbox team folders and revoke external links, then review the Dropbox admin console to confirm no active sharing remains. The output is a restore test record and a list of accepted exceptions.
Decommission Dropbox and sign off
After the agreed fallback period, export a final copy of any folder the business requires for records, then cancel or downgrade Dropbox team licenses according to your contract terms. Review the contract's notice and data retention terms with procurement and legal before you cancel. Collect sign-offs from the data owners, security, and the IT lead. The output is a signed decommission record that lists each library, its owner, the final export location and the date Dropbox access ended.

Moving files, users and integrations out of Dropbox

Moving a Dropbox team to Seafile is less a single transfer than four separate jobs: copying the bytes, mapping folders to libraries, reconnecting identities, and rebuilding the sharing and integrations that Dropbox held for you. Each card below covers one of those jobs and the decision or check that comes with it.

Desktop app for large transfers

The Dropbox desktop app syncs the full folder tree to a local disk, which is the reliable copy path once folders grow beyond what a browser download handles. Run the sync on a machine with enough free space for the largest team folder and confirm every file has finished downloading before you treat it as a source. Expect the transfer to be limited by bandwidth and local disk rather than by Dropbox limits, and keep the original Dropbox account untouched until the cutover is signed off.

Browser downloads and their hard limits

Browser folder downloads from dropbox.com only work for folders under 250 GB uncompressed with fewer than 10,000 files. Use them only for small, self-contained folders such as archived project sets, and check the file count before you start, because a folder that fails partway gives you a zip you cannot trust as complete. Anything above either limit belongs in the desktop app or the bulk path.

Bulk transfer for larger sets

For very large or long-lived archives, plan a bulk transfer that copies data straight into the Seafile server storage or into a staging area, then imports it into libraries. Confirm with your Seafile partner or the admin manual which import procedure matches your version and storage backend, and test it on one library first. Budget a verification pass that compares file counts and sizes per library, since bulk tooling rarely carries Dropbox metadata across.

LDAP, AD and SAML sign-in

Seafile supports LDAP and Active Directory integration and several single sign-on options, and SAML 2.0 is a Professional Edition feature. Decide before migration whether users sign in with directory credentials or a separate local account, because switching later changes who owns each library. Map Dropbox team roles to Seafile roles and permissions on paper first, then test sign-in with a pilot group.

Per-library encryption tradeoffs

Seafile libraries can each be encrypted with a password chosen by the user. That protects content at rest from administrators who do not hold the password, but the server cannot index, preview or scan encrypted content, and a lost password means the library is unrecoverable. Decide per library which data needs this, document who holds each password, and confirm with the vendor how server-side features such as search and ClamAV scanning behave on encrypted libraries.

Rebuilding shared links and integrations

Dropbox shared links, folder permissions and third-party app connections do not move with the files. Inventory every shared link and connected app before cutover, recreate the shares as Seafile library permissions, and reconnect integrations such as document editors through Seafile's documented extensions, including online office integration with Collabora Online. Tell recipients which old links will stop working and on what date.

How the Seafile migration differs by team size and starting point

Seafile Professional Edition can run without a license file for up to 3 users, so a very small team can start with the Professional feature set at no license cost. The migration is mostly about getting a single node running reliably and moving a short list of shared folders. Because the team is small, the main decisions are which Dropbox folders become libraries and who holds the administrator role.

Licensing: Confirm that the user count stays at or below 3 before you plan around the no-license mode, and recheck it whenever you add a person.
Deployment: A Docker single-node setup, documented in the admin manual, is usually enough for a team this size.
Library layout: Map each Dropbox top-level folder to one library, and keep the number of libraries small so that sharing stays easy to audit.
Transfer: Use the desktop client to upload each library from a machine that already holds a synced copy of the Dropbox data.
Ownership: Name one administrator and one backup administrator before cutover, so that a single person does not hold the only access to the server.

Before you start, check the current user count and the Seafile admin manual for the limits that apply to the edition and version you plan to install.

Mapping Dropbox folders to encrypted Seafile libraries

The key decision in this migration is how to turn Dropbox team folders into Seafile libraries. Each library syncs separately and can be encrypted with a password chosen by the user, so a Dropbox tree that holds mixed sensitivity data should be split into several libraries before the first copy. Decide per library whether encryption is needed, based on what the data is and who must reach it. Encrypted libraries protect data at rest from anyone without the password, including administrators, but that protection has consequences you must plan for before cutover.

The main consequence is recovery. The library password is not something Seafile administrators can reset for users, so a lost password can mean lost data. Record who holds each library password, how it is stored and what happens when a team member leaves. Also confirm with the Seafile admin manual, Seafile admin manual, how password changes, library recovery and server-side handling of encrypted libraries work in the version you deploy. Test these procedures on a sample library, not on migrated business data.

Encryption also limits some features. Server-side functions such as full-text search, previews and online office editing may behave differently or be unavailable on encrypted content, so confirm each one in your test environment before you assign a library to a team. Sharing works differently too: a link or share to an encrypted library needs the recipient to know the password, which replaces Dropbox's simpler link model. Map each Dropbox shared folder to a library, list the people who need access, and decide whether those permissions should live in Seafile's own roles or in your directory group structure.

What drives the cost and duration of a Dropbox to Seafile move

What is the main driver of how long a Dropbox to Seafile move takes?

Total data volume and file count set the transfer time, and they are the first thing to measure. A move of a few hundred gigabytes with a modest number of files is mostly a bandwidth and verification exercise, while a large archive with millions of small files adds sync time, error handling and checksum passes. Ask for an inventory of folders, sizes and file counts per team before agreeing on any schedule. Browser downloads from Dropbox are limited to folders under 250 GB with fewer than 10,000 files, so large teams usually move through the desktop app or a bulk process, which takes longer but is more predictable.

How do the number of libraries and owners change the effort?

Each Dropbox team folder usually maps to one Seafile library, and each library needs an owner, permissions and a sync decision. More libraries means more mapping work, more sharing rules to recreate and more client setup for users who sync several of them. Ownership matters too: files owned by departed staff need to be reassigned before the move, or they arrive without an accountable owner. Ask for a mapping table that lists each source folder, its target library, the owner and the people who need access, because that table drives most of the planning effort.

Does AD or SSO scope change the cost of a Seafile deployment?

Yes, because identity integration is set-up work that is done once but touches every user. Seafile supports LDAP and Active Directory integration and several single sign-on options, and SAML 2.0 is listed as a Professional Edition feature. Costs rise when the directory is messy, when groups must map to Seafile roles, or when several identity sources must coexist during cutover. Confirm which directory is the source of truth, which groups grant library access, and whether SAML is required, since that choice decides which edition and which identity provider work is needed.

How do encryption decisions affect the move and ongoing operations?

Per-library encryption protects data at rest with a password chosen by the library owner, which is a strong control but adds operational weight. Encrypted libraries cannot be indexed or previewed server side in the same way, and a lost password means the data cannot be recovered, so password custody must be designed before the first library is created. Encrypted and unencrypted libraries also need different handling in search, online office integration and any virus scanning. Decide per library which data needs this protection, document who holds the passwords, and include that process in the training and runbook budget.

Which storage backend choice changes the recurring cost the most?

Storage backend selection is the largest recurring cost lever after staff time. The Seafile manual documents S3, Ceph and OpenStack Swift as storage options, and each has different hardware, licensing and operations demands. Object storage from a cloud provider bills by capacity and requests, while Ceph needs a cluster you run yourself. Ask for a capacity forecast for three years, including growth and version retention, and compare the cost of object storage in your own region with the cost of existing SAN or NAS capacity. The chosen backend also determines how backups and replication are done.

When does Seafile Professional Edition licensing add cost?

Seafile Professional Edition runs without a license file for up to 3 users, per the Seafile download page, so the licensing cost begins once the user count goes above that limit. Professional features such as SAML 2.0, cluster deployment, multi-tenancy, role-based permissions, ClamAV virus scanning and advanced file search are included in that edition, so teams above 3 users should confirm the license terms with Seafile before planning the budget. Community Edition is free to run but lacks those features. Ask for a written list of which features your requirements need, then match them to the edition.

Which backup and high availability choices add one-time and recurring costs?

Backup and high availability are where a pilot-sized deployment becomes a production system, and they add cost in both categories. One-time work includes designing the backup target, restore tests and failover architecture, which Seafile supports through cluster deployment for Professional Edition. Recurring costs include backup storage, replication bandwidth, monitoring and the staff time to test restores on a schedule. A regulated team should expect restore testing to be part of the design, not an afterthought. Ask any implementation partner for the backup and restore procedure and the test evidence that proves it works, and price those items separately from the initial build.

How much staff time does the client rollout take, and who pays for it?

Client rollout is often the largest hidden cost, because each user must install the desktop client, select libraries, resolve conflicts and learn the new sharing model. Seafile provides desktop clients under GPLv2 and mobile clients for iOS and Android, so the software is free, but IT staff, team champions and training time are not. Plan a pilot team first, then one team at a time, and budget for help desk tickets during each wave. Recurring costs continue after cutover through support and operations, so ask for a rollout plan that separates one-time migration, pilot and training from ongoing hosting, storage, support subscriptions and operations.

What usually goes wrong and how to prevent it

Most failed Dropbox to Seafile moves do not fail on copy speed. They fail on the things Dropbox did implicitly: links, permissions, passwords and the habits of people who keep working in the old tool. Each card below names one risk, why it hurts a team cutting over library by library, and the check that catches it before users notice.

Lost sharing links

Dropbox share links do not move with the files. Anyone who bookmarked, emailed or embedded a Dropbox link will hit a dead end after the cutover, and external partners often do not know the link changed. Build an inventory of active shared links from the Dropbox admin console before cutover, then republish the important ones from Seafile as share links with the expiry and password settings you intend. Confirm with each owner which links must keep working.

Mismatched permissions after SSO

Seafile can integrate with LDAP, Active Directory and several single sign-on options, but group membership in your identity provider does not automatically match the folder access people had in Dropbox. A user who signs in through SSO may land in a library they should not see, or miss one they need. Map each Dropbox team folder to a Seafile group, test with one account per role, and review the library owner and sharing permissions before you open the library to the whole team.

Sync conflicts during parallel run

If people keep editing in Dropbox while a copy runs in Seafile, the two versions drift apart and sync clients create conflicted copies in both places. Reconciling them by hand is slow and error-prone. Pick a cutover date per library, freeze writes to the Dropbox folder for the final copy, and run a last delta sync before you tell users to switch. Keep the parallel period short and documented, with a named owner for each library.

Encrypted library passwords lost

Seafile libraries can each be encrypted with a password chosen by the user, and Seafile does not give administrators a way to recover that password. A library whose password is forgotten or stored only in one person's head becomes unreadable, including its history. Decide which libraries really need client-side encryption, record each password in your enterprise password manager under a named owner, and test the unlock flow on a copy before you rely on it.

Browser download limits hit by large folders

Dropbox only lets users download a folder from the web as a .zip when it is under 250 GB uncompressed and holds fewer than 10,000 files. Teams that try to pull large archives through the browser will hit these limits partway through, or end up with partial copies that look complete. Use the Dropbox desktop app for large folders, compare file counts and total sizes on both sides after each transfer, and keep a checksum or file list for the audit trail.

Users writing to Dropbox after cutover

After cutover, some people will keep saving to the old Dropbox folder, bookmarks and mobile apps will still point there, and automated jobs may keep writing to it. Files then exist in two places with no single owner. Remove Dropbox from managed devices where your policy allows, redirect or rename the old folders to read-only where possible, update scripts and integrations, and check access logs for a few weeks to find stragglers.

Questions buyers ask before moving from Dropbox to Seafile

How much effort does a Dropbox to Seafile move take, and who does the work?

The effort depends on how many libraries you map, how much data sits in Dropbox, and how many people you have to move. Your team does the copy through the desktop clients or a bulk transfer, while a Seafile administrator sets up the server, libraries, permissions and storage. Ask any implementation partner for a written scope that lists the libraries, users, storage backend and cutover steps, since those items drive the quote. Dropbox's browser download limits (folders under 250 GB and fewer than 10,000 files) are one reason large folders usually move through the desktop app instead, so plan that work per team.

How long does a Dropbox to Seafile migration take?

Duration is driven by total data volume, upload bandwidth to your own servers, the number of libraries, and how many teams cut over in waves. Dropbox's own help documentation notes that its browser downloads are limited to folders under 250 GB with fewer than 10,000 files, so large folders take longer through the desktop app. No fixed timeline applies to every team, so ask for a schedule that separates the server build, a pilot library, the bulk copy and the verification of file counts and sizes before any team is switched over.

Can our team migrate from Dropbox to Seafile without outside help?

Yes, a team with Linux and container experience can do it internally, using the Docker single-node setup or a binary installation described in the Seafile admin manual. The harder parts are design decisions: which folders become libraries, which libraries need per-library encryption (which uses a user-chosen password and affects how search and sharing behave), and how permissions map to Dropbox team folders. Teams without a Seafile administrator often pay for a short design and handover engagement instead of a full implementation, so confirm which of these tasks you can staff internally before you decide.

What does our IT staff need to provide for the Seafile rollout?

Your IT staff typically supply the hosting environment, a domain and TLS certificates, storage (local disks, or an S3, Ceph or OpenStack Swift backend as listed in the Seafile admin manual), backup targets, and the identity source. If you want single sign-on, the manual documents LDAP and Active Directory integration and several SSO options, so your identity team must confirm which directory and protocol you use. Also plan for monitoring, patching and an administrator who owns upgrades, because those tasks recur after go-live.

Do we need Seafile Professional Edition, and how does the 3-user rule work?

Seafile Professional Edition is needed only if you require features that the Seafile admin manual lists for that edition, such as SAML 2.0, cluster deployment, multi-tenancy, role-based permissions, ClamAV virus scanning or advanced file search. Per the Seafile download page, Professional Edition can run without a license file for up to 3 users. Teams above that size need a license file, so confirm your user count, required features and any support terms with Seafile before you choose an edition. Community Edition, listed as 12.0.14 for generic Linux on the download page, covers core sync and sharing.

What happens to Dropbox sharing links and version history after the move?

Dropbox sharing links and version history do not carry over automatically, so plan to recreate shares and re-send links to external collaborators after each library is live. Seafile has its own sharing model and file history, which you should test with a pilot library before cutover. Keep the original Dropbox data available until you have checked file counts, sizes and key documents. Confirm with Seafile exactly how history is retained for migrated files, and record which older versions you need to preserve for legal or audit reasons.

Can we encrypt sensitive libraries in Seafile, and what does that cost us?

Yes, Seafile organizes files into libraries that sync separately, and each library can be encrypted with a password chosen by the user, according to the Seafile README. Encryption protects data at rest on the server, but the password must be shared with users who access the library, and lost passwords cannot be recovered by the administrator. Ask your security team which libraries need encryption, how keys are distributed and whether encrypted libraries work with your search, preview and online office requirements before deciding how to structure the migration.

How DeployOpen scopes and runs a Seafile migration

DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted Seafile inside your own cloud accounts, data centers or air-gapped networks. Engagements are fixed-scope, so the libraries, sharing rules, sign-in method and cutover plan are agreed in writing before any team's files move.

How we scope

Inventory Dropbox team folders, member counts and shared links to define which folders become Seafile libraries.
Agree which libraries use per-library encryption and document the password recovery process owners must accept.
Define the LDAP, Active Directory or SSO integration, storage backend and Professional or Community edition choice in the written scope.

How we build

Deploy Seafile with Docker, Kubernetes with Helm charts or binary installation, matching your infrastructure standards.
Configure storage on S3, Ceph or OpenStack Swift and connect the identity source you agreed in scope.
Test sync from the desktop clients on pilot libraries, including large folders and permission boundaries, before any production copy.

How we hand over

Deliver runbooks for installation, library creation, user onboarding, backup and restore, and upgrades.
Document the migration record per folder, showing source, destination library, file counts and any exceptions found.
Walk administrators through library ownership, encryption key handling and sharing controls with your own staff.

How we support

Offer ongoing support, upgrades and continuous testing under a retainer agreed separately from the migration scope.
Plan patch windows and version upgrades of Seafile and its extensions as part of the retainer, with changes agreed in writing.
Run security testing of the deployed service on request, so you can confirm controls before and after each cutover wave.