Migration from Owncloud 9.1.6 to Nextcloud 10.0.5 fails

When trying to switch fom Owncloud 9.1.6 to Nextcloud I get the following error:

Current version is 9.1.6.
Migration to Nextcloud 10.0.5 available.
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-10.0.5.zip
Retry update
Check for expected files
Check for write permissions
Enable maintenance mode
Create backup
Verifying integrity
Downloaded version is lower than installed version

I tried to make the upgrade manually with the same problem…

When I Try to manually upgrade to Nextcloud 11 I get the Error:

Exception: Updates between multiple major versions and downgrades are unsupported.
Update failed

Thanks for help…

Best regards


afaik 9.1.6 was released recently so its marked as a stable upgrade yet

But I still have the Error:
Downloaded version is lower than installed version

In my case it was the same problem. As a workaround I modified the version of my owncloud virtually to This can be done by modifying the file config/config.php in your owncloud installation directory (modify the string ‘version’ => ‘’ to ‘version’ => ‘’). After this you are able to manually install nextcloud (haven’t tried this with the installer method).

@Patrick_Morgenstern you shouldnt do that. ownCloud uses a different database migration system which has to be manually adjusted in Nextcloud so this might leave you with a broken database

Maybe you are right and it was luck. But in my case the written down method worked fine. All apps (Calendar, Contacts, Files) are running without problems. The update to newest NextCloud 11.0.3 after checking NextCloud 10.0.5 went also fine.
Anyway thanks you for your hint … this could be a problem on other installations. :slight_smile:

When will a compatible Nextcloud version be released? is this 10.0.6?

The latest Nextcloud 10.0.5 has same engine as Owncloud 9.1.5
Since Owncloud 9.1.6 has a newer engine, the process fails with message “Downloaded version is lower than installed version”

1 Like

I’m also interested in how this is going to be addressed… I didn’t even know about Nextcloud last week when I updated ownCloud through my package manager to 9.1.6 as usual, and suddenly the calendar app was throwing an error. I Googled that and found out it’s probably not being supported for ownCloud. So I looked at Nextcloud migration and it told me that it can upgrade 9.1.* to Nextcloud 10, and even the update script told me that an upgrade from 9.1.6 to 10.0.5 is possible, and created a backup. Then it failed in the middle of it, and I couldn’t find any information on whether there’ll even be a Nextcloud 10.0.6 or if I somehow need to fix this manually.

Some sort of statement or link to current plans would be appreciated, because now my calendar hasn’t been working for a week because the app was left in a broken state.

@frankagricola @derula when its done

1 Like

First: thank you for a very nice software :slight_smile:

Searching this forum i see this problem in this thread is not new, it have happened for other users for an earlier version too.
The bug here is in your instructions, that clearly say the latest point releases should be used when migrating:
From https://nextcloud.com/migration/

… Nextcloud 10.0.x as an upgrade to ownCloud 9.1.x

These are some examples of an upgrade path. The minor release (.x below) should always be the latest bugfix release.

So you (accidentally) fool admins to update ownCloud to latest point release even when it is known not to be compatible when NC point release is behind!

What it really should add is something like: the Nextcloud point release must not be lower than the ownCloud point release. Exampe: Nextcloud 10.0.5 is NOT compatible with ownCloud 9.1.6.

Please correct your migration guide ASAP before more people get fooled!

I hit this while evaluating upgrade+migration method for ownCloud in Mageia 5 to Nextcloud in Mageia 6. https://bugs.mageia.org/show_bug.cgi?id=21066#c7 ( which i am trying to make nice at https://wiki.mageia.org/en/OwnCloud#IMPORTANT:.2ABEFORE.2A_upgrading_to_Mageia_6.21 - improvements and corrections are welcome, BTW )_

Sincerely /Morgan


Hi @Morgano please report this on the appropriate issue tracker https://github.com/nextcloud/nextcloud.com :wink:

Instruction: https://github.com/nextcloud/server/issues/5426 (first issued as https://github.com/nextcloud/nextcloud.com/issues/496 )
Script: https://github.com/nextcloud/server/issues/5425 (first issued as https://github.com/nextcloud/nextcloud.com/issues/497 )

@Morgano thanks for filing the issues. The Nextcloud updater should ignore minor versions (the .5 vs .6) on migration between different products (oC to Nc), but apparently something is wrong. It might be that oC didn’t properly set the vendor on install or update, there was a bug with that. Once 10.0.6 is out it should of course work but this isn’t nice so we have to look if we can work around it…

A work-around from this blog is to set the version of your ownCloud server to, see:

edit your config/config.php and set version to or lower.

From @nickvergessen - if the reason is that oC didn’t set the vendor properly, you should run this before you try to upgrade to Nextcloud:

occ config:app:set --value "owncloud" core vendor

Reading from posts earlier in this thread, and other places, I am told that OC 9.1.6 use a newer engine than OC 9.1.5 and NC 10.0.5, so that is not a safe path anyhow. Or is there news on that?

It do seem to work for some anyhow, but i am trying to define an official upgrade path for Mageia 5 (owncloud) to Mageia 6 (nextcloud) that is doable ASAP. https://bugs.mageia.org/show_bug.cgi?id=20953#c21 , https://wiki.mageia.org/en/OwnCloud#IMPORTANT_:.2ABEFORE.2A_upgrading_to_Mageia_6.21

It there any idea yet when NC 10.0.6 (or other compatible NC) is out: like in a week, or four weeks?
If soon, maybe we can get NC 10.0.6 into Mageia5 backports

I agree with the assesment from the blog on https://0xstubs.org/migrating-from-owncloud-9-1-6-to-nextcloud-10/ that there don’t seem to be any changes to the database, which would indeed be unlikely in such a late-in-the-series bugfix. This should not cause any problems.

However, I’m testing this myself now with a fresh 9.1.6 and will try to fix this out. Will get back to you all.

Many thanks :slight_smile:
If the workaround is safe, it will save a lot of people some work.

In my case, I had to set version in file version.php. When I set config/config.php, the updater still recognize installed owncloud version as 9.1.6.

In the end, migration from owncloud 9.1.6 (faking it as a version) to nextcloud 10 to nextcloud 11 went well.

1 Like

FYI - https://github.com/nextcloud/owncloud-web-migrator/issues/1

I modified version.php to refer to which worked for me but didn’t work for a user on twitter. We have to fix the migration script… The upgrade itself, if you manually replace the files that is, does work.