Migrate to/from Seafile (Library-Based, Encrypted)

What is Seafile?

Seafile is the open-source, self-hosted file-sync platform built around a distinctive library model — every collection of files lives in its own isolated 'library' with its own permissions, sharing rules, and optional client-side encryption key. Founded in 2012 by ex-Tsinghua University engineers, Seafile is widely deployed in European universities, research institutions, and privacy-focused enterprises — particularly where the more granular library-based access control fits the workflow better than Nextcloud's whole-filesystem-per-user model. The Pro Edition is free for up to 3 users, €100/year for up to 9 users, and €44 per user per year for 10+ users — among the most affordable enterprise self-hosted file-sync licensing in the market.

Seafile's signature feature is true client-side end-to-end encryption at the library level: when you create an encrypted library, the password derives the encryption key on the client device, files are encrypted before upload, and the Seafile server stores only ciphertext — even system administrators cannot decrypt encrypted-library content. This zero-knowledge model is shared with Proton Drive and Filen, but applied at library granularity rather than account-wide. CloudsLinker connects to Seafile via the standard account-credentials API, supporting non-encrypted libraries fully and encrypted-library metadata only (encrypted content cannot be read by any third-party tool, by design). The connector also accepts custom server URLs for self-hosted deployments — Seafile Cloud (the SaaS offering) and self-hosted instances both work.

Key features of Seafile

Library-based architecture

Unlike Nextcloud's per-user filesystem, Seafile stores files in libraries — each with its own permissions, sharing, and optional encryption key. A user can have many libraries; each is migration-scoped independently.

Pro Edition: free for 3 users

Free up to 3 users. €100/year for up to 9 users. €44/user/year for 10+ users — among the cheapest commercial self-hosted file-sync licensing in the market.

Library-level E2E encryption

Encrypted libraries use client-side AES encryption with the password as the key root. Server stores ciphertext only; even admins cannot decrypt. Zero-knowledge by design.

WebDAV available, but slower

Seafile exposes WebDAV (SeafDAV) as a secondary protocol. Each WebDAV file requires a separate commit, so bulk uploads are slower than the native sync client. CloudsLinker uses the native API for performance.

Encrypted libraries inaccessible via WebDAV

WebDAV cannot decrypt encrypted libraries — they appear empty over WebDAV. To migrate encrypted library content, decrypt locally first, then re-encrypt on the destination.

European university adoption

Widely deployed at French, German, Austrian, and Swiss universities (PHP-based Nextcloud and Go-based oCIS being primary alternatives). Research institutions value the library model's scope isolation.

Why connect Seafile to CloudsLinker

CloudsLinker connects to Seafile using your account email + password, plus the server URL for self-hosted deployments (Seafile Cloud uses the default seacloud.cc; self-hosted users provide their custom domain). Once connected, transfers run over the Seafile REST API at the library level — non-encrypted libraries are fully readable and writable; encrypted libraries are accessible only as metadata (filenames, sizes, structure) but content cannot be decrypted by any third-party tool, including CloudsLinker.

What you can do with Seafile on CloudsLinker

Library-aware migration

Migrate Seafile libraries individually to Google Drive folders, OneDrive directories, or S3 buckets — preserving the per-library scoping that's distinctive to Seafile's model.

Runs on our servers

Seafile transfers execute on CloudsLinker infrastructure. Useful when ingesting from a fast cloud source into a relatively constrained self-hosted Seafile.

Scheduled & incremental sync

Hourly / daily / weekly schedules. Useful for keeping a research-data library synced from Seafile to off-site S3, or for nightly Seafile → Wasabi backup.

Filter by library, type, size

Migrate only specific libraries, exclude large research datasets, or back up just office documents from each library.

Common Seafile transfer scenarios

Research-data backup: Seafile library → S3 / Wasabi cold archive

Universities and research institutions store multi-TB datasets in Seafile libraries, often per-project. CloudsLinker migrates an entire library to S3 Glacier Instant Retrieval ($0.004/GB) or Wasabi ($6.99/TB) at end-of-project — preserving folder structure within the library, freeing up Seafile capacity for active research, and providing immutable Object Lock retention.

