Moving workflows in or out: import and export
Your automation workspace can be exported in a single file and imported again later, either back into the same workspace or into a new one. This guide covers exporting everything you own, importing workflows and credentials, and moving your work across from another n8n installation you already run.
Note: Export and import are available to members on a paid Smart Marketing plan. You need at least one saved workflow or credential for an export to be useful.
Export your workspace
The export gives you one file containing every workflow and credential you own, written in n8n's own format.
On the Automations tab, find the Export card.
Click Export my workspace.
The file downloads to your computer. Save it somewhere you control.
You can run another export ten minutes after the last one.
Warning: The export file contains your saved logins and keys in readable form. Store it somewhere safe, never share it, and never upload it to other websites or file-conversion tools.
A good habit is to keep the file in the same place you keep other business passwords and account details — an encrypted folder, a password manager's secure notes, or an offline drive.
Import workflows and credentials
The Import card has two boxes side by side: Workflows and Credentials. Each one says Drop the JSON here or click to choose.
Drag a file onto the matching box, or click the box and pick the file from your computer.
Check that the file name shown on the box is the one you meant to use.
Click Import.
Each box accepts an n8n export file. Either box also accepts the single file produced by Export my workspace — it is split into workflows and credentials automatically, so you do not need to separate anything yourself.
Files can be up to 10 MB each. If a file is larger, export it in smaller parts and import them one after another.
Note: A backup of your workspace is taken automatically before any import. If the result is not what you expected, you can restore that backup.
Imported credentials are secured for your workspace, the same as credentials you create by hand.
Move from another n8n installation
If you already run n8n somewhere else — on your own machine or with another setup — you can bring everything across.
On that installation, create the workflow file by running:
n8n export:workflow --all --output=workflows.json
Create the credentials file by running:
n8n export:credentials --all --decrypted --output=credentials.json
If that n8n runs inside a container, run the same two commands inside the container.
Copy both files to the computer you use to open your 1smart.link workspace.
In your workspace, drop
workflows.jsononto the Workflows box andcredentials.jsononto the Credentials box.Click Import.
Warning: The
credentials.jsonfile is created in readable form so it can be imported. Treat it like a password file and delete it from your computer once the import has finished.
What does not move
Three things stay behind when you import. None of them stop your automations working once you have tidied them up.
Item | What happens | What to do |
|---|---|---|
Execution history | Past runs do not come across | Nothing — new runs are recorded from the moment you switch a workflow on |
Community nodes | Not installed automatically | Reinstall each one from n8n's settings in one click |
Webhook URLs | Change, because the address has changed | Copy the new URL and update it in the service that calls it |
Workflows that use a community node show a missing-node warning until you reinstall it. Once the node is back, open the workflow and the warning clears.
Webhooks matter most if you have a website form feeding a spreadsheet, or a shop sending new-order notifications. Those services are still pointing at the old address, so nothing will arrive until you paste in the new one.
After importing
Imported workflows arrive switched off. This is deliberate — it gives you a chance to check everything before anything runs.
Open each imported workflow one at a time.
Check that every node shows a credential selected, not a blank field.
For any workflow that starts with a webhook, copy the new URL and update the service that calls it.
Reinstall any community nodes the workflow needs.
Run the workflow once by hand to confirm it behaves as expected.
Switch the workflow on.
Work through them in order of importance. A daily summary email can wait; a new-order notification should be checked first.
Result
Once the import is finished and each workflow has been checked and switched on, your automations run exactly as they did before — same steps, same connected accounts, same schedules. The only differences are the new webhook addresses and a fresh execution history that starts from today's runs.
Troubleshooting
The file is rejected with a message about not being an n8n export
Only n8n's own export files are accepted. A spreadsheet, a plain text file, or a JSON file from another tool will be refused with a plain message such as That file is not an n8n export, and nothing in your workspace is changed. Re-export from the source using the commands above, or use the file from Export my workspace.
The file is refused for being too large
Files over 10 MB are not accepted. Export in smaller parts — for example, export a group of workflows at a time rather than all of them — and import each part separately.
A workflow shows a missing-node warning
The workflow uses a community node that is not installed yet. Open n8n's settings, reinstall the node in one click, then reopen the workflow.
A node shows no credential selected
The credentials file was not imported, or it was imported after the workflows. Import the credentials file, then reopen the workflow and pick the credential from the list.
Export my workspace does nothing
You can only export once every ten minutes. Wait, then click Export my workspace again.
n8n is a registered trademark of n8n GmbH. 1smart.link is an independent hosting provider and is not affiliated with or endorsed by n8n GmbH.
Related articles
Article #59
Article #60
Article #57