Migrate from Box to Seafile

How to migrate from Box to Seafile without losing control of the content

Most teams leaving Box arrive here because of a renewal, a residency requirement or pressure from lock-in. Migrating from Box to Seafile is three pieces of work: a bulk export of the content, a rebuild of that content as Seafile libraries, and a rebuild of permissions, shared links and single sign-on in the new platform. The export is the simplest part. Box documents FTPS and SFTP access for bulk migration and occasional bulk download for Business and Enterprise customers, and it caps files transferred over FTPS at 32 GB, so confirm with Box which of your plan tiers and transfer paths apply before you plan the export window. The library rebuild and the permission rebuild carry most of the effort and most of the risk.

In practice an internal platform or IT team owns the migration and brings in an implementation partner for the Seafile build, the scripted loading of folders, and the identity integration. The internal team should own the decisions: which Box folders become which libraries, who holds owner rights in each library, and which shared links are still needed. Seafile supports LDAP and Active Directory integration and several single sign-on options, so confirm early which identity provider your users authenticate against and whether SAML 2.0 is needed, because that is a Seafile Professional Edition feature. Seafile Professional Edition runs without a license file for up to 3 users, so a small pilot can start before you buy a subscription.

The control question is where the content and its keys live during the move. Seafile organizes files into libraries that sync separately and can each be encrypted with a user-chosen password, so decide which libraries need that protection and who holds those passwords before loading any data. Keep a staging copy of the Box export on storage you control, record a checksum or file count per folder, and compare counts after each load. Expect Box version history, comments and collaborator roles to need a deliberate decision rather than a straight copy, and ask your partner to document each mapping so auditors can trace where a file came from.

Which Box capabilities map cleanly to Seafile and which need rework

This table compares the main Box capabilities with their Seafile equivalents and marks each as clean, needs rework or gap. Use it to scope the migration, then confirm each Seafile feature against the admin manual for the edition and version you plan to deploy.

Capability	Box	Seafile	Status
Folder structure	Nested folders in a single account tree	Libraries hold folder trees and sync separately; plan how top-level folders become libraries	Clean
Sharing with internal users	Folder and file sharing with collaborators	Library and folder sharing to users and groups in Seahub; confirm group sharing behavior in the admin manual	Clean
Shared links	Shared links with expiry and password options, depending on plan	Share links with password and expiry options; confirm available link settings for your edition	Needs rework
Collaborator roles	Editor, viewer, uploader and co-owner roles	Library permissions such as read-only and read-write; map Box roles to these and confirm in the admin manual	Needs rework
Version history	Version retention depends on the Box plan	Library history is kept by Seafile; confirm retention settings and whether old Box versions are carried over	Needs rework
Encryption	Box-managed encryption at rest, with key options depending on plan	Per-library encryption with a user-chosen password; users must re-enter passwords, so plan key handling	Needs rework
Single sign-on	SAML and identity integrations on enterprise plans	SAML 2.0 and LDAP or Active Directory in Professional Edition; confirm connector settings for your identity provider	Needs rework
Full-text search	Content search across files in the Box account	Advanced file search is a Professional Edition feature; confirm index behavior and scope in the admin manual	Needs rework
Online office editing	Box Notes and Box Office integrations	Collabora Online or ONLYOFFICE integration; Box Notes content must be exported separately	Needs rework
Box Notes and Box integrations	Native notes and third-party app connections	No direct equivalent to Box Notes; app connectors must be rebuilt or replaced	Gap

What data can be exported from Box and what it leaves behind

Box offers documented bulk paths over FTPS and SFTP, but a bulk transfer moves file content and little else. The cards below set out the transfer limits, the metadata and permission records you must inventory separately, and the identity and integration work that stays with you during the move to Seafile.

FTPS bulk download path

Box documents FTPS and SFTP access for Business and Enterprise customers and describes them as intended for bulk migration and occasional bulk download. Confirm with your Box admin that FTP access is enabled for your account before scheduling any transfer. Plan the run around the 32 GB per-file limit that applies over FTPS, and identify any larger files for a separate route.

SFTP as the alternative route

SFTP is the other documented bulk path for Business and Enterprise accounts, and it is the one to test first when your team needs an encrypted channel with a stable client. Verify with Box which file size limits apply to SFTP in your tenant, since the 32 GB figure is documented for FTPS. Record which path each library used, so the Seafile load step can be checked against the source.

Version history and file timestamps

A plain download delivers the current version of each file and generally does not carry older versions across. Decide which version history matters for audits and legal holds, and export it through a separate method or archive it before the source is closed. Seafile stores its own history per library, so record the original modification dates in your manifest because a file load may reset them.

