How to Migrate from Self-Hosted Nextcloud to Managed Nextcloud

Moving from self-hosted Nextcloud to managed hosting is not simply copying files to a new server. A complete Nextcloud environment may also contain accounts, groups, sharing permissions, calendars, contacts, file versions, application data, encryption settings, and external storage connections. If any of these elements are missed, your files may still be there, but the way you use them might not work as before.

This guide explains how to choose the right migration method, protect your data, complete the transfer, and check the managed environment before switching off your self-hosted server.

What changes when you move from self-hosted to managed Nextcloud?

Moving to managed Nextcloud does not mean starting over with a new platform. You can keep the familiar Nextcloud experience, and the right migration method can bring across your files, folders, contacts, calendars, sharing rules, and supported app data. What really changes is the work happening behind the login screen. Your provider takes care of running and maintaining the hosting environment, so you no longer have to manage the server yourself.

Whether you use Nextcloud on your own or across a company, managed hosting gives you back the time spent maintaining the server. You can continue managing your files, accounts, groups, permissions, calendars, contacts, calls, and documents. The main trade-off is less server-level freedom. SSH access, custom server components, and some integrations may be restricted, so check any essential requirements before migrating.

When should you move to managed Nextcloud?

Self-hosting may work well when you have the time and technical knowledge to maintain it properly. Moving to managed Nextcloud may make sense when:

• Security updates and software patches are regularly postponed.
• Backups exist, but nobody has tested whether they can be restored.
• Server problems depend on one technically skilled person.
• Performance issues and failed background jobs keep returning.
• Maintenance takes time away from clients, projects, research, or team management.
• Predictable costs and German data residency have become more important.
• You want to keep Nextcloud without managing the underlying infrastructure.

Self-hosting can still be a good fit if you are comfortable maintaining the server and need complete control over every part of the setup. But if you no longer need root access or advanced customisation, managed hosting lets you keep using Nextcloud without carrying all the technical work yourself.

Ways to Migrate from Self-Hosted to Managed Nextcloud

Buying managed Nextcloud gives you a maintained cloud environment, but it does not always include moving your existing data. Some providers handle the migration for you, while others give you a new account and leave the transfer in your hands.

The right method depends on what your provider supports. A full migration may be possible if they accept your database, files, and configuration. If not, you can move your data with the User Migration app, the desktop client, or separate exports. Let’s look at how each method works and what it can bring across.

Whichever method you choose, create a current, restorable backup and keep the old instance unchanged until the managed cloud has been fully checked.

Full-Instance Migration with Help from Your Provider

This method is designed to move your complete Nextcloud setup, not just your files. Instead of transferring files one by one, the migration brings the database, data directory, configuration, and supported app information into the managed environment. This method suits individuals, professionals, teams, and businesses that want to preserve more than their current files.

How does it work?

• The provider reviews your existing setup. You share details such as the Nextcloud version, database type, storage volume, installed apps, encryption status, domain, and external integrations.
• Both sides agree on the migration plan. The source administrator and provider decide who will create the backup, transfer the data, change the DNS records, and test the new environment. They also agree on a maintenance window and rollback plan.
• Nextcloud is taken offline for the final transfer. Maintenance mode is enabled first, and access to the source instance is then stopped so files and database records cannot change while the final copy is created.
• A complete migration copy is created. This normally includes the database, data directory, config.php, and any required custom apps or themes. File timestamps are preserved to reduce unnecessary resynchronisation afterward.
• The provider restores the instance. The database and files are imported into the managed environment. Server-specific settings, permissions, domains, caching, storage connections, and supported integrations are then configured.
• The new cloud is tested. Logins, files, permissions, shares, calendars, contacts, sync clients, and essential apps are checked before the domain is switched.
• Traffic moves to the managed instance. If you are keeping the same domain, its DNS records are updated to point to the new environment. Maintenance mode is disabled, and the provider monitors the instance for problems.

What might not transfer?

Unsupported apps, custom server components, external storage, LDAP, SSO, full-text search, and Office integrations may require separate configuration. Confirm these requirements before the migration begins.

What should you verify?

Check logins, files, permissions, sharing links, calendars, contacts, desktop sync, mobile access, and essential apps. Keep the original server available until the new cloud has been fully tested.

If you want help moving your self-hosted Nextcloud, contact CloudBased Backup at support@cloudbasedbackup.com. Our support team can review your setup, help identify the safest migration route, and guide you toward a managed plan that fits your storage and collaboration needs.

Migrate an Account With the Nextcloud User Migration App

The official Nextcloud User Migration app moves selected user data from one Nextcloud account to another. It can include files, settings, profile information, calendars, contacts, and data from apps that support Nextcloud’s migration framework. This method works well for an individual account or a small number of accounts. For a larger team, the process normally has to be repeated for each account unless the provider performs a server-level migration using the database and data directory.

How does it work?

• Check support on both Nextcloud instances. The User Migration app must be compatible with both versions of Nextcloud. Your managed provider must also permit the app to be installed and enabled.
• Install and enable the app on both instances. An administrator can find “User Migration” in the Nextcloud App Store and select Download and enable on the self-hosted instance. On the managed instance, the provider may need to install and enable it because managed plans can restrict app installation.
• Choose what you want to export. Open Personal settings, select Data migration, and choose the available files, settings, profile information, calendars, contacts, or supported app data. The available options depend on the installed apps and the migrators they provide.
• Create and download the migration archive. Start the export and wait for Nextcloud to process it. The resulting archive is named user.nextcloud_export. Large accounts may take longer to process and require enough free storage for the archive.
• Prepare the account on the managed instance. Create or obtain the destination account. The target instance must also have a compatible version of the User Migration app.
• Upload and import the archive. Upload user.nextcloud_export to the new account. Open Personal settings, choose Data migration, and start the import.
• Test the imported account. Check the files and supported data before repeating the process for any remaining accounts.

