I’m currently working with a client who is currently using n8n Cloud but wants to move everything to a self-hosted instance He talked about someone recommending Repocloud’s 1-click installer since it’s a lot cheaper.
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?
What do you think about the installer?
Would really appreciate any guidance from folks who’ve done this before or know the process well. Thanks a lot in advance! I need this ASAP
hi guys , I am also in the process of evaluating n8n , and am trying the same thing for myself. I have a working n8n workflow on n8n.io, and I have exported the json file. I am expecting that I could simply import this json file into my self hosted n8n - but this clearly is not working. Please anyone point me to a guide on how to migrate workflows from n8n cloud to n8n self hosted, as I am having trouble finding any clear information.
You can pass a folder with all the workflow files. Only thing you need afterwards is to create all credentials and map them in every node of every workflow.
hi, thanks for suggestion - it gives me a starting point. From n8n dashboard > manage , there is also an export feature which exports as a zip file. Do I need ot use the zip file or individual jsons ? Is there any youtube video or something I can follow, because I would expect this is a very likely scenario i.e. to be able to import existing workflows into self hosted n8n ?
You need to provide the json files, so first need to unpack the zip.
It’s up to you how you get the files onto the server (eg. scp), after that use „docker cp“ to copy the files into the container (eg. /tmp). After that you can run the import.
It’s basically just regular linux and docker stuff. I don’t think there will be a video about this particular process.
first path is on host, second path is for n8n docker instance.
Hope that helps. I would copy the tar over, and then tar it out, and use the commands
here commands btw
Workflows#
Import workflows from a specific file:
n8n import:workflow --input=file.json
Import all the workflow files as JSON from the specified directory:
n8n import:workflow --separate --input=backups/latest/
Credentials#
Import credentials from a specific file:
n8n import:credentials --input=file.json
Import all the credentials files as JSON from the specified directory:
n8n import:credentials --separate --input=backups/latest/
thanks guys - david you given me some good info ! Its just a little bit off-putting when I see so many youtubers claiming n8n self hosting is easy with hostinger, railway etc . They should say - get familiar with docker, transferring files if you want to import, etc.
@manuu I get it, I’ve spent the last decade doing this technical support, but your right there a difference from saas where it’s a managed service enviroment, and moving over to self host indeed setups can be advanced, but also then issues can become troublesome too, I havn’t found reliable docs on backup restore (maybe export workflow and creds it it), except taking manual backups for the .n8n folder, and if using postgress the db also.
I actually did a restore for someone today who had issues, so id say yes you certainly need some sort of technical support / sys admins ideally, am thinking to actually offer this as a consulting service for technical support, may have to discuss with N8N properly terms and scope soon. But atm am just helping out in the community.
If they mean easy 1 click deploy yes maybe but when you’re faced with actual technical issues or crashed when developing your workflow, knowing how it all works helps. This is what i’ve dedicated the last month doing, it understanding how the system works so I can properly manage it, I’d hate to do alot of workflows and to lose my data.
hi guys, I have copied the workflow file to the vps, then also copied the workflow to the dokcer container. Imprt also seems succesful. Please let me know if you see anything I might have missed ( docker container is called root-n8n-1 ).
Its working guys - thanks so much. When I get time I will setup youtube channel to help others with same procedure. I am curious why after import the credentials need to be setup again ? Is it because the export does not export credentials ? Is this a security/safety aspect of exporting workflows - that the credentials are NOT exported ?
hi samuel, you mean to say there is an option available to import with all credentials ? Thsi would be handy, because now I got to go through each node - and if you have 50 nodes, this would be a hassle ! manu
hi, I am managed to get some nodes working in the imported workflow, however I now have another node which does not work at all - there seems to be a difference in behaviour for the n8n cloud and n8n self hosted which indicates a bug. Can anyone suggest how to notify potential bugs to the n8n guys ? manu
So, what issue are you seeing? Could you show which node please and the error, bugs can be report here in the forum, of it documented properly on the github issues page.