Shared links and collaborator permissions

Shared links, folder invitations and per-user roles live in Box, not in the downloaded files. Build an inventory of every shared link, its expiry and password settings, and each collaborator's access level before the export starts. Map those records to Seafile libraries and roles, then rebuild them for the people who still need access, so a link that exists in Box does not silently vanish.

SSO and directory integration

Box user accounts usually authenticate through a corporate identity provider, and those assignments do not transfer. Seafile supports LDAP and Active Directory integration, and SAML 2.0 is a Professional Edition feature. Decide whether users will sign in with the directory or a SAML identity provider, confirm the attributes Seafile needs for each user, and test sign-in before cutover.

Connected apps and integrations

Box connections to Microsoft Teams, Slack, Salesforce, scanners, or internal scripts stop working once the source is decommissioned. List every integration, its service account and its API calls, and decide which ones need a Seafile API replacement and which can be retired. Include scripts that read Box folder IDs, since those identifiers will change after the migration.

The migration sequence from inventory to decommissioning Box

This sequence moves Box content into Seafile libraries in controlled batches, rebuilds permissions and links on purpose, and only switches users over after a parallel run confirms the data and access are right. Each step ends with a written output and a gate that must pass before the next step starts.

Inventory Box content, owners and external shares
Start by listing every folder, owner, and external collaborator in the Box tenant that is in scope, and record size, file count, and the groups or users who hold access. Export the list from the Box admin console and reports, then confirm it with the content owners so that abandoned or duplicate folders are marked before any transfer. The output is a signed-off inventory that maps each Box folder to a planned Seafile library and names an accountable owner for each one. Gate: no library moves forward until its owner has confirmed the inventory row.
Select and migrate a pilot library set
Choose a small set of libraries that span different sizes, owners, and sharing patterns, such as one internal team folder and one folder with external collaborators. Set up the Seafile test environment on your own infrastructure, create the pilot libraries, and move the pilot data through the full path so that download, load, and access checks are exercised end to end. The output is a pilot report listing what transferred, what failed, and how long each batch took in your environment. Gate: the pilot is accepted only when owners confirm their files open correctly and no file name or folder structure has been lost.
Bulk download Box content over FTPS or SFTP
Use the FTPS or SFTP access that Box provides for Business and Enterprise customers to pull content in batches, keeping each batch under the 32 GB per-file limit that applies to FTPS. Store the downloads on a staging volume with checksums recorded per file, and log any file that fails or is skipped. Box describes these methods as intended for bulk migration and occasional bulk download, so confirm access with your Box administrator before scheduling. The output is a complete staging set with a manifest of checksums and an exception list. Gate: the exception list is reviewed and every missing file is either retrieved or accepted in writing by its owner.
Load folders into Seafile libraries
Create the production libraries in Seafile according to the signed-off inventory, then load the staged files into them with the correct folder hierarchy and owner assignments. Decide per library whether password encryption applies, because encrypted libraries need their passwords handled through a documented process before users can sync them. Verify each load against the checksum manifest and the file counts from the inventory. The output is a loaded set of libraries with a reconciliation report showing matching counts and sizes. Gate: reconciliation must show no unexplained differences before permissions are rebuilt.
Rebuild collaborator permissions and shared links
Recreate group and user permissions in Seafile using the roles and access levels recorded in the inventory, and rebuild external shares as new Seafile share links with expiry and password settings chosen by each owner. Box shared links do not transfer as working links, so every link that users depend on must be issued again and its new URL recorded against the old one. If you use LDAP, Active Directory, or SAML single sign-on, confirm that group membership maps correctly before assigning access. The output is a permissions register and a link map that tells users where each shared item now lives. Gate: owners sign off that each permission and link matches their intent.
Run Box and Seafile in parallel
Keep Box available as the system of record while a defined group of users works in Seafile, and set a rule for which system holds the latest version of each file during this period. Track access problems, sync issues, and missing links in a shared log, and fix them in the migrated libraries before expanding the group. Confirm that virus scanning, search, and any online editing integrations behave as expected for your Professional Edition configuration. The output is a parallel-run log with a list of resolved and open issues. Gate: the group expands only when no open issue blocks daily work and the content owners confirm their libraries are current.
Cut over users and freeze Box writes
Announce a cutover date, freeze new writes in Box for the migrated content, and run a final incremental transfer of anything changed since the staging download. Repeat the checksum and reconciliation steps on the delta, then switch all users, links, and integrations to Seafile. Confirm that the link map has been published to users and that help desk staff know how to answer questions about moved content. The output is a cutover record showing the final reconciliation, the freeze time, and the list of users switched. Gate: the cutover is complete only when the final reconciliation passes and no user still depends on a Box link for active work.
Decommission Box after retention checks
Before removing Box access, confirm with your legal, compliance, and records owners which content must be retained, exported, or deleted, and document the retention decision for each category. Revoke Box user access, remove integrations and shared links, and keep an archived copy of the export and the reconciliation records under your own retention policy. Ask your Box account representative to confirm the terms and dates that govern account closure and data deletion, since those details depend on your contract. The output is a decommissioning record that lists what was retained, where, and who approved the closure. Gate: Box is closed only when the records owner has signed the decommissioning record.

