chore(admin): update ownCloud migration guide#15048
Open
MichaIng wants to merge 1 commit into
Open
Conversation
9 tasks
Contributor
📖 Documentation Preview📄 1 changed documentation pageLast updated: Sat, 30 May 2026 17:04:43 GMT |
nextcloud/server#59677 fixes direct migration from ownCloud to latest Nextcloud. It does not change something about the fact that latest ownCloud 10 does not support any PHP version supported by Nextcloud. But while keeping PHP 7.4 during the migration to Nextcloud 25 makes it easier to revert to ownCloud in case of an issue, that path requires manually patching `version.php`, a lot of major version upgrades, and intermediate PHP upgrade steps. Overall the efforts are a lot higher than migration directly to latest Nextcloud, and upgrade PHP only once prior to that. Another reason to prefer direct migration to latest Nextcloud is, that Nextcloud 25 migrations are not maintained anymore. There is hence a chance that some recent ownCloud 10 version introduces a change that causes a major or subtil issue during the migration, that is fixed only in Nextcloud versions which are not EOL. The migration steps have been adjusted to reflect the direct migration path to the upcoming Nextcloud 34.0.0. The table itself, to in case list different migration paths for different ownCloud versions, has been left in place, including the optional/conditional migration steps to further upgrade Nextcloud and in case PHP afterwards. However, to reduce maintenance efforts and simplify/clarify things, I'd vote for removing support for migration to any older Nextcloud versions entirely, and remove the target version and post-migration upgrade steps from the docs. Once latest Nextcloud removes support for migrations from ownCloud 10.13.x, it is probably better to simply remove this migration path from the docs, and require admins to upgrade ownCloud first. IMO, keeping support for (and documenting) migrations to Nextcloud versions, which themselves are not supported, and hence do not get possibly needed fixes for migration scripts and `version.php`, does not make sense. Let me know if you agree to the last point, then I'll adjust the commit accordingly. Signed-off-by: MichaIng <micha@dietpi.com> Signed-off-by: MichaIng <micha@dietpi.com>
MichaIng
force-pushed
the
update-owncloud-migration
branch
from
8d825ca to
7db6ca7
Compare
skjnldsv
approved these changes
May 31, 2026
Member
skjnldsv
left a comment
skjnldsv
left a comment
There was a problem hiding this comment.
Looks good, I'll wait for the other to check as well! Thanks !! :hug:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nextcloud/server#59677 fixes direct migration from ownCloud to latest Nextcloud.
It does not change something about the fact that latest ownCloud 10 does not support any PHP version supported by Nextcloud. But while keeping PHP 7.4 during the migration to Nextcloud 25 makes it easier to revert to ownCloud in case of an issue, that path requires manually patching
version.php, a lot of major version upgrades, and intermediate PHP upgrade steps. Overall the efforts are a lot higher than migration directly to latest Nextcloud, and upgrade PHP only once prior to that.Another reason to prefer direct migration to latest Nextcloud is, that Nextcloud 25 migrations are not maintained anymore. There is hence a chance that some recent ownCloud 10 version introduces a change that causes a major or subtil issue during the migration, that is fixed only in Nextcloud versions which are not EOL.
The migration steps have been adjusted to reflect the direct migration path to the upcoming Nextcloud 34.0.0.
The table itself, to in case list different migration paths for different ownCloud versions, has been left in place, including the optional/conditional migration steps to further upgrade Nextcloud and in case PHP afterwards. However, to reduce maintenance efforts and simplify/clarify things, I'd vote for removing support for migration to any older Nextcloud versions entirely, and remove the target version and post-migration upgrade steps from the docs. Once latest Nextcloud removes support for migrations from ownCloud 10.13.x, it is probably better to simply remove this migration path from the docs, and require admins to upgrade ownCloud first. IMO, keeping support for (and documenting) migrations to Nextcloud versions, which themselves are not supported, and hence do not get possibly needed fixes for migration scripts and
version.php, does not make sense.Let me know if you agree to the last point, then I'll adjust the commit accordingly.
☑️ Resolves
🖼️ Screenshots
Before:
After:
Would it make sense to split each ownCloud-Nextcloud version pair into their own table row, when keeping the table at all?
✅ Checklist
have builtlet github-actions build the documentationlocallyand reviewed the output (😅)codespellor similar and addressed any spelling issues