Migrate to/from Self-Hosted ownCloud (Server / Infinite Scale)

What is ownCloud?

ownCloud is the original open-source self-hosted file-sync platform that started the entire category — founded by Frank Karlitschek in 2010 as a personal-cloud alternative to Dropbox and Google Drive. After Karlitschek's 2016 fork to create Nextcloud (with much of the developer community), ownCloud doubled down on enterprise-grade file collaboration under its corporate parent (now Kiteworks, after the 2023 acquisition). Two product lines coexist in 2026: the legacy ownCloud Server (PHP-based, in maintenance mode) and the new ownCloud Infinite Scale (oCIS) — a ground-up rewrite in Go for high-performance, container-native deployments, designed to handle large file transfers and concurrent users without the PHP performance tuning that Nextcloud at scale requires.

ownCloud Infinite Scale is the more interesting product going forward — its Go architecture handles large-file uploads more cleanly than PHP-based stacks, with built-in S3 backend support and Kubernetes-native deployment. The legacy ownCloud Server still ships and is widely deployed in established enterprises that haven't yet migrated to oCIS. CloudsLinker connects to either via the same WebDAV API, so migrations work identically. Where ownCloud differs from Nextcloud — and where third-party tooling needs to be careful — is the licensing posture: many ownCloud Enterprise features (workflow automation, advanced tagging, additional storage backends) are gated behind paid licenses, while Nextcloud keeps everything in the AGPLv3 community edition.

Key features of ownCloud

Two product lines (2026)

ownCloud Server: legacy PHP, maintenance-mode but widely deployed. ownCloud Infinite Scale (oCIS): Go rewrite, container-native, recommended for new deployments.

Acquired by Kiteworks (2023)

ownCloud is now part of Kiteworks, a US-based secure-data-sharing company. Affects roadmap and licensing relative to Nextcloud (which remains independent and AGPLv3-pure).

Default chunk size: 10 MB

Both ownCloud Server and oCIS use 10 MB chunked uploads by default to bypass PHP / proxy size limits. Configurable for tuning against specific deployments.

Enterprise license gating

Several ownCloud features (workflows, advanced tagging, branding) require Enterprise license. CloudsLinker works against community-edition deployments unchanged — features are server-side, not API-side.

S3 backend support

ownCloud Infinite Scale has first-class S3 backend support — your ownCloud frontend can store files in AWS S3 / Wasabi / B2 transparently. CloudsLinker reads/writes via WebDAV regardless of underlying storage.

App passwords for 2FA

If 2FA is enabled, WebDAV requires an app-specific password. ownCloud generates these from Personal Settings → Security — same pattern as Nextcloud.

Why connect ownCloud to CloudsLinker

CloudsLinker connects to ownCloud (Server or Infinite Scale) via WebDAV using your server URL, username, and password (or an app password if 2FA is enabled). The WebDAV path differs slightly between the legacy Server and Infinite Scale — Server uses /remote.php/dav/files/<username>/, oCIS uses a slightly different namespace structure with Spaces. CloudsLinker handles both. Use as source for migrating off ownCloud (often paired with Nextcloud migrations or consolidation onto commercial cloud), as destination for migrating into a fresh oCIS deployment, or for ongoing backup of ownCloud content to S3-compatible object storage.

What you can do with ownCloud on CloudsLinker

WebDAV-based migration

Migrate from Google Drive, OneDrive, Dropbox or S3 into your ownCloud instance via WebDAV — works against both legacy ownCloud Server and the new Infinite Scale (oCIS).

Runs on our servers

ownCloud transfers execute on CloudsLinker infrastructure. Useful when uploading from a fast cloud source to a relatively constrained self-hosted ownCloud server.

Scheduled & incremental sync

Hourly / daily / weekly schedules. Useful for keeping an off-site backup synced from your self-hosted ownCloud, or for ongoing sync between ownCloud and a commercial cloud.

Filter by folder, type, size

Migrate only specific ownCloud folders, exclude large files (PHP servers may have lower limits), or back up just office documents.

Common ownCloud transfer scenarios

Migrate ownCloud Server → ownCloud Infinite Scale (oCIS)

The PHP-based legacy ownCloud Server is in maintenance mode; new deployments should use oCIS. CloudsLinker copies content between the two via WebDAV — connect the legacy Server as source, the new oCIS as destination, run a one-shot migration. Folder structure and file content transfer cleanly; per-user sharing permissions don't (different permissions models).