Migrate Seafile → Nextcloud for productivity-suite consolidation

Organizations sometimes outgrow Seafile's library-only scope and want Nextcloud's full productivity suite (Talk, Calendar, Office). CloudsLinker copies non-encrypted libraries from Seafile to Nextcloud user accounts via WebDAV, mapping each Seafile library to a Nextcloud folder. Encrypted libraries require re-uploading after decryption.

Cross-instance Seafile DR: primary on-premise, secondary in cloud VM

Run a primary Seafile at the office and a secondary on a Hetzner / Scaleway VM. CloudsLinker schedules cross-instance sync via the Seafile API — both instances connect with their respective credentials, with delta sync keeping the secondary current.

Migrate Google Drive / OneDrive → Seafile for EU-sovereignty

Privacy-conscious EU teams migrating away from US-controlled clouds often pick Seafile (alongside Nextcloud and ownCloud) as the destination. CloudsLinker copies entire user OneDrive / Google Drive content into per-user Seafile libraries preserving folder hierarchy.

Hybrid: Seafile for daily collaboration, Storj for E2E-encrypted archive

Run active research data on Seafile (where library-level access control matters), with finished projects archived to Storj's decentralized E2E-encrypted network. CloudsLinker filters by modification date — projects unmodified for 12+ months migrate to Storj at $4/TB with built-in encryption.

How to connect Seafile to CloudsLinker

Seafile uses account credentials (email + password) plus a server URL for self-hosted deployments.

Before you start

For self-hosted Seafile deployments, you’ll need:

The Seafile server URL (e.g. https://seafile.example.org)
A user account with access to the libraries you want to migrate

For Seafile Cloud (the SaaS offering at seacloud.cc), use the default URL.

If 2FA is enabled on your Seafile account, you may need to generate an app token from the Seafile profile page (the exact path varies by Seafile version).

Connection steps

In CloudsLinker, click Add Cloud → choose Seafile.
Enter a display name (e.g. “Seafile — research data”).
Enter the Server URL:
- Seafile Cloud: https://seacloud.cc (or the default if your CloudsLinker version pre-fills it)
- Self-hosted: https://<your-seafile-domain> (your custom domain)
Enter your email (Seafile login email).
Enter your password.
Click Confirm — CloudsLinker validates with the Seafile API and lists your libraries to verify the connection.

Encrypted library note

If a library is marked as encrypted in Seafile, CloudsLinker can list its files (names, sizes, structure) but cannot read content. To migrate encrypted-library content, use the Seafile desktop sync client to download and decrypt locally, then re-upload to the destination.

Revoke access

To revoke CloudsLinker’s session later: change your Seafile password from the account profile page → all existing sessions including CloudsLinker’s are invalidated. Alternatively, delete the specific session token from Seafile’s profile / connected apps page (path varies by version).

Seafile upload & download limits you should know

Seafile is self-hosted, so most “limits” depend on your deployment configuration:

Library architecture: files organized into libraries, each with its own permissions, sharing, and optional encryption.
Pro Edition pricing:
- Free up to 3 users (full Pro features)
- €100/year for up to 9 users
- €44/user/year for 10+ users
Encryption: library-level E2E encryption with client-side AES; password as key root; zero-knowledge.
Maximum file size: no inherent cap — depends on server disk and reverse-proxy client_max_body_size. Defaults handle multi-GB files without configuration changes.
Sync client chunked upload: large files split into small chunks server-side for resilient transfer.
WebDAV (SeafDAV): secondary protocol; slower bulk uploads (separate commit per file); cannot access encrypted libraries.
Native API: primary protocol used by CloudsLinker — faster than WebDAV, supports library-level operations.
Bandwidth: unlimited by default; per-user quota configurable by admin.
Trash retention: configurable per library; default typically 30 days.
Version history: included; per-library retention configurable.
API rate limits: Seafile applies brute-force protection on auth; otherwise no per-user rate limiting by default.
Self-hosting: widely deployed at European universities, research institutions, and privacy-focused enterprises.

Sources: Seafile: Pricing, Seafile Admin Manual: WebDAV extension, Seafile Admin Manual: Security features, Seafile: Features overview.

Seafile + CloudsLinker — Frequently Asked Questions

What's the Seafile 'library' concept?

A library is Seafile's unit of file organization — equivalent to a 'top-level folder with its own permissions, sharing, and encryption key'. A user can own many libraries; admins create shared libraries for groups. Each library is independently versioned and can be set as encrypted or non-encrypted at creation. CloudsLinker treats each library as a separate migration scope.

Can CloudsLinker read encrypted libraries?

No. Encrypted libraries use client-side encryption with the password as the key root — Seafile's server (and any third-party tool, including CloudsLinker) stores only ciphertext. Even Seafile admins cannot decrypt. To migrate encrypted-library content, you must download via the Seafile sync client (which decrypts), then re-encrypt on the destination.

Does CloudsLinker work with non-encrypted libraries?

Yes — fully. Non-encrypted libraries are accessible via the Seafile API exactly like any other file storage. CloudsLinker reads, writes, and syncs them at full API speed.

What's the maximum file size?

Seafile self-hosted has no inherent per-file size limit — bounded by your server's disk space, PHP / Go runtime configuration, and reverse proxy settings. The default uses chunked uploads to bypass HTTP request size caps. Practical files in the multi-GB range work without configuration changes; for files above 10 GB, ensure your reverse proxy's client_max_body_size allows it.

How does Seafile WebDAV (SeafDAV) compare to the native API?

WebDAV (SeafDAV) is supported but slower for bulk operations — each WebDAV file write requires a separate commit, where the native API can batch. CloudsLinker uses the native Seafile API for performance. WebDAV is useful for occasional manual file access or for tools that only support WebDAV.

Are my Seafile credentials safe with CloudsLinker?

Yes. Email + password are encrypted at rest with AES-256 and decrypted only inside the active transfer worker. For self-hosted deployments, we strongly recommend creating a dedicated Seafile account scoped to specific libraries via Seafile's group/sharing model, separate from admin credentials.

How does Pro Edition pricing work?

Free for up to 3 users (full Pro features). €100/year for up to 9 users. €44 per user per year for 10+ users. Among the cheapest commercial self-hosted file-sync licensing — significantly lower than Nextcloud Enterprise per-user pricing and ownCloud Enterprise.

Can I migrate between two Seafile instances?

Yes. Connect each instance as a separate cloud in CloudsLinker (each with its own server URL and credentials), then run cross-instance copies. Folder structure within libraries transfers; library-level permissions and sharing don't (they're instance-specific).

How does Seafile compare to Nextcloud and ownCloud?

Seafile: library-based architecture, fastest sync engine in the category, library-level encryption, leaner feature set. Nextcloud: per-user filesystem, full productivity suite (Talk, Calendar, Office), AGPLv3 community edition. ownCloud: per-user filesystem, two product lines (PHP Server, Go-based Infinite Scale), enterprise focus under Kiteworks. Pick by architectural fit — library model vs filesystem model.

Is this an official Seafile partnership?

No. CloudsLinker is a third-party tool that uses Seafile's public API under your account credentials. Revoke access by changing your Seafile password — invalidates all existing sessions including CloudsLinker's.

Seafile transfer guides

Step-by-step walkthroughs for moving data to and from Seafile.

Transferring Files from Seafile to Google Drive Seamlessly

Discover the ease of moving files between Seafile and Google Drive with Cloudslinker. This guide explores the streamlined process …

Conclusion

Seafile's library-based architecture, generous Pro Edition pricing (free up to 3 users), and library-level zero-knowledge encryption set it apart from Nextcloud and ownCloud — particularly attractive for European universities and research institutions where per-project scope isolation matters more than productivity-suite features. CloudsLinker connects via account credentials and a server URL, supporting full migration of non-encrypted libraries and metadata of encrypted ones. Connect with your Seafile credentials and run your first migration in minutes.

Start Your Free Seafile Transfer