How Seafile libraries, encryption and Professional Edition change the target design

Seafile organizes content into libraries, and each library syncs separately and can be encrypted with a password the user chooses. That structure changes how Box folders should be mapped. In Box, a top-level folder tree often carries permissions and sharing for many teams at once. In Seafile, a library is the unit that receives its own sharing, sync and, if you choose, its own encryption. Before any bulk load, decide which Box folders become libraries, which stay as folders inside a library, and which libraries must be encrypted. An encrypted library's password is not held by the administrator in the same way as an ordinary library, so confirm with Seafile how password recovery and administrator access work for each option, and document the answer before the first upload. Confirm too that your sync clients and mobile apps behave as your users expect with encrypted libraries.

Professional Edition features need to be planned as scope, not added after cutover. The Seafile manual lists SAML 2.0, multi-tenancy, role-based permissions, virus scanning with ClamAV and advanced file search as Professional Edition capabilities. Each one affects the design: SAML 2.0 determines how identities arrive from your identity provider, role-based permissions determine how Box collaborator levels translate into Seafile roles, and ClamAV determines whether files are scanned as they arrive from the bulk export. Community Edition 12.0.14 is listed for generic Linux on the Seafile download page, but that listing does not answer your licensing question. The download page states that Professional Edition runs without a license file for up to 3 users, so ask Seafile for the license terms, user-count limits and support options that apply to your headcount before you choose an edition.

What drives migration cost and duration

This table lists the main factors that move the effort of a Box to Seafile migration, why each one matters, and how to keep it manageable. Read it as a checklist to scope a fixed-scope quote, and ask for each driver to be sized in writing before work starts.

Driver	Why it changes cost or effort	How to keep it down	What to ask for in a written quote
Content volume and file count	Bulk download time, transfer capacity and upload time into Seafile scale with total bytes and object count. Box FTPS transfers are capped at 32 GB per file, so large files need a separate path.	Archive stale content before export, split very large files into a separate batch, and run transfers in windows that do not compete with production traffic.	Total data size, file count, largest single file, and the handling plan for files above the FTPS per-file limit.
Number of libraries and encrypted libraries	Each Seafile library is a separate sync unit, and libraries can be encrypted with a user-chosen password. Encrypted libraries need passwords to be collected and tested, which adds coordination work.	Consolidate small folders into fewer libraries where the access model allows, and decide early which content must be encrypted.	Planned library count, which libraries are encrypted, and who holds and distributes library passwords.
Permission complexity	Box collaborator roles, group grants and inherited folder permissions must be mapped to Seafile share and role settings. Exceptions found late in testing drive rework.	Export a permissions inventory from Box first, reduce direct user grants in favor of groups, and agree a role model with content owners before loading.	Method for exporting Box permissions, mapping rules, and the number of permission exceptions the quote assumes.
External collaborators	Guest accounts, shared links and expiry settings from Box have to be recreated and checked. Partners outside the organization often need verification and onboarding.	Inventory active external shares, remove expired ones, and confirm which partners still need access before migration starts.	Count of external collaborators and shared links, expiry rules to rebuild, and the partner communication responsibilities.
SSO and directory integration scope	Connecting Seafile to SAML 2.0, LDAP or Active Directory is Professional Edition work. Attribute mapping, group sync and test users add effort per identity source.	Confirm the identity provider early, limit the number of identity sources, and use group-based access instead of per-user setup.	Identity providers in scope, whether SAML 2.0 or LDAP/AD is used, group sync requirements, and test and rollback plan.
Office editing integration	Online editing with ONLYOFFICE or Collabora Online is a separate component to install, connect and test. Document formats and co-authoring needs determine the test matrix.	Decide which formats must be edited online, and test only those formats in a pilot before wider rollout.	Editing platform chosen, supported file types to test, and whether co-authoring and certificate setup are included.
Integrations and scripts to rebuild	Box integrations, webhooks and automations that call the Box API must be replaced or retired. Each one needs its own design and testing.	List every connected app and script, retire those no longer used, and map the rest to Seafile APIs or existing tools.	Inventory of integrations, which ones are replaced, which are retired, and how the API work is priced or scoped.
Hosting, storage and backups	Storage capacity, backup targets and the recurring operations for Seafile run for as long as the platform is in service. These costs continue after cutover.	Size storage from the content inventory, define backup scope and retention early, and check that restores are tested.	Storage backend choice, backup design, recovery test plan, and which costs are one-time versus recurring.