Migrate ownCloud → Nextcloud (or vice versa)

Many organizations evaluate both ownCloud and Nextcloud and end up consolidating on one. CloudsLinker handles the WebDAV-to-WebDAV migration in both directions, preserving folder hierarchy and modification times. A typical 500 GB / 50-user migration completes in a weekend.

Off-site backup of ownCloud to S3 / Wasabi / B2

Even if your ownCloud uses S3 as the storage backend, you still want a separate off-site backup independent of your storage provider. Schedule a CloudsLinker nightly incremental from ownCloud (via WebDAV) to a different cloud — Wasabi ($6.99/TB) or B2 ($6/TB) — for true 3-2-1 protection.

Migrate Google Drive / OneDrive → ownCloud (de-Google migration)

Privacy-conscious enterprises migrate away from US-controlled clouds toward self-hosted ownCloud, particularly EU government and healthcare deployments. CloudsLinker copies entire user OneDrive / Google Drive content into ownCloud user accounts preserving folder hierarchy.

Hybrid: ownCloud for collaboration, S3 for cold archive

Keep active working data on ownCloud (where collaboration features matter), with cold projects archived to IDrive e2 ($4/TB) or Wasabi. CloudsLinker filters by modification date — files unmodified for 12+ months migrate off ownCloud to cheap object storage.

How to connect ownCloud to CloudsLinker

ownCloud uses WebDAV authentication — URL + username + password. If 2FA is enabled, an app-specific password is required.

Before you start

If 2FA is enabled on your ownCloud account, generate an app password first:

Sign in to your ownCloud at https://<your-domain> with your normal credentials and 2FA.
Click your avatar (top right) → Settings (Personal Settings).
Go to Security in the left sidebar.
Scroll to App Passwords → enter a name (e.g. cloudslinker) → click Create new app password.
ownCloud displays the generated app password once. Copy it.

If 2FA is not enabled, you can use your regular login password — but creating an app password is still recommended (revocable individually).

Connection steps

In CloudsLinker, click Add Cloud → choose ownCloud (or generic WebDAV for non-ownCloud servers).
Enter a display name (e.g. “ownCloud — production”).
Enter the WebDAV URL:
- ownCloud Server (PHP): https://<your-domain>/remote.php/dav/files/<username>/
- ownCloud Infinite Scale (oCIS): check your oCIS deployment’s WebDAV documentation for the namespace pattern (typically involves Spaces).
Enter the username matching the URL placeholder.
Enter the app password from step 5 above (or your regular password if 2FA is off).
Click Confirm — CloudsLinker validates with a PROPFIND request and shows the connection ready.

Self-hosted prerequisites (PHP Server)

For uploads larger than 2 MB on the PHP-based ownCloud Server, ensure your server has:

php_value upload_max_filesize 16G and php_value post_max_size 16G in php.ini
client_max_body_size 16G in nginx (or equivalent in Apache)
php_value max_execution_time 3600 for slow uploads

Infinite Scale (Go-based) doesn’t need PHP tuning — file size limits are configured directly in oCIS settings.

Revoke access

To revoke CloudsLinker’s app password later: ownCloud → Personal Settings → Security → App Passwords → find the entry → click delete. The app password becomes immediately invalid.

ownCloud upload & download limits you should know

ownCloud is self-hosted, so most “limits” are configurable — defaults depend on the product line:

Two product lines:
- ownCloud Server (PHP, legacy, maintenance mode)
- ownCloud Infinite Scale (oCIS) (Go, modern, recommended for new deployments)
Default chunk size: 10 MB for chunked uploads on both lines, allowing arbitrarily large files regardless of PHP upload_max_filesize.
PHP Server defaults: upload_max_filesize 2 MB out of the box; raise to 16 GB+ via php.ini.
Reverse-proxy: must also raise client_max_body_size in nginx to match PHP limits.
oCIS file size: configurable in deployment settings, with no inherent PHP-imposed cap. Some users report ~100 MB folder upload issues on oCIS v7.1.1 — check release notes for fixes.
WebDAV authentication: username + password, or app password if 2FA enabled.
Storage capacity: whatever you provision (local disk, NFS, SMB, S3-compatible object storage).
Per-user quota: configurable by admin; default unlimited.
Trash retention: default 30 days, configurable.
Version history: enabled by default.
API rate limits: ownCloud applies brute-force protection on auth; otherwise no per-user rate limiting by default.
Enterprise features: workflows, advanced tagging, branding gated behind Enterprise license.