What might not transfer?

The User Migration app does not copy the complete Nextcloud server. Global configuration, Nextcloud user groups and group membership, server-wide app settings, LDAP or SSO, external storage, Redis, object storage, mail configuration, and custom server services require separate setup. Apps can transfer their data only when they support the User Migration framework. Do not assume that every share, public link, permission, file version, or app setting will survive the import.

What should you verify?

Compare important files and folders, calendars, contacts, profile settings, shares, permissions, and supported app data. Test desktop and mobile synchronisation with the managed account. Keep the original instance until the imported information has been checked.

Transfer files with the Nextcloud desktop client

The Nextcloud desktop client offers an easy way to copy files from your self-hosted account to a managed account. It works well for an individual, freelancer, or small team when a full-instance import and the User Migration app are unavailable. This method moves current files and folders, not the complete Nextcloud setup.

How does it work?

Finish synchronising the old account. Open the desktop client and wait until the source account shows that synchronisation is complete. Resolve any conflicts and make virtual files available offline before starting the final copy. Ask anyone with access to stop editing files during the final copy.

Add the managed account. The Nextcloud desktop client supports multiple accounts. Select Add New, enter the managed server address, sign in, and choose a separate local folder for the new account.

Copy the files locally. Copy the required files from the old account’s synchronised folder into the new account’s folder. Use copy instead of cut so the original local files remain available if something goes wrong.

Wait for the upload to finish. The desktop client will upload the copied files to the managed instance. Keep the computer connected and check the client for errors. The transfer time depends on the file volume, upload speed, and available storage.

Verify the managed account. Sign in through the web interface and check important folders, filenames, file counts, and a selection of documents. Confirm that the desktop client shows a completed synchronisation before removing the old connection.

What might not transfer?

This method does not normally recreate accounts, groups, permissions, shares, public links, file versions, deleted-file history, comments, tags, favourites, calendars, contacts, or app settings. Server configuration, LDAP, SSO, external storage, and encryption settings also remain outside the transfer.

What should you verify?

Open a sample of important files instead of checking only their names. Look for missing folders, zero-byte files, conflicts, duplicates, unsupported filenames, and failed uploads. Keep the old Nextcloud instance and its local folder until the new account has been fully checked.

Export and import data separately

This method moves each type of data on its own. Files are transferred using one method, calendars and contacts are exported in their supported formats, and app settings are handled separately. It works well for a small account or a selective migration when a full-instance import and the User Migration app are unavailable.

How does it work?

• Create the destination accounts. Set up the required accounts on the managed instance before importing anything. Groups, storage quotas, and basic permissions may need to be recreated manually.
• Transfer the files. Move current files with the Nextcloud desktop client, WebDAV, or a transfer arranged with the provider. This copies file content but does not recreate the original database metadata, sharing history, or file versions.
• Export and import each calendar. Export the required calendars from the self-hosted instance as .ics files. In the managed instance, open Calendar settings, select Import Calendar, upload the file, and choose the destination calendar. Nextcloud supports iCalendar-compatible .ics files for this process.
• Export and import your contacts. Export each address book from the old Contacts app as a .vcf file. Open Contacts on the managed instance, select Settings, choose Import, and upload the file.
• Review other apps individually. Check whether Notes, Tasks, Bookmarks, Deck, or other important apps provide a compatible export option. Data from an app without export and import support may need to be recreated manually or handled by the provider.
• Rebuild sharing and integrations. Recreate groups, internal shares, public links, external storage, LDAP or SSO, Office connections, and other required settings. Nextcloud Mail accounts may also need to be connected again on the managed instance.
• Verify each imported dataset. Open important files, compare calendar events and contacts, test sharing, and reconnect desktop and mobile devices. Keep the self-hosted instance until every required data type has been checked.

What might not transfer?

This method does not normally preserve account IDs, group memberships, file versions, deleted-file history, comments, tags, activity records, shares, public links, or complete app settings. Calendar events and contacts may transfer successfully while their original sharing permissions and app-specific settings do not.

Who should use this method?

Separate export and import is suitable when you need only selected data or have a small number of accounts. If the migration involves many accounts, important file history, complex sharing, or several business-critical apps, a provider-assisted full-instance migration is usually more complete.

How to minimise Nextcloud migration downtime

The easiest way to keep downtime short is to finish as much preparation as possible before taking the old instance offline.

• Test the managed environment, apps, storage, and integrations before the migration.
• Transfer an initial copy of large datasets in advance when the provider supports it.
• Resolve sync errors and unsupported app issues before taking the source offline.
• Schedule the final transfer during a quiet period and ask everyone to stop editing files.
• Prepare any DNS changes early and test the managed instance before reopening access.
• Keep the original server unchanged until the new environment has been verified.

File-only transfers may not require a full outage, but changes should still pause during the final copy. A complete instance migration normally requires the source to remain offline, so avoid any promise of zero downtime.

What CloudBased Backup manages after the migration

Once your migration is complete, you can leave the server work to us. CloudBased Backup manages the hosting infrastructure, maintenance, operating-system patches, Nextcloud security updates, and backups according to your plan and SLA. Your cloud stays in German data centres under GDPR-aligned data protection. GDPR compliance also depends on how you control access, retain data, and handle it within your own work or business.

You remain in control of what matters inside Nextcloud. You manage your accounts, groups, files, sharing permissions, apps, and working policies through the admin interface. You can also use your own domain and personalise the branding of your cloud portal.

If you want the benefits of Nextcloud without maintaining the server yourself, explore our managed Nextcloud plans.