How to Migrate n8n Workflows to a New Instance (Without the Headache)

If you're moving to a new n8n host, leaving n8n Cloud, or upgrading to a bigger server, sooner or later you hit the same wall: how do you migrate your n8n workflows without rebuilding everything by hand? When you only have two or three workflows it's annoying. When you have 30, 50, or a few hundred, manual migration turns into a full day of tedious exporting and re-importing.

This guide covers everything you need to know about n8n migration — what actually transfers, the manual export/import method, the gotcha with credentials that trips everyone up, and the one-click way to move your whole library in minutes.

Why people migrate n8n workflows

There are a handful of common reasons to move n8n workflows to a new instance:

• Leaving n8n Cloud for self-hosted or managed hosting to cut costs and remove execution limits.
• Switching hosting providers for better performance, support, or pricing.
• Scaling up — moving from a small server to a larger dedicated instance as your automations grow.
• Consolidating several instances into one, or splitting one busy instance into several.

Whatever the reason, the goal is the same: get all your workflows running on the new instance with as little manual work as possible.

What can (and can't) be migrated in n8n

Before you start, it helps to know exactly what moves across:

• Workflows — fully migratable. Every node, connection and setting travels with the workflow.
• Tags — migratable, and best reused by name so you don't end up with duplicates.
• Folders — migratable on newer n8n versions that expose them.
• Credentials — not migratable. This is the big one, and we'll explain why below.

Why credentials don't transfer

n8n encrypts your credentials (API keys, OAuth tokens, passwords) and never exposes the secret values over its API — not even to you. The API can tell you a credential exists and what type it is, but it will never hand back the actual secret. That's a deliberate security boundary, and it's a good thing.

The practical upshot: no migration tool — ours or anyone else's — can copy your credential secrets. After you move your workflows, you re-enter those secrets once on the new instance. Any tool that claims to copy your secrets should make you nervous.

Method 1: Migrate n8n workflows manually (export & import)

The built-in way to move a workflow is to export it as JSON and import it on the other side:

1. Open a workflow on your old instance.
2. Use the menu to Download (export) the workflow as a JSON file.
3. On the new instance, choose Import from File and select that JSON.
4. Re-link the credentials on each node, then activate the workflow.
5. Repeat for every single workflow.

This works fine for a couple of workflows. The problem is it doesn't scale: there's no "export everything" button in the standard UI, so 50 workflows means 50 downloads and 50 imports — plus re-creating your tags and folders by hand. It's slow, error-prone, and easy to miss one.

Method 2: Bulk migration with the n8n API

n8n ships a public REST API that can list, read and create workflows programmatically. That means a script (or a tool) can pull every workflow from the source instance and recreate it on the target instance automatically — including remapping tags and folders along the way.

This is how proper bulk n8n migration works under the hood. A few things to get right:

• Import workflows inactive. If you activate a webhook or schedule trigger while the old instance is still live, it can fire twice. Bring everything over switched off, then turn it on once you've cut over.
• Strip credential bindings. Since secrets don't transfer, the migrated workflows reference credentials that don't exist yet on the new instance — you'll re-attach them.
• Reuse tags and folders by name so you don't create duplicates.
• Respect n8n's strict create schema. Newer n8n versions add workflow settings fields that the create endpoint rejects, so a good migration sanitizes those before importing.

You can build this yourself with the API, or use a tool that handles the edge cases for you.

The easy way: one-click n8n migration

On n8nautomation.cloud we built a workflow migration tool so you don't have to touch JSON files or write a script. Here's the whole process:

1. In your old n8n, create a short-lived API key (Settings → n8n API) — set a 1–2 hour expiry.
2. Create an API key on your new instance the same way.
3. Open the migration page, paste both keys, and pick your destination instance.
4. We scan your old instance and show you exactly what will move — workflows, tags and folders.
5. Hit start and watch a live progress bar as everything transfers.
6. Re-enter your credentials once (we show you the exact list), switch your workflows on, and you're done.

Your API keys are used once and never stored, and your workflows arrive inactive so nothing fires before you're ready. A library that used to take a day of manual work moves over in a couple of minutes.

Common n8n migration pitfalls

Duplicate workflows on a second run

If you run the same migration twice, you can end up with duplicate copies. Decide up front whether you want to skip workflows that already exist, rename them, or replace them — a good tool lets you choose.

Webhooks firing twice

This is why importing inactive matters. Keep the new workflows off until you've fully switched over, then activate them and disable the old instance.

Forgetting the credentials checklist

Because secrets don't migrate, a workflow can look "moved" but fail at runtime until you re-add its credentials. Keep a list of which credentials each workflow needs (our tool generates this for you automatically).

Frequently asked questions

Can I migrate all my n8n workflows at once?

Yes. The standard UI only exports one workflow at a time, but the n8n API — or a migration tool built on it — can move your entire library in a single pass.

Will migrating move my credentials too?

No. n8n never exposes credential secrets over its API, so credentials are re-entered once on the new instance. This is a security feature, not a limitation of the tool.

Is it safe to give a migration tool my n8n API key?

Use a key with a short expiry and revoke it once you're done. With our tool, the key is used a single time to read your workflows and is never stored.

Do my workflows keep running during migration?

Yes — your old instance keeps running. Workflows arrive on the new instance switched off so they don't double-fire, and you flip them on when you're ready to cut over.

Ready to migrate your n8n workflows?

If you're moving to managed n8n hosting, you can bring everything with you in minutes. Spin up a dedicated instance and use our one-click migration tool to transfer your workflows, tags and folders automatically — then re-enter your credentials once and you're live.