How the migration differs by organization size and starting point

A small team on Box Business usually has few accounts, a modest set of shared folders and few external collaborators. The migration is mostly about moving content and re-inviting people, so scope stays small and sequencing can be simple. As an illustrative example, a team of four with two project folders could export, load and cut over in a single working session if the content is small, though the team should still measure the folders first.

Scope: Sort folders into active, archive and delete before export, since old copies and duplicates often make up a large share of small accounts.
Licensing: Seafile Professional Edition can run without a license file for up to 3 users, per the Seafile download page, so confirm current terms before relying on that allowance.
Sequencing: Move one library at a time, then have its owner check file counts and names before starting the next.
Parallel run: A short overlap is usually enough. Keep Box read-only for a fixed window and tell users where each library now lives.
Operations: Decide who applies updates and who restores backups, because a small team often has no dedicated administrator.

Before cutover, check your user count against the Professional Edition terms and name the person who will own patching and backups.

What usually goes wrong when moving from Box to Seafile

Most failed Box to Seafile cutovers trace back to a few gaps: metadata that a plain download never carried, access rules that were never written down, and credentials nobody recorded. Each card below names one failure mode and the check that prevents it during the inventory and pilot.

Version history not carried over

A plain bulk download from Box gives you the current file versions, not the revision history that teams may rely on for audits or rollback. Decide per library whether older versions matter, and if they do, load them deliberately rather than assuming they arrive. During the inventory, sample files with several revisions and record which ones need history. In the pilot, confirm that the chosen approach preserves what the business actually needs.

Shared-link expiry settings lost

Box shared links often carry expiry dates, passwords and download restrictions that do not travel with the files. Links created on Box stop working after cutover, and the settings that limited exposure disappear with them. During the inventory, export a list of active shared links with their settings, then decide which to recreate in Seafile and which to retire. Test each recreated link in the pilot from outside the corporate network.

External collaborators locked out

Partners and customers who received Box invitations will not have accounts on your Seafile server, and they will not be told where to go. Access breaks at cutover unless the invitations are rebuilt. Map every external collaborator to a library and role during the inventory, send them a planned notice, and confirm in the pilot that each one can sign in or open a link.

Encrypted library passwords lost

Seafile can encrypt each library with a password chosen by the user, and Seafile cannot recover that password for you. A library created with an unrecorded password becomes unreadable. Require owners to record passwords in an approved password manager before any encrypted library is created, and confirm during the pilot that every owner can open their library after a fresh sign-in.

SSO misconfiguration at cutover

Professional Edition supports SAML 2.0 and LDAP or Active Directory, but attribute mappings, group names and logout behavior must match your identity provider exactly. A small mismatch can grant the wrong role or lock out a whole department. Document the attribute map during the inventory, test with a pilot group containing admins, standard users and a leaver account, and confirm role assignment before widening access.

Large file uploads failing

Files that moved cleanly over FTPS or SFTP can still fail when uploaded into Seafile if web server, proxy or storage limits are lower than the largest files in your estate. Failures often surface only for a few users with big design or media files. During the inventory, list the largest files by library, and in the pilot upload representative large files through the web interface and the desktop client, checking the timeouts and size limits on every proxy in front of the server.

Users syncing back to Box

Desktop sync clients, mobile apps and bookmarks pointed at Box keep working until someone turns them off, and staff may keep editing the old copy. The result is two diverging versions of the same contract. Set a freeze date in the cutover plan, disable Box sync where your admin controls allow, publish the new Seafile address, and check during the pilot which users still have Box clients installed.

Questions buyers ask before moving from Box to Seafile

What does a migration from Box to Seafile cost?

The cost depends on the work involved, not on a single number. Seafile Community Edition is free to run under AGPLv3, while Seafile Professional Edition needs a license once you go beyond 3 users, so licensing is one recurring line. The bigger items are one-time: planning, bulk export from Box, loading folders into libraries, rebuilding permissions and SSO, and testing. Recurring costs include the servers, storage growth, backups and support. Ask any quote to split one-time work from recurring costs, and to state which Professional features (SAML, ClamAV, multi-tenancy) are assumed.