Sources: ownCloud: Big File Upload Configuration, ownCloud: Large File Uploads, ownCloud: Unlimited File Size feature, ownCloud Central: oCIS file size limit.

ownCloud + CloudsLinker — Frequently Asked Questions

What's the difference between ownCloud Server and ownCloud Infinite Scale?

ownCloud Server is the original PHP-based product (10+ years old), now in maintenance mode — still widely deployed, still supported, but not actively gaining major features. ownCloud Infinite Scale (oCIS) is the 2024+ ground-up rewrite in Go, designed for container-native deployment and significantly better performance under load. New deployments should use oCIS; existing Server deployments should plan a migration path.

Should I use ownCloud or Nextcloud for new deployments?

Both are fundamentally similar (Nextcloud forked from ownCloud in 2016 and they share architectural DNA). Pick Nextcloud for community focus, AGPLv3 license uniformity, full productivity suite (Calendar, Talk, Office), and the broadest plugin ecosystem. Pick ownCloud (especially oCIS) for enterprise-focused deployments, Go-native performance, and Kiteworks' enterprise-data-sharing roadmap.

What WebDAV URL does ownCloud use?

ownCloud Server (PHP): https://<your-domain>/remote.php/dav/files/<username>/. ownCloud Infinite Scale: a slightly different namespace structure with Spaces — check your oCIS deployment's WebDAV documentation for the exact URL pattern. CloudsLinker accepts either format.

Why does WebDAV fail with my normal ownCloud password?

Almost always because 2FA is enabled. WebDAV doesn't support TOTP prompts during HTTP basic auth — ownCloud requires an app-specific password generated from Personal Settings → Security when 2FA is active. Same pattern as Nextcloud.

What's the maximum file size I can upload?

Depends on your ownCloud configuration. Default chunk size is 10 MB — chunked uploads bypass PHP's upload_max_filesize limit. With proper PHP and reverse-proxy tuning (upload_max_filesize 16G, post_max_size 16G, client_max_body_size 16G), files up to filesystem limits work. ownCloud Infinite Scale (Go-based) handles large files more cleanly than the PHP Server.

Are my ownCloud credentials safe with CloudsLinker?

Yes. Username and password (or app password) are encrypted at rest with AES-256 and decrypted only inside the active transfer worker. Best practice: create a dedicated app password from ownCloud's Personal Settings → Security, separate from your main login password — revocable individually if any compromise is suspected.

Does CloudsLinker support ownCloud's S3 backend?

CloudsLinker connects via WebDAV regardless of what storage backend ownCloud uses. If your ownCloud writes to AWS S3 / Wasabi / B2 underneath, CloudsLinker reads files via WebDAV the same way it would from local-disk storage. Performance follows the underlying backend.

How fast can CloudsLinker push data into ownCloud?

Throughput depends on three factors: (1) ownCloud server CPU/disk speed, (2) network path between CloudsLinker and your server, (3) PHP and reverse-proxy configuration. Typical throughput against a modest VPS-hosted ownCloud Server is 50–150 GB/day; oCIS deployments often hit 200–400 GB/day per connection due to Go's better concurrency.

What happens to ownCloud federated shares during migration?

Federated shares (file shares between separate ownCloud / Nextcloud instances) are remote pointers, not local files. CloudsLinker copies local content; federated remote content needs to be re-shared on the destination instance after migration.

Is this an official ownCloud / Kiteworks partnership?

No. CloudsLinker is a third-party tool that uses ownCloud's standard WebDAV API. Revoke access by deleting the app password from Personal Settings → Security in your ownCloud instance.

Conclusion

ownCloud — the original self-hosted file cloud, now under Kiteworks' enterprise focus — has two parallel product lines in 2026: legacy PHP Server (maintenance) and the modern Go-based Infinite Scale. CloudsLinker connects to either via standard WebDAV with app password support, handling chunked uploads and S3 backends transparently. Connect with your ownCloud URL + credentials and run your first migration in minutes.

Start Your Free ownCloud Transfer