Community | News from ownCloud | ownCloud | Product | security | Updates

ownCloud Classic 10 reaches end of support on 31 December 2026: your two paths forward

We want to bring your attention to the end of support for ownCloud Classic 10. It reaches end of support on 31 December 2026, so from January 2027 it is end of life, as already listed in our public Maintenance and Release Schedule. If you run ownCloud Classic 10, you have two good options: upgrade […]

We want to bring your attention to the end of support for ownCloud Classic 10. It reaches end of support on 31 December 2026, so from January 2027 it is end of life, as already listed in our public Maintenance and Release Schedule.

If you run ownCloud Classic 10, you have two good options: upgrade to ownCloud Classic 11, or move to ownCloud Infinite Scale (oCIS). This post walks through both in detail. We link to the official documentation for every step instead of rewriting it, because the docs are the one place we keep current.

Why Classic 10 is reaching end of support

Classic 10 runs on technology that has aged out, and we can no longer keep it secure in a reliable way. Its PHP 7.4 runtime has itself reached end of life, and running a production system on an unsupported runtime is a compliance problem, especially in the public sector. We said as much in April, when we announced PHP 8.3 for Classic.

ownCloud Classic 11 shipped on 30 July 2026. It needs PHP 8.3, removes legacy code we could not maintain safely any more, and the 11.0.0 release alone contains 11 security fixes.

What end of support means if you stay on Classic 10

From 1 January 2027, ownCloud Classic 10 no longer gets security patches or bug fixes. It may keep running after that date, but newly discovered vulnerabilities will not be fixed. The longer you stay on it, the more likely you are to run into security incidents or outages. It may also stop working with newer operating systems and third-party software, and it may no longer meet regulatory requirements. If you keep running it, you do so at your own risk, including the risk to your data.

Path 1: Upgrade to ownCloud Classic 11

Classic 11 is the same Classic you know, so there is no new platform to learn. Upgrades are supported from 8.2.11, 9.0.9 and 9.1 onwards, so every 10.x installation has a direct path. Read the 11.0.0 announcement before you start, because it lists every breaking change.

Classic 11 runs in Docker only

Starting with Classic 11, the only supported installation method is a Docker-based installation that includes PHP 8 and Apache. Manual installation on Linux is no longer supported, and a non-Docker setup is out of support. The official image is owncloud/server.

Pin an explicit version tag, never latest. The docs use owncloud/server:11.1.0 as their example, and explain that latest does not track the newest Classic release and that there are no rolling major or minor tags. Pinning also means you decide when an upgrade happens, not a container restart. Once Classic 11 runs in Docker, you run occ with docker compose exec owncloud occ <command>, without a php prefix.

Pick your route

You run Classic 10 Follow this guide What it covers
In Docker already Docker to Docker No data migration. In outline: maintenance mode, disable and delete the apps provided by ownCloud (updated ones are embedded in the new image), bring the compose environment down, set the Classic 11 image, pull and start it, leave maintenance mode, then run the occ upgrade.
On a VM or from packages Native to Docker More than an in-place update. The guide assumes a different server, and covers migrating the data directory, moving config.php settings to environment variables, bringing over apps that are not part of Classic 11, and a reverse proxy in front of the embedded Apache. Kerberos, Windows Network Drive and custom preview settings need your own image.

The outline above only tells you what to expect. Follow the guide itself for the exact steps, and test in a non-production environment first.

Before you start

The upgrade guide asks you to:

  • Take a fresh backup before the upgrade.
  • Read the release notes.
  • Expect maintenance mode during the upgrade, and allow several hours on large installations.
  • Review your third-party apps for compatibility, disable them before the upgrade, and re-enable the compatible ones afterwards. Unsupported apps may disrupt the upgrade.
  • Remember that downgrading is not supported. To go back, do a fresh installation and restore from backup.

With a few exceptions, Classic 11 provides its configuration keys as environment variables, and the docs recommend moving your settings there. See the configuration notes.

What changes in Classic 11

  • Group admins are off by default. Existing group-admin (subadmin) assignments are ignored until you set ‘allow_subadmins’ => true in config.php.
  • Apps come with the image. The image ships the apps provided by ownCloud, updated for PHP 8, regardless of licensing scheme. That is why the guides have you remove the old ones first.
  • Third-party apps must be Classic 11 ready. That includes PHP 8.3 and a G2 signature. Old G1 signatures stop verifying after 31 December 2026 (23:59:59 UTC), so please ask your app maintainers for updated releases if they are not yet available.
  • Some apps left the bundle: web, impersonate, kerberos, sharepoint, templateeditor and updater. They were dropped without an alternative at hand. The updater app is gone because you now upgrade by pulling a new image. If you depend on one of the others, let us know on the Central forum or in GitHub Discussions so we know what is needed.
  • Some commands were removed. occ integrity:sign-app and occ integrity:sign-core are gone (only app developers need them, and integrity:check-* still works).
  • If you set htaccess.RewriteBase, run occ maintenance:update:htaccess after upgrading.

Path 2: Move to ownCloud Infinite Scale (oCIS)

oCIS is where ownCloud is heading, and you can move there today if files and sharing are what you use. The official guide is Migrating to ownCloud Infinite Scale. It transfers users, groups, files and shares from your Classic instance to a target oCIS in sequential steps. Your Classic server is not modified and stays operational for most of the process.

Is it right for you?

The migration guide covers users and groups with their memberships, the files in each enabled user’s home directory (they land in that user’s personal Space, transferred with the bundled rclone), and user, group and link shares. Calendars and contacts are not part of it.

