Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114 3 reasons to upgrade your ownCloud instance to Nextcloud and how easy it is - NextcloudSkip to main content
EDIT in 2022: as users still ask about migration, we have added up-to-date instructions to our documentation! Best use those, the instructions below are only relevant for the older versions!
Since ownCloud 10.0.0 was released, many users have been asking us how to migrate to the latest version of Nextcloud. We have turned our update mechanism into a easy to use migration tool to make it as easy as possible to move over and get the benefits of Nextcloud!
In this blog, we will give you three good reasons to migrate and a short walk-through of using our migration tool. Jump immediately to the instructions if you’re already convinced it is time to move over!
ownCloud vs Nextcloud – why would I migrate?
Last week, Nextcloud 12 was released and thousands of users upgraded their Nextcloud instances, many of whom shared how great the upgrade experience had been and how they appreciated Nextcloud 12 on Twitter and other social media. Nextcloud 12 is a big upgrade, delivering significant new capabilities around communication and collaboration. It builds those improvements on the very solid base of Nextcloud 11 which set a new standard of stability, performance, and security in open source file sync and share technology.
There are three simple, clear reasons to migrate your ownCloud system to Nextcloud.
First, stability. Nextcloud 12 is a far more reliable update than the latest ownCloud according to comments from users on social media while Global Scale shows we have the know-how to truly move open source file sync and share technology forward.
Second, security – if this is an important concern to you, Nextcloud is the only option that puts its money where its mouth is with a third-party verified focus on secure development backed by a 5K Security Bug Bounty program.
And last, Nextcloud 12 extends the lead we have in features over other solutions.
Upgrades of #Nextcloud are just jaw-dropping, upgrade to 12 took literally 5 min of my time. Kudos to @Nextclouders!
Nextcloud 11 was widely praised for its stability and reliable upgrades. Our experienced team, with most people having 3 to over 7 years experience working on ownCloud and now Nextcloud, built a new updater and did extensive testing together with our community.
We already updated our internal Nextcloud server to the Nextcloud 12 beta even before it was released. Using your own product is a great way to make sure it is reliable and it avoids obvious issues like a broken LDAP or losing calendar and contacts data – we would fix those right away that as we use the Calendar, Contacts and Mail apps daily ourselves!
But don’t take our word for it. You can simply search social medial like Twitter and compare.
Testing also involves community contributions and apps. Nextcloud already had dozens of apps available for Nextcloud 12 before the beta was even out. You’ll also notice apps are typically very up to date on the Nextcloud app store, as they are primarily developed in the Nextcloud community.
So far so good with the new #nextcloud update to version 12. Easy upgrades per usual with @Nextclouders
— Zachary Rohrbach (@zacharyrohrbach) May 22, 2017
The results of this work become publicly visible on HackerOne. You can read the entire process of finding, analyzing and fixing a security issue reported by a security researcher in, for example, this recent XSS vulnerability.
Nextcloud 11 was mostly focused on massive scalability and security improvements. It performed easily 60% faster in large installations than previous versions and introducing a wide range of security improvements like brute force protection, CSP 3.0, password verification and more. While Nextcloud 12 will feature further enhancements in both areas, even our December release is still significantly ahead and will lower your server load and improve responsiveness for users compared to any ownCloud release out there.
Nextcloud 12 expanded its lead with many new collaboration and communication features. For large installations but also benefiting smaller, Nextcloud has started development of a major new architecture, Global Scale, which brings orders of magnitude better scaling, lowers cost, and give more control over data locality to enterprise users.
If you are currently on ownCloud 10.0.0 or an even earlier release, upgrading is extremely easy thanks to our brand new ownCloud-Nextcloud migration tool! Here’s how to use it.
Use a comand line terminal to log in to your ownCloud server and navigate to the folder where ownCloud is installed and execute these commands:
grab the update script: wget https://download.nextcloud.com/server/installer/migrator/index.php
put it in the updater folder: mv index.php.1 updater/index.php
(there is already an index.php in the ownCloud folder so the newly downloaded one will be called index.php.1)
Now go in your browser to the URL of your ownCloud server, say your.owncloudserver.cop and append updater/index.php: your.owncloudserver.com/updater/index.php
You should now see our migrator. Just follow the steps! Watch our video below to see how easy it is.
You can do the final step manually from the command line, which is advised on large installations where the time-out on PHP via the web interface can be a problem. Note that ownCloud 10.0.1 can not yet be migrated to Nextcloud 12, we are still testing this upgrade path to make sure it is 100% reliable!
You can also, of course, do all this the manual way. For example, to upgrade from ownCloud 10.0.0 to Nextcloud 12, you log into the ownCloud server, navigate to the folder where ownCloud is installed and:
Turn on Maintenance Mode by editing config/config.php and setting 'maintenance' => true,
Add the item if it isn’t yet there. You can also use the command line tool (replacing www-data with what is relevant on your platform): sudo -u www-data php occ maintenance:mode --on
Move old folder out of the way: cd .. && mv owncloud OLDcloud
Grab the latest Nextcloud 12 and extract it: wget https://download.nextcloud.com/server/releases/latest-12.zipunzip latest-12.zipmv nextcloud owncloud
(you can keep it a nextcloud folder but you’ll have to adjust your server configuration that way)
Move in the config and data and start the update: mv OLDcloud/data owncloudmv OLDcloud/config/config.php owncloud/configsudo -u www-data php occ upgrade
Disable Maintenance Mode by editing config/config.php and set 'maintenance' => false,
You can also use the command line tool (replacing www-data with what is relevant on your platform): sudo -u www-data php occ maintenance:mode --off
Now you have all the benefits of a faster, more secure and more powerful private cloud solution with more capabilities and you can look forward to further enhancements thanks to our fast development pace!
“When we have welcoming communities of contributors, open source software gets better and more useful to everyone.” Limor Fried, Electrical Engineer, Inventor and Founder of open-source hardware company Adafruit We believe in this ideal and love to work with our community. We are always looking to involve more people in Nextcloud, bringing in their ideas, […]
When cables are cut, sanctions are put in place or privacy legislation prohibits the use of the service your entire organization depends on, what can you do? Amidst geo-political changes, organizations face dependencies on large, centralized communication platforms. A major example of this is the SaaS-only communication platform Microsoft Teams. It is the only solution […]
We save some cookies to count visitors and make the site easier to use. This doesn't leave our server and isn't to track you personally!
See our Privacy Policy for more information. Customize
Statistics cookies collect information anonymously and help us understand how our visitors use our website. We use cloud-hosted Matomo
Matomo
_pk_ses*: Counts the first visit of the user
_pk_id*: Helps not to double count the visits.
mtm_cookie_consent: Remembers that consent for storing and using cookies was given by the user.
_pk_ses*: 30 minutes
_pk_id*: 28 days
mtm_cookie_consent: 30 days