Migrating from n8n Cloud to Self-Hosted (AWS/Google Cloud) – Best Practices?

Questions
1

Hi everyone! :wave:

I’m currently working with a client who wants to start using n8n Cloud (paid plan) but is planning to move everything to a self-hosted instance later on (most likely on AWS or Google Cloud).

Before we dive in, I want to make sure this migration is feasible and smooth.

• Is there a native way to migrate all workflows, credentials, executions, etc. from n8n Cloud to a self-hosted version?

• Or is it just a matter of manually exporting/importing workflows as JSON ?

• Are there any known limitations or caveats I should be aware of (especially around credentials or data)?

• Any tools, plugins, or recommended practices for this kind of move?

Would really appreciate any guidance from folks who’ve done this before or know the process well. Thanks a lot in advance! :pray:

2

I think migration itself it’s not a critical task: export workflows and credentials (with decrypted option) via cli. Import two files via cli to self hosted instance.

If you didn’t have particular custom needs, building a deploy/maintenance plan with docker looks easy. I wouldn’t expose the n8n instance to internet.

2 Likes
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.