Downloading a workflow file is a starting point, not proof that your operation can continue elsewhere. The workflow also depends on connected accounts, triggers, run history and data held in source and destination systems. Before closing an account, establish what can be restored and what must be rebuilt.
The short answer
Inventory four layers: workflow design, connections, run history and business data. Export what the platform actually offers and identify what the file does not carry. Import a copy in a controlled environment only where the platform documents support; otherwise rebuild and validate the workflow. Leave only after the replacement has an owner, authentication, triggers, conditions and outcomes verified, with no unresolved work in the old account.
Make says a scenario blueprint includes modules, settings and mapped values, but account connections need to be created after import. Zapier’s account export includes a Zapfile.json with non-deleted Zaps and CSVs linking to downloadable history; the cited documentation does not present that bundle as a reimportable backup. Inputs and outputs may hold sensitive data, so restrict storage, access and retention. In Power Automate, a solution should include dependent components such as connection references and environment variables. Neither “JSON downloaded” nor “history saved” means the migration is complete.
Four-layer exit matrix
| Layer | What to locate | What an export may not solve | Evidence to advance |
|---|---|---|---|
| Workflow design | Steps, filters, branches, mappings, version | Unsupported import or incompatible logic on another platform | Import where supported; otherwise rebuild and compare step by step |
| Connections and secrets | Authorized account, scope, environment, owner | Credentials should not travel in a shareable file | Connection rebuilt with least privilege and authorized test |
| History and pending work | Runs, errors, queues, retries, IDs | A design export does not necessarily retain events | Pending items classified and audit trail retained as needed |
| Business data | Orders, contacts, files and records in source/destination | The workflow may move data without storing the source of truth | Authoritative system identified and sample reconciled |
This Pulse matrix lets you label each item exported, rebuilt, verified or still dependent. If a critical layer remains dependent, postpone shutdown or establish a safe manual bridge.
Inventory the whole dependency chain
For each automation record its purpose, owner, trigger, frequency, source and destination systems, integration IDs, transformed fields, error rules, connection, sensitive data handled, last legitimate run and next expected run. Do not paste passwords, tokens or API key values into the inventory. Find webhooks, addresses or schedules that must be redirected, plus workflows that call other workflows.
Separate “ran last week” from “has not run for months.” A monthly export may be active and critical despite being invisible in a short observation period. Cover its cycle or design a controlled, authorized check. Do not manufacture real orders, messages or payments to generate a dashboard event.
Restore before retiring the source
- Export through the platform’s documented route. Keep a restricted copy and record its version and date. Zapier’s
Zapfile.jsonmay contain sensitive inputs and outputs: inspect it, limit access and retention, and never share it as a public template. - Export history, reports and business data separately when needed and permitted. Record format, plan and retention limitations instead of assuming every platform offers the same package.
- Import into a controlled environment only when supported by documented instructions; otherwise rebuild in the destination. Reconnect authorized accounts and compare triggers, filters, branches, mappings and failure handling against the inventory.
- Use fictional data or an already authorized run to check the outcome, duplicate behavior and error record. Do not activate old and new workflows simultaneously for the same action without duplicate protection.
- Observe the first legitimate run and less frequent jobs. Keep evidence that the new route works and that no pending item or webhook still points to the old platform.
Do not shut down while a connection is missing, pending work has no owner, required history is not preserved, the source of truth is unknown or the trigger still targets the old service. If a subscription expires before validation, document the possible interruption and a manual fallback; do not claim the migration is complete.
Use the automation failure contingency plan to keep work moving during an interruption. If exit also involves credentials, see how to rotate an API key before revoking the old one. Exporting a workflow and rotating a key are separate decisions.
Sources and limits
Make’s blueprint guide supports the distinction between configuration and connections. Zapier’s account data export guide describes Zapfile.json and history links, but does not establish reimportability. Microsoft documents solution exports and their dependent components. The matrix and inventory are our editorial models, not a guarantee that one platform can import another’s file or a report of a real migration. Check your plan’s features, retention rules and operational obligations.