How long does a Box to Seafile migration take?

Timeline is set by the volume and structure of content, not by the tool. The main drivers are total data size, number of folders and files, how many users and groups need access, how many shared links and external collaborators must be recreated, and whether SSO is in scope. Bulk export speed depends on your network and on how Box's FTPS or SFTP transfers perform for your data. Ask for a written schedule that separates a pilot library from the full cutover and names the change-freeze window for Box.

What does our internal team have to provide?

Your team has to supply decisions and access that only your organization can give. That includes a list of which Box folders must move and which can be archived, an owner for each library, the group structure you want in Seafile, access to your identity provider for LDAP, Active Directory or SAML, and storage capacity on your servers or object storage. You also need a named approver for permission mapping and someone who can test each department's workflows before cutover. Without these, any provider will spend time guessing at ownership.

Can we run the Box to Seafile migration ourselves?

Yes, a capable internal team can do it, especially for a small number of libraries. Seafile's admin manual documents Docker single-node setups, Kubernetes with Helm charts and binary installations, and the download and export steps are standard file operations. The harder parts are rebuilding permissions for many users, integrating SSO correctly, and validating that nothing was lost. If you want outside help, DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted platforms in your own infrastructure, under a written, fixed scope.

How do we handle Box's 32 GB FTPS limit?

Box's FTPS transfers are limited to 32 GB per file, so any single file larger than that cannot come down over FTPS. Box describes FTPS and SFTP as intended for bulk migration and occasional bulk download, available to Business and Enterprise customers. Plan a pre-migration inventory that lists files over the limit, then decide whether to split them into separate transfers or handle them through another route. Confirm the current limit and access method with Box support before you start, because the platform's terms can change.

What happens to shared links and collaborator permissions?

Shared links and permissions do not carry over automatically from Box, so they must be rebuilt in Seafile. A plain bulk download brings files and folders but not the sharing model. Map each Box collaborator to a Seafile user or group, then recreate library permissions by role. Shared links need new owners, expiry settings and passwords in Seafile, and recipients must be told their new links. Seafile libraries can each be encrypted with a user-chosen password, and that choice affects how you manage access during the transition. Review every external share before cutover.

Does Seafile Professional Edition cover SSO and role-based access after migration?

Seafile Professional Edition adds SAML 2.0, role-based permissions and multi-tenancy to the feature set documented in its admin manual. Seafile also supports LDAP and Active Directory integration and several SSO options. Confirm in the manual which edition, version and identity provider configuration match your environment before you design the permission model. Because these features are part of the Professional Edition, include the license and the identity integration work in the quote so they are not treated as optional extras.

How DeployOpen scopes and runs a Box to Seafile migration

DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted platforms inside the client's own infrastructure, so a Seafile deployment runs in your cloud account, data center or air-gapped network rather than in a DeployOpen environment. Most engagements are fixed-scope, which means the scope, deliverables and timelines are agreed in writing before any work starts. For a Box to Seafile move, that written scope is where the decisions get made: which libraries move, which Box accounts map to which Seafile users and groups, whether Professional Edition features such as SAML 2.0 or role-based permissions are in scope, and which storage backend (for example S3, Ceph or OpenStack Swift) holds the data. A quote follows from that written scope, so the more precisely the scope names these items, the more precisely the quote reflects the work.

Before a quote can be written, the scope needs a few facts from your side. Ask for an inventory of Box content by size, file count and folder depth, a list of external collaborators and shared links, and a decision on which Box version history must be preserved. Confirm the Seafile edition you need, since the Seafile download page states that Professional Edition runs without a license file for up to 3 users, which will not cover most organizations. Confirm the identity source for SSO and whether ClamAV scanning and online office editing with ONLYOFFICE or Collabora Online are required. Each of these changes the number of configuration, integration and testing tasks, and therefore the effort in the quote.

Ongoing support, upgrades and continuous testing are available as retainers, and they are separate from the initial fixed-scope migration. Once Seafile is live, the recurring costs you should plan for include the infrastructure that holds the data, backups, Seafile Professional licensing if you move beyond the free user limit, and whatever support level you choose. Ask any implementation partner, DeployOpen included, to state in the written scope which items are one-time (installation, data load, permission rebuild, cutover) and which are retainers (upgrades, patching, support windows and periodic restore tests), so you can compare offers on the same basis.