Migration Checklist (Free Download)

How to use this checklist

Work through it once for your whole account (sections 1–3), then once per automation (sections 4–6). A downloadable spreadsheet version with one row per Zap is available below.

Free download: Migration tracker spreadsheet (one row per Zap: trigger, actions, tasks/month, owner, priority, status, cut-over date). [Download link to be added]

1. Before you start

• List every Zap/scenario with owner, status and monthly task/credit usage
• Turn off and archive unused automations
• Note every app and account each automation connects to
• Identify automations triggered by webhooks (their source apps will need new URLs)
• Agree a cut-over window with the team
• Decide the target: n8n Cloud, self-hosted n8n, or Make

2. Set up the new platform

• Create the account or deploy the server
• Set timezone (GENERIC_TIMEZONE for n8n)
• Back up the encryption key (self-hosted n8n)
• Create a shared folder/project structure and naming convention
• Create credentials for every app, using service accounts or bot users
• Confirm OAuth scopes match what the old tool used

3. Monitoring and safety

• Create an error alert workflow (Slack or email)
• Enable retries on API steps
• Set up backups or workflow exports
• Document who owns each workflow

4. Per automation: rebuild

• Trigger rebuilt and tested with sample data
• Filters and branching rebuilt
• Formatter/data transformations rebuilt and verified
• Delays and schedules match the original
• Code steps rewritten and tested
• Output compared with the old tool's history for the same input

5. Per automation: parallel run

• New workflow active, writing to test destinations
• Ran for at least 3–7 days or 20+ real events
• Results match, including edge cases (empty fields, special characters, duplicates)

6. Per automation: cut-over

• Switch new workflow to production destinations
• Turn off the old Zap/scenario at the same moment
• Update webhook URLs in source apps
• Watch the first 24 hours of executions
• Keep the old automation disabled (not deleted) for 2–4 weeks

7. After migration

• Cancel or downgrade the old plan at the end of the billing cycle
• Record before/after costs
• Review failed executions weekly for the first month
• Update internal documentation

Need help?

If you would rather not migrate yourself, we can audit your Zaps, estimate savings and handle the migration. [Link to service page]