Move ownCloud Classic to oCIS with a Supported Migration
Plan an ownCloud 10 to oCIS migration with the supported app, ordered commands, identity checks, and a clear list of data that needs separate handling.
Use ownCloud’s dedicated migrate-to-ocis app and its occ commands to transfer users, groups, files, and supported shares from ownCloud Classic 10 to a separately installed ownCloud Infinite Scale (oCIS) instance. This is a staged migration, not an in-place upgrade: the target needs to be reachable, prepared for authentication and impersonation, and clean of conflicting data. Plan for password resets, role reassignment, and manual handling of external mounts.
ownCloud’s current Server 10.16 migration documentation describes a supported path using an app supplied by ownCloud as part of a guided migration. The app is not available in the Marketplace; contact ownCloud support to obtain it. The source and target must both be configured, running, and able to reach one another. You also need SSH access to the Classic server and the ability to run occ commands as the web server user.
The documented migration transfers enabled users and groups, files in each enabled user’s home directory, and user, group, and link shares. It does not transfer disabled users, files owned by disabled users, passwords, or external mounts. Received shares and files in external mount locations are excluded from the file transfer. If your users rely on mounted SMB/S3 storage, shared admin mounts, or existing external repositories, inventory them and plan a separate copy and recreation process before scheduling cutover.
For example, a small team with local accounts and files in personal home directories may be able to use the built-in local-user migration flow. A company whose accounts are in LDAP should first ensure that oCIS can resolve the same users and groups, then follow the LDAP-specific requirements. A mixed population of local and LDAP users is not supported by the documented procedure. For production or larger deployments, ownCloud recommends a real LDAP or external identity management system over the limited embedded oCIS IDM.
migrate-to-ocis app from ownCloud support, install it in the Classic apps or apps-external directory with the correct ownership, and enable it. Example, assuming the default installation path and Apache’s www-data account:sudo -u www-data php /var/www/owncloud/occ app:enable migrate_to_ocis
Adjust the path and operating-system account to match your installation. The migration app bundles its own rclone binary, so do not substitute a separate manual copy procedure for the documented app workflow without a migration plan from ownCloud.
auth-app service and impersonation. The documented environment settings are OCIS_ADD_RUN_SERVICES: "auth-app", PROXY_ENABLE_APP_AUTH: true, and AUTH_APP_ENABLE_IMPERSONATION: true. Create an app token for the oCIS admin through the auth-app. The migration uses the admin username and this token for oCIS operations. Store the token securely; do not paste it into a shared shell history or article configuration.uid or samAccountName, rather than an internal UUID that does not match oCIS identities. User and group names must match across the relevant systems. Do not add, delete, or rename accounts or groups after the migration’s identity stage.Commands below use /var/www/owncloud, www-data, and an oCIS host named ocis.example.com as examples. Replace them with your actual values. The admin password is requested interactively by the migration commands.
sudo -u www-data php /var/www/owncloud/occ migrate:to-ocis:init ocis.example.com
sudo -u www-data php /var/www/owncloud/occ migrate:to-ocis:verify
Review verification output and fix missing or duplicate emails before continuing. Do not skip verification simply to move faster; the documented skip option makes email-related problems your responsibility. Avoid --insecure except for a controlled test with a certificate problem you understand. Fix TLS trust for a production migration.
sudo -u www-data php /var/www/owncloud/occ migrate:to-ocis:migrate:users ocis-admin
sudo -u www-data php /var/www/owncloud/occ migrate:to-ocis:assign-role ocis-admin
sudo -u www-data php /var/www/owncloud/occ migrate:to-ocis:migrate:groups ocis-admin
The role assignment step is mandatory. One selected oCIS role is assigned to migrated Classic users; Classic roles are not preserved, and subadmin privileges have no equivalent role. Check administrator accounts individually and grant elevated oCIS privileges only where intended. If LDAP already provisions the users, follow the official LDAP route and use the supported skip options where instructed instead of duplicating accounts.
sudo -u www-data php /var/www/owncloud/occ migrate:to-ocis:migrate:files ocis-admin
sudo -u www-data php /var/www/owncloud/occ migrate:to-ocis:migrate:shares ocis-admin
Files in each user’s Classic home directory are transferred to that user’s personal Space. External mounts and received shares are excluded. The shares command handles user, group, and link shares, but errors involving missing users or groups can be reported while migration continues. Password-protected links receive a new password that will not match the Classic password; passwordless links may fail under the default oCIS policy. Tell users to replace published links and distribute updated passwords through a secure channel.
After the commands finish, compare a sample of users, groups, folder trees, file counts, permissions, and key shares against your inventory. Test with ordinary user accounts, not only the administrator. Confirm that external storage has been recreated and its data copied through a separately planned process. Prepare password resets or onboarding because migrated users’ old passwords are not transferred.
Keep the Classic service available while validating and communicating the change. For a consistent final cutover, schedule a write freeze, prevent new changes on the source, and account for any changes made since the migration run; the documented sequence is not a promise of continuous synchronization. Only redirect users and clients after the checks pass. Keep a rollback window and a known-good backup, and do not reset and rerun against a populated target without understanding the documented reset behavior: --force restarts migration state but leaves already migrated target data in place, so the target should be cleaned before restarting.
Plan an ownCloud 10 to oCIS migration with the supported app, ordered commands, identity checks, and a clear list of data that needs separate handling.
Replace ownCloud Classic 10 logos and tune web UI colors with a theme app, while avoiding upgrade and integrity-check pitfalls.
Assign byte-based storage limits to new ownCloud Infinite Scale users by role, with a proxy.yaml example and a safe verification checklist.
Restore ownCloud desktop syncing by checking the server hostname, certificate chain, private CA trust, and captive portal issues without disabling TLS verification.
Use the invalid-file report to identify mismatched core files or app signatures, restore the correct release files, and verify the integrity check safely.
Deploy ownCloud Infinite Scale from its official Compose example, configure domains and persistent storage, then verify TLS, containers, and first login.
Set up the S3NG driver, bucket permissions, persistent metadata storage, and upload sizing so ownCloud Infinite Scale can store file contents reliably.
Find why an ownCloud Server upload stops near completion by checking file status, quota, temporary disk space, PHP limits, and proxy timeouts.
Set AllowOverride All only for ownCloud’s web root, validate the active Apache vhost, and reload safely to restore .htaccess rules.
Enable ownCloud’s Enterprise Auditing app, route admin_audit events to a protected log file, and confirm that real user actions are being recorded.