If you rely on calendars and contacts, Classic 11 is the better stop for now. The Calendar and Contacts apps are available through the Marketplace for Classic 10 and 11 (see the docs for Calendar and Contacts), and we are working on a native answer for oCIS, described below.

What you need

Requirement Details from the guide
A running oCIS Fully configured, reachable from your Classic server, and fresh and clean before you start. See the oCIS docs, the deployment guide and the Ubuntu with Docker Compose example.
The auth-app service with impersonation Set OCIS_ADD_RUN_SERVICES: “auth-app”, PROXY_ENABLE_APP_AUTH: true and AUTH_APP_ENABLE_IMPERSONATION: true on oCIS. Then create an app token for the oCIS admin user with the auth-app service.
The migration app on Classic Version 3.0.0 for Classic 11 (PHP 8.3 or newer, oCIS 7.1.0 or newer). Version 2.0.1 for Classic 10. It is also part of the Complete bundle. Install it as described in Installing and Managing Apps: copy it into the apps or apps-external folder, set permissions, enable it with app:enable migrate_to_ocis.
Shell access Every migration step is an occ command.
Valid, unique emails All enabled users need a valid email address, unique across enabled users. migrate:to-ocis:verify reports problems.
A plan for identities Local and LDAP users cannot be combined. For production, the guide recommends a real LDAP server or an external identity solution over oCIS’s built-in IDM, which suits small installs and testing.

If you use LDAP, the guide adds requirements. LDAP users must have the email attribute set, and the username attribute should be uid or samAccountName (the guide shows ldap:set-config ” ldapUserName uid). On oCIS, check OCIS_LDAP_USER_ENABLED_ATTRIBUTE, OCIS_LDAP_USER_SCHEMA_ID, OCIS_LDAP_GROUP_SCHEMA_ID and OCIS_ADMIN_USER_ID. If you need to migrate passwordless share links, set OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false on oCIS first, because oCIS requires a password on links by default.

What does not come across

  • Disabled users, their files, and shares created by or targeting them. The migration reports errors for the shares and carries on.
  • Migrated users have an unknown password, so plan a reset or onboarding process. Passwords on link shares change too, and users should update them.
  • External mounts. You recreate them and migrate their data manually.
  • Classic roles are not preserved. Everyone gets the one role you pick, and group-admin (subadmin) rights have no oCIS equivalent. Members of the Classic admin group keep the group membership but get oCIS admin rights only if the assigned role grants them.
  • Users who never logged in are skipped, since they have no files.

How it goes

The guide describes three phases: user and group migration, preparing the data migration with migrate:to-ocis:init and migrate:to-ocis:verify, and then migrate:to-ocis:migrate:files and migrate:to-ocis:migrate:shares. If you migrate local users into the built-in IDM, the commands are migrate:to-ocis:migrate:users, migrate:to-ocis:assign-role and migrate:to-ocis:migrate:groups, and the guide has you run the preparation phase first. Please follow its order and exact commands, and see the occ reference.

Three things are worth knowing up front. Make no user or group changes after the user and group step. A completed step cannot be repeated without deleting the data it created. And if you need to start over, migrate:to-ocis:init has a –force flag, but data already on the target stays there, so use a clean oCIS.

Calendar and contacts: what we are working on

We know calendars and contacts are what keep many of you on Classic, and we are working on calendar and contacts integration for oCIS. The ownCloud team are building ocis-groupware, an Apache-2.0 project that adds CalDAV and CardDAV, a Graph-style API and Calendar and Contacts apps to oCIS Web. It supports sharing with users and groups, iCalendar and vCard import and export, and app passwords for DAV clients. It also has an admin command that copies calendars, address books, shares and app tokens out of a Classic database. Public links and subscriptions are reported as not migrated, and the migration docs in the repository explain the details.

Please treat it as work in progress. Today it runs as its own service next to oCIS, behind the same domain. We will tell you here when it is ready for production use. In the meantime, the most useful thing you can do is try it, open issues and send pull requests.

You may have seen that the answer on the forum used to be that CalDAV and CardDAV were not planned for oCIS. That has changed because of interest and requests for this feature from the community.

Why 31 December, and why Classic 11 is a bridge

Three things land on the same date. Classic 10 support ends, the old G1 app signatures stop verifying, and your migrations over the next weeks show us what breaks on real installations, which makes the path smoother for everyone who moves in 2027.

Classic 11 is a bridge, and we want to be straight about that. We plan to support it through 31 December 2027 and will confirm that date on 30 June 2027. Until then we are working on what oCIS needs to take everyone along: a one-path installer in get-owncloud, calendar and contacts for oCIS, and a smoother migration path.

Tell us how it went

We learn from every migration, good or bad. Please let us know how it went, what worked and what did not, in this ownCloud Central forum thread or in GitHub Discussions. Useful reports get a thank-you in the Contribution Spotlight.

Already upgraded? Thank you, and please ignore this note.

About the Author

Jordana Fung is the Open Source & Community Manager at Kiteworks, where she helps build and lead the company’s new Open Source Program Office (OSPO). A longtime contributor and active member of the open-source community, she brings years of experience as a developer, mentor, and speaker. Jordana previously served as chair of the Drupal Community Working Group, contributing to both the Community Health and Conflict Resolution teams — working to cultivate a welcoming, inclusive, and healthy community. At her core, Jordana is a technical community manager and community-taught developer who thrives in collaborative environments. She is passionate about open source, knowledge and idea sharing, creating safe and brave spaces, and empowering people to do and be their best.

Jordana Fung

November 19, 2026

Read now: