Repository navigation
Migration path from Owncloud >= 10.14? #12199
Description
Activity
I think it is basically the same as you need to migrate to Nextcloud 25 first because of the supported PHP versions of ownCloud and Nextcloud. Then after the migration you can migrate from 25 -> 26 -> 27.1 -> 28 -> 29.
There is also more information available in the Nextcloud blog: https://nextcloud.com/blog/owncloud-to-nextcloud-migration/
It was just updated a couple weeks ago: #12124
I'll move this to the docs repo though.
Thanks.
Maybe I was too fast.
owncloud is currently in 10.15.0, the docs refer to 10.13.x -> NC.
Will it work with 10.15.0 too?
- changed the title
[-]Migration path from Owncloud?[/-][+]Migration path from Owncloud >= 10.14?[/+]on Sep 15, 2024 Any updates yet?
Related to [Ticket#9668648]Hi,
I just executed my local migration with 10.15 and did not see any main issues 👍🏻While I just now migrated a staging machine and it took like 3 hours, I needed to apply nextcloud/server#49523 manually.
Now I came across the question: Why do I need to start with 25.x?
The old php version should not matter, if you juts download some .tar archive extract it and run occ upgrade.
Is the "upgrade path" just to be able to do it "without downtime"?
Cant I start directly with 30.x?
Hello @someone-somenet-org
the php version does matter. oC only works with php7.4. NC30 only works with php8.xwhat you can try is to stop oC; upgrade the whole Server to the newest OS/PHP and then start the occ upgrade on NC30.
Its not officially supported. But you have proper Backups in place, do you?The question is: is OC10.15 -> NC25 -> NC26 -> NC27 -> NC28 -> NC29 -> NC30 more supported than OC10.15 -> NC30 (and why)?
In both cases i have to edit the version.php file to make it work and both NC25 and NC30 have "migration is supported from owncloud 10.13", so I think both paths are not really officially supported but both should work equally well and due to my instances' size, its impossible to do any migration without downtime anyway, so It doesnt really matter to me if I grab a fresh VM and provision it with php8.2 from the get go and start with NC30 ... the question is, whether its more likely that something subtly breaks.
I didnt come across anything except for the no working AD/LDAP logins so far (both NC25 and NC30 affected), but that doesnt mean subtle breakage cannot happen and if its subtle backups wont help as if I notice half a year later that i should have gone the other way, because some data was lost, there is no way to roll back to backups that are half a year old.
(Sure I have backups... its a staging box after all, so in the worst case i can always copy over the production data. And yes, its a huge instance (cant open the admin->accounts page; it works with owncloud tho) and i cant get nc enterprise before i can show promising migration results and drop-in replacement feasibility)
I have done multiple migration tests via the OC10.15 -> NC30 path and the OC10.15 -> NC25 -> NC26 -> NC27 -> NC28 -> NC29 -> NC30 path.
They feel the same and I end up with the same unresolved issues afterwards.
Yet it would be cool to get a clarification if both are equally safe.
We were able to migrate several instances from owncloud 10.15 latest » Nextcloud 25 latest » Nextcloud HUB9.
What made the trick was firstly to change the versionstring to 10.13.0.4 within the config.php and secondly to create the folder called
/var/www/nextcloud/apps-external
as described here.The question is: is OC10.15 -> NC25 -> NC26 -> NC27.1 -> NC28 -> NC29 -> NC30 more supported than OC10.15 -> NC30 (and why)?
Yes this is the supported migration path, to make sure all migrations (speaking of e.g. database migrations or app data) are run correctly.
I do recommend the standard/supported migration path only.
The db differs from oC to Nc - you will have troubles.Last week I received an email from kiteworks saying "that ownCloud 10.14 and all versions earlier will reach end-of-life by December 31, 2025."
I'd highly appreciate direct migration support from ownCloud 10.15 to nextcloud 31.
@criegerde Thank you for your documentation which is very helpful until then.
I tested both paths extensively and I dont see a reason why the short migration path would not work.
It would actually make much more sense, as getting old versions of php is getting more difficult by the day.
But since we have a big instance to migrate we dont want to end up in a situation where Nextcloud enterprise support will tell us we are on our own, since we did the fast migration, we will stick with the official slow one...
yay for 1-2 days of downtime... our users will hate us.
Since Kiteworks (owncloud owner) seems to have increased their subscription prices there might be increased interest to migrate to Nextcloud.
Could you therefore update the migration page to the newest possible info there is:
https://docs.nextcloud.com/server/latest/admin_manual/maintenance/migrating_owncloud.html