Migrating from n8n Cloud to self-hosted

According to the official n8n documentation, migrating from n8n Cloud to a self-hosted n8n instance is not possible in an automated way: workflows can be exported as files and imported into the new environment, but credentials cannot be exported for security reasons and must be recreated completely from scratch in the target system. In addition, the webhook address changes when switching to your own domain, so every external connection that addresses n8n via webhook must be reconfigured. Anyone who plans for these two points from the start avoids the most common pitfalls during the switch. As of: July 2026.

Why do companies switch from n8n Cloud to self-hosted?

Companies switch mainly because of data sovereignty, cost control, and deeper integration into their own infrastructure. With n8n Cloud, workflow data and execution logs run on the provider's servers, whereas with self-hosting you determine yourself on which server and in which country the data is stored. Additional factors include fixed costs instead of usage-based costs and the ability to connect n8n directly to internal systems, VPNs, or your own databases, which is not possible to the same extent with the cloud variant.

How do you export your workflows from n8n Cloud?

The export takes place via the admin panel of your cloud instance: there you open the Manage section, select Export, and download the workflows as files. The official n8n guide on migrating from cloud to self-hosted explicitly states that there is no automated migration path and that the export-import process via the user interface is the intended way. Also check inactive workflows and drafts so that nothing is missing during the import.

Why do credentials have to be recreated completely?

Credentials generally cannot be exported from n8n Cloud because, for security reasons, they are bound to the encryption of the respective instance. After importing the workflow files, you therefore manually recreate every credential connection, for example to Google, Slack, Microsoft, or your own APIs, in the new instance, usually including a new OAuth authorization. The import itself is straightforward: you create a new workflow in the self-hosted instance, open the three-dot menu in the top right, select Import from file, and upload the previously downloaded file. Plan firmly for recreating the credentials, because without valid credentials the imported workflows cannot be executed.

Why do the webhook URLs change during the move?

The webhook address changes because n8n composes it from your own domain, or from the environment variables for protocol, host, and port, as soon as the instance no longer runs under the cloud subdomain but on your own server. If n8n runs behind a reverse proxy, the n8n documentation on webhook URL configuration additionally recommends setting the WEBHOOK_URL environment variable so that n8n displays the correct external address in the interface and registers it with external services. After the move, you must therefore manually switch every external connection, for example to payment providers, form tools, or other systems that previously pointed to the cloud webhook URL, to the new address.

What should you check before the move?

Before the actual switch, it is worth taking stock so that operations run stably after the move. This includes a complete list of all active workflows along with the external services that send webhooks to n8n, an overview of all required credentials, and a plan for backups and updates of the new infrastructure, because with self-hosted these tasks are no longer handled by the provider but by you yourself. Anyone who does not want to carry out this move alone, or who wants an existing n8n automation to be maintained cleanly and with a view to German data sovereignty, will find with the n8n consulting from NordFlux support for the move and ongoing operation.

Frequently asked questions about n8n Cloud to self-hosted

Can I export credentials from n8n Cloud?

No, according to the official n8n documentation, credentials cannot be exported from n8n Cloud for security reasons. After importing the workflows, they must be recreated manually in the self-hosted instance, including a new OAuth authorization for services such as Google or Microsoft.

How long does the migration from n8n Cloud to self-hosted take?

The official n8n documentation does not give a blanket time estimate. The effort depends mainly on the number of workflows and credentials, since every credential connection must be recreated individually and every webhook must be updated individually with the external services. Also plan additional time to test the restored workflows before you finally shut down the cloud instance.

Does the webhook URL change also apply to test webhooks?

Yes, n8n distinguishes between a test URL, which is used when running an inactive workflow, and a production URL, which is only registered when a workflow is activated. After the move to self-hosted, the base address changes for both URL types, which means that test webhooks you use during development must also be set up again.

Do I have to take care of backups and updates myself with self-hosting?

Yes, unlike with n8n Cloud, with self-hosted you take care of server operation, backups, and updates yourself. The n8n documentation describes various installation methods for this, such as npm, Docker, or deployments with cloud providers, but does not provide managed operation like the cloud version. Therefore, clarify before the move who will take care of monitoring, backups, and regular updates of the instance.