Migration Feature / Archive Package

Feature Requests
1

The idea is:

A archive format including not only the workflow but also additional assets inside n8n like data tables a if desired credentials.

My use case:

I had to migrate a workflow using data tables and a non default plugin from one n8n instance to another - it was quite a tinkering job.

I think it would be beneficial to add this because:

  • Problem 1: Workflows reference datatables not by their name but by their ID, so you need to do search&replace inside the JSON so switch the ID’s or manually configure each data table node again.
  • Problem 2: Data Tables contain basic rows which can not be inported to the new instance (_id, created, updated)
  • Similar tasks appear for settings up credentials and reinstalling external nodes.

A NAP (n8n-archive-package) would be cool - where all the assets can be transfered in a linked way.
So basicly some kind of zip in combination with a tilored import/export process.

If and how external nodes and credentials should be part of such a package file would of course be a topic to secuirty discussion.

2

Including workflows, data, and credentials in a single archive would clearly simplify migration and make projects more scalable. It would let you deploy full environments quickly without redoing the setup each time. The key is to ensure credential security throughout the process.

Summary
  • Simplified migration by bundling workflows, data, and credentials
  • Time saved by quickly deploying complete environments
  • Greater scalability in managing n8n projects
  • Crucial to ensure security when handling integrated credentials
1 Like
3

thats a very nice wrapping of the idea - thx

1 Like