Migrate an external workflow
Import an n8n workflow JSON, review mapped nodes, and test the rebuilt flow before switching over.
Start with a copy of the external workflow JSON and a small set of expected inputs and outputs. Record its triggers, conditions, connection requirements, and points where it sends, writes, or submits. Remove embedded tokens, private headers, and sensitive example values from the copy.
Import and review the mapping
- In Workflows → Start delivery → Import existing flow, open Local file. Choose or paste the n8n workflow JSON. A parsed import opens a review of the mapped definition.
- Under Understand JSON and Review, compare the source graph with the proposed steps, branches, inputs, and outputs. Review triggers, expressions, loops, and any imported write or publish effect in particular.
- In Connection binding, choose the concrete connection, resource, and grant for the intended project or role. Credential references are prompts to bind locally. Keep credentials in the connection setup.
- In Save, choose from the available actions for the reviewed source. A saved workflow draft opens in Flow Library for further review and activation. A Work Pack or exported package carries the definition and setup requirements.
| What the import shows | How to handle it |
|---|---|
| Mapped capability | Check the specific operation and the connection’s support for it. An importer can recognize a service without having a runnable route for your account. |
| Data transform | Compare its rule and result with a sample from the old flow. A transform that fell back to passthrough needs a replacement rule if the original changed data. |
| Browser projection or third-party step | Review the intended action. Configure a supported automation route or replace the step with a working capability. |
| Unsupported expression, static node, or blocked code | Rebuild the needed logic with supported inputs, branches, or data operations. Imported custom code stays blocked until separately reviewed and configured through an eligible controlled route. |
Prove the cutover path
Use a test project and test destinations. Activate the reviewed flow and start it manually with a known input. Compare the mapped output and both branches with the source. Put an approval before each external effect that needs human review and verify that the run pauses and the receipt or read-back matches the test destination.
Set up and validate any timer or incoming trigger separately before switching over. Choose a cutoff that avoids two active flows writing to the same target. If the external flow is from another tool or uses features the importer cannot map, build the affected portion on the canvas using node selection and apply the same checks.
See runs and safe retry and Work Packs.