Hi everyone,
I’m new to n8n
I am currently looking into using n8n Cloud, but I might want to migrate to a self-hosted instance in the future.
Before I commit, I would like to know: if I decide to make this switch later on, is it possible to easily export all my workflows from the Cloud version and import them into a self-hosted setup?
Are there any limitations I should be aware of regarding exporting workflows, credentials, or execution data?
Thanks in advance for your help!
1 Like
Hi @driss_bunji Welcome!
You can easily export your workflows from cloud and settle them up in your Self hosted n8n, credentials are something you need to set manually.
And for self hosted n8n instance, i recommend reading this:
Thanks Anshul. By any chance do you know how much time or account remains active.
For example: I need to use n8n from now until July and do not need it until end of year.
Do you know whether I could pause my subscription and find my workflows intact when back on it?
Best
@driss_bunji ummm as other services like Netflix for example you cannot PAUSE your subscription right, same goes with n8n cloud, although your data is saved for 90 days after your plan gets expired.
Also i think if you are really gonna switch export all of your data from the cloud instance:
But in case like if the issue is huge, i would recommend reaching out to support team maybe they could give you a straight answer, but i do think so that you cannot actually PAUSE your subscription there.
Feel free to reachout here:
Also i would recommend using Self Hosted instance if you do not want to consistently use n8n.
welcome to the n8n community @driss_bunji
Just to add one practical detail: exporting the workflows is the easy part, but before leaving Cloud I’d also document credentials, env vars, webhook URLs, users/projects, and any instance-level settings you rely on. That usually makes the self-hosted migration much smoother, since the workflow JSON alone doesn’t fully recreate the whole setup.
1 Like