Move your workflows
wherever they need to go

The exported file contains the complete definition of the workflow as a self contained portable JSON document. Every step with its config and field mapping, every trigger with its conditions, every conditional branch, every variable reference, every connection identifier, every schedule, retry policy, timeout, and notification rule, so the workflow recreates exactly in any other workspace. Secrets and credentials are referenced by name rather than included, so the file is safe to commit.

Most teams treat their workspace as the source of truth and use the export to capture it in version control. The typical pattern is to schedule an automatic export of the whole workspace, commit any changes, and let the repository's history become the audit trail of every workflow change. For teams that prefer the repository as the source of truth, the reverse works too: make changes through pull requests that update the file, merge to main, and import the file into the live workspace.

The standard pattern is build in development, test in staging, run in production, and the same file moves through all three. Build the workflow in your development workspace. Export it. Import it into staging where the data resembles production and verify it works end to end. Once staging looks good, import the same file into production. The only differences are the connections and variables configured per workspace.

Bulk export handles workspaces of any practical size, from a handful of workflows to many hundreds. The export bundle comes out as an archive containing one file per workflow, with a manifest describing the contents of the archive and the version of the platform that produced it. Large workspaces export in the background with a progress indicator, so the team can kick off an export at the end of the day, leave it running, and find the bundle ready in the morning.

Export and import work at the workflow level: one at a time, or many in a bulk operation. A migration works at the environment level and moves entire setups (workflows, variables, connections, schedules, and config) together as one coordinated operation. Use export and import to move specific workflows between workspaces or back them up. Use migration to move a whole environment cleanly with everything that supports it. Migrations also support a rollback safety net that single imports do not.

Every migration captures the complete state of the target environment before applying any changes, so rollback returns it to exactly the state it was in before the migration started. Modified workflows return to their prior definitions. Configuration that changed returns to the prior values. Connections and schedules return to their prior states. The captured state is retained for a configurable window after the migration, so rollback stays available as long as the team needs to verify.