Welcome

The Make Migration tool transfers your scenarios and their dependencies from one Make organization to another in a different Make zone. This process preserves your automation workflows while allowing you to reorganize your work across zones.

Prerequisites

To start the migration, you need an active account on both the source and target Make zones. The target organization must already exist and contain at least one team. Ensure you have appropriate permissions (admin or owner) in both organizations to complete the migration process.

Pre-migration checklist

Before migrating, verify that your scenarios are error-free. Scenarios with errors cannot be migrated and will be listed separately for review.

If your organization uses the Make API, the hardwired IDs will need to be updated after migration.

We recommend migrating all scenarios that use the same data stores together in a single migration session. Migrating them separately can lead to data inconsistency issues.

For detailed migration guidance, refer to our Upgrade to Enterprise guide.

When in doubt, reach out to our Care team.

IP-based restrictions

If your scenarios interact with applications that have IP-based restrictions, you may need to update allowlists after migration.

What gets migrated

The migration tool transfers the following entities:

• Scenarios
• Connections (OAuth and API key-based)
• Webhooks and mailhooks
• Data stores and data structures
• Folders
• Custom apps
• Team variables
• Organization variables

Your scenarios will maintain their structure, settings, and configurations in the target organization.

What does not get migrated

The following entities are currently not migrated:

• Custom Properties (Scenario)
• Authenticated Webhooks
• AI Agents
• Templates
• Incomplete Executions
• Webhook Queues
• Execution Logs
• Audit Logs
• Analytics