Upgrading to Make
Make is not just a small update, but a whole new product with a completely changed underlying infrastructure. Integromat customers need to perform an upgrade of their user accounts, organizations, and data.
This article describes how to upgrade from the Integromat platform to Make.
Overview of the upgrade
To start using Make, you need to perform an upgrade procedure.
The upgrade to Make consists of several steps, most of which are automated.
Upgrade your user account and organization.
Migrate custom apps.
Prepare your scenarios for migration.
Migrate your scenarios and data.
Enter your payment information into Make.
Step 1 - Upgrade your user account and organization
You don't have to create a new account in Make. Instead, you upgrade your existing Integromat account and your organizations to Make.
When you do so, Make creates a copy of your user account and organizations. After this, you can start migrating your scenarios and data.
This step does not disable your Integromat account. You can still use your Integromat account until you complete all steps involved in the upgrade.
Note
Since you don't need to create a new account in Make, keep in mind that you need to use the same email address in Make which you already use in Integromat.
Learn more about upgrading your user accounts and organizations
Step 2 - Migrate custom apps
If you own custom apps on Integromat, we ask you to migrate them to Make as soon as possible. If you shared your custom apps with other users, they won't be able to migrate their scenarios containing the apps if you don't migrate them to Make first.
Step 3 - Prepare your scenarios for migration to Make
One of the major changes in Make is the introduction of parallel processing of webhooks. As a result, Make no longer allows triggering multiple scenarios with a single webhook. In Make, each webhook must trigger exactly one scenario.
If your scenarios share a single webhook, you will need to re-create the scenarios to ensure each scenario uses its own dedicated webhook.
Step 4 - Migrate your scenarios and data
After you have upgraded your accounts and organization to Make, you can start migrating your scenarios and associated data.
You don't need to migrate everything at once. The Migration tool allows you to choose what to migrate. You can always come back and continue migrating where you left off.
The Migration tool offers a fast migration option, which automatically migrates all selected scenarios. This is the most convenient option for the majority of our customers.
If you own complicated scenarios that we cannot migrate automatically, the Migration tool will inform you about this and provide options for manual migration.
We don't recommend using scenario blueprints to migrate your scenarios. Always use the migration tool.
Note that once you complete your migration of scenarios and data to Make, your Integromat account switches to read-only mode. You can still log in to Integromat to view the scenario execution history for your organization, but you won’t be able to activate or execute your scenarios in Integromat.
Step 5 - Enter your payment information into Make
Since Make uses a new payment services provider, we cannot transfer your payment details from Integromat.
At the end of the migration process, Make asks you to enter your payment information.
After you confirm your payment information, we stop charging the card that you entered in Integromat and start charging the one entered in Make.
Note that if you enter your payment information before you complete the migration, you have 60 days to finish the migration. The 60 days start counting the moment your new payment information is confirmed. After the 60 days, your Integromat license is removed, your scenarios deactivate, and your organizations become read-only.
Upgrade to Make in detail
Tip
For most customers, the upgrade process is fully automated. If your upgrade requires some manual steps, the upgrade tools inform you of this fact and guide you through the process step by step.
Tip
You don't need to perform the whole migration process at once. Both the Upgrade hub and the Migration tool can resume an upgrade you started earlier.
Important terms
Upgrade is the entire process of migrating your user accounts, organizations, and your data to Make.
Migration is the process of transferring your data (scenarios, connections, data stores, etc.) to Make. Migration is a part of the upgrade process.
Upgrading user accounts to Make
Make upgrades your Integromat account and organizations for you. You don't need to get new credentials for Make.
Go to make.com and click .
Enter the email address that you use for Integromat.
If you use this email address on Integromat, Make recognizes you as an existing customer.
The system shows a dialog, which allows you to upgrade your account automatically.
Accept the terms and conditions and click .
The system redirects you to the Integromat Sign in page.
Sign in with your Integromat credentials.
From this point on, until you upgrade all your organizations, the system shows the Upgrade hub every time you sign in. Follow the instructions in Using the Upgrade hub to complete your upgrade.
You can skip upgrading your user account and migrate data from an Integromat organization to an existing Make organization. This is useful if you have already created an account on Make and you don't want to take time copying your organization and users. Use the Migration tool to do this.
Go to migrate.make.com.
Follow the instructions in Migrating your data to Make.
Using the Upgrade hub
The Upgrade hub gives you an overview of all your Integromat organizations and their upgrade status. From here, you can copy your organizations and users to Make and migrate your data. You can also resume upgrading organizations that you started earlier.
Important
Make sure you have a Make account. Either upgrade your Integromat account or create a new one on Make.
Go to make.com/en/upgrade/hub and log in with your Make account.
The Upgrade hub shows all your organizations. You can upgrade organizations where you are an owner or an admin.
Choose an organization and click .
Make allows you to choose the location of the data center, which will store and process your data. In Select region, choose a location that is closest to you.
This is the location of the Amazon AWS data center where Make will store your data.
Click .
The Upgrade hub creates a copy of your organization in Make, including all associated users and settings.
All users who are part of the organization still need to upgrade their account to gain access to the upgraded organization. Until they do, you can revoke their access to the organization by going to Make > Organization > Users and removing them from the organization.
Make requires all users to be members of at least one team. The Upgrade Hub creates a team in your organization and assigns all users to the team.
Migrating your data to Make
Use the Migration tool if the Upgrade hub did not manage to migrate your data automatically.
You must be an owner or an admin of an organization to use the Migration tool. Launch the Migration tool for each of your organizations separately.
You can launch the Migration tool from the Upgrade hub.
Migration modes
The Migration tool provides two migration modes:
Fast migration migrates all of your data automatically. In some cases, the system may ask you to provide additional details or make a decision that can't be made automatically. Always follow the instructions on-screen.
Manual migration allows you to set up rules for migrating different types of data.
What data is migrated?
The Migration tool can migrate the following items. You can choose what to migrate and how in the Manual migration mode.
Scenarios and scenario folders
Connections (except those that reference a connected system and use an On-prem Agent)
Webhooks and mailhooks
Keys
Devices
Data stores, including their contents
Data structures
Custom apps
Some of the migrated items require you to perform manual steps before and after the migration. Read the following sections for more details.
What data is NOT migrated?
The migration tool does not migrate the following items.
Scenario execution histories
Incomplete scenario executions
User accounts
Use the Upgrade hub to transfer your user account from Integromat to Make.
Organizations
Use the Upgrade hub to transfer your organizations from Integromat to Make.
Webhook event queues and mailhook mail queues
Items that are not used in scenarios are not migrated
If any of the following items exist in your source instance but are not used in any of your scenarios, the Migration tool ignores them in all migration steps.
Connections
Data stores and data structures
Devices
Keys
Webhooks and mailhooks
To be able to migrate these items, use them in a scenario first.
Preparing for migration
Organizations
Use the Upgrade hub to copy your organization to Make or create a new organization.
Users
Use the Upgrade hub to copy your users to Make or create a new organization with new users and teams.
Teams
The fast migration mode migrates everything into one team. If you want to use more teams, prepare your teams in your target organization before the migration. Then, execute a manual migration for each team separately. Migrate scenarios and data that belong to one team in each execution of the Migration tool.
You can't move scenarios from one team to another after the migration is complete. If you decide to set up teams after your migration is complete, clone your scenarios one by one and choose the desired Target team in the Clone dialog.
Webhooks and mailhooks
Make requires a unique webhook or mailhook for each scenario.
We recommend you prepare new hooks on your target instance and use manual migration. The manual migration will allow you to replace hooks from the source instance with hooks on the target instance. If the Migration tool detects that more than one scenario is using a particular hook, you will not be able to continue the migration until you create replacement hooks on the target instance.
Alternatively, you can create a scenario, which starts with the original webhook and distributes the incoming data to multiple webhooks using a router and HTTP request modules.
Learn more about migrating webhooks
Data stores
The Migration tool may encounter problems If your scenarios update your data stores more often than every five minutes. If you update a data store on Integromat while the migration is running, the data on Make may be inconsistent with the data on Integromat at the end of the migration process.
We recommend that before you start the migration, you stop scenarios which write into a data store and:
Are triggered by a webhook
Run more often than every five minutes
After you finish the migration, enable those scenarios on Make manually.
Devices
The migration tool will create mock devices, which you will allow the migration to complete. However, you will need to create new devices in the target organization and then replace the mock devices with the new devices in your migrated scenarios.
Executing the migration
Don't worry if the migration fails
If the migration fails for any reason, you will not lose your work. If it encounters any errors, the Migration tool rolls back all changes made to both the source instance and the target instance.
Starting the migration
Use the Upgrade hub to start the migration. The Upgrade hub keeps track of the status of the migration of all your organizations. Click or next to an organization. Then, continue to select scenarios to migrate.
Alternatively, you can access the Migration tool directly:
Go to migrate.make.com.
Sign in to your Integromat instance and to your Make instance.
Select a source organization and a target organization. Note that the list shows only those organizations where you are an admin or an owner.
Select the team to which you want to assign your data.
The migration tool analyzes data in your source and target instances and shows what you already migrated and what you still need to migrate.
Select scenarios that you want to migrate.
Choose either (if available) or .
Migrating custom apps
If your scenarios use custom apps but you are not the owner of these apps, you will need to contact their owner and ask them to migrate the custom apps.
If you are the owner of some custom apps, the Migration tool detects them. You can see the list of your custom apps in step 3.1.
Warning
If you made your custom apps public via a link, you must migrate your custom apps before anyone migrates scenarios that use them. This doesn't apply to custom apps that are public and approved.
If you don't migrate your custom apps, their users will not be able to migrate their scenarios.
Important
Do not use VS Code to migrate your custom apps. Use the Migration tool instead.
Click next to each app. The Migration tool automatically installs an identical copy of the app on the target instance. All scenarios that use this app on the source will use the migrated copy on the target.
The editability of the custom app depends on its status. A custom app can be edited both on Integromat and Make if its status is private, published, or waiting for approval. However, we don't recommend editing apps in Integromat after migration because it can cause complications.
If the custom app is in the approved status, you cannot edit it in Integromat any longer. You can, however, manage all aspects of your custom apps on Make as you were used to.
Fast migration
Fast migration migrates all of your data with default migration settings.
You can't use fast migration if:
You have a webhook that triggers more than one scenario.
Your scenarios use custom apps whose owner has not migrated them to Make. This applies to private apps, custom apps available based on an invitation, and custom apps approved for public use.
Your scenarios use mobile devices.
Fast migration performs the following:
Migrates the selected scenarios, including all data associated with those scenarios.
Enables migrated scenarios on the target instance, but only those that were enabled on the source instance.
Note: Since scenarios with a set schedule always execute immediately after you enable them, your scheduled scenarios will execute immediately after you migrate them.
Disables migrated scenarios on the source instance.
Migrates data stores, including their contents.
Migrates webhooks and mailhooks. You will be able to use webhook URLs and mailhook addresses that you set up at the source instance. The system will forward traffic to the target instance automatically.
Items that are not used in scenarios are not migrated
If any of the following items exist in your source instance but are not used in any of your scenarios, the Migration tool ignores them in all migration steps.
Connections
Data stores and data structures
Devices
Keys
Webhooks and mailhooks
To be able to migrate these items, use them in a scenario first.
Follow the instructions on the screen to complete the migration.
Manual migration
Manual migration allows you to select which items to migrate and how to migrate them. Depending on the data detected on both the source instance and the target instance, the tool presents you with configuration options.
Follow the instructions on the screen to complete the migration.
The following sections describe the individual configuration options.
Scenarios
Here you can select, which scenarios you want to migrate. Your choice will influence subsequent settings, as the migration tool will only migrate items that are connected to the scenarios you choose to migrate.
Webhooks and mailhooks
Migration of webhooks and mailhooks depends on how you prepared the target instance. By default, you can choose to duplicate a webhook or mailhook with or without forwarding traffic.
If you choose to duplicate hooks without forwarding traffic, the scenarios that use this hook will change to use the duplicated webhook.
If you choose to duplicate hooks with forwarding traffic, the scenarios that use this hook will keep using the old hook. The migration tool will also create a new webhook URL or mailhook address. Since the legacy instance will be retired in the future, we recommend you begin using the new URL or address as soon as possible.
If you have created replacement hooks on the target instance, you can choose to replace the source hooks with the target hooks.
Devices
Make requires a unique device for each scenario with the same action set.
The migration tool creates mock devices on the target instance to ensure that scenarios using those devices do not contain errors.
The mock devices replace the Device setting in the Apple iOS and Android modules.
After the migration, you need to create your devices again, and then go through all your scenarios that use a device. In the device's module settings, replace the mock device with your newly created device.
Custom apps
Here you select how to map custom apps on the source to corresponding custom apps on the target.
Connections
The migration tool allows you to choose whether to create duplicate connections on the target instance or replace connections from the source instance with connections that you already created on the target instance.
It is not possible to duplicate a connection that references a connected system and uses an On-prem agent. You need to create such a connection on your target instance first. However, if you already have such a connection on your target instance, you can use it to replace connections from the source instance.
If you use the private instance, you need to re-authorize OAuth2 connections after the migration.
Data stores and data structures
The migration tool allows you to choose whether to create duplicate data stores with no records, to create duplicate data stores and migrate records from the source instance, or to replace data stores from the source instance with data stores that you already created on the target instance.
Tip
If you have an empty collection in your data structure, we recommend either:
to delete a collection before migrating a data structure.
to migrate a data structure to Make first, and use the
replace(input;{};null)function in the module that uses this data structure.
As a result, the module ignores an empty collection.
Folders
If you have scenarios on the source instance stored in folders, you can select whether to create folder duplicates or replace folders with those that you already created on the target instance.
Keys
The migration tool allows you to choose whether to create duplicate keys or to replace them with keys that you already created on the target instance.
If you choose to create duplicate keys, the keys will keep their settings but they will have different IDs.
Updating your license and billing information
All users with a paid Integromat subscription upgrading to Make receive the Integromat Legacy plan. You keep paying the same price as you were used to with Integromat. You keep the same amount of operations. The Integromat Legacy plan has the same features as the new Core plan in Make.
When you complete your upgrade to Make, the system asks you to update your payment method. When you update your payment method, we stop charging you in Integromat and start charging you on Make. Do not cancel your Integromat subscription during the migration process. The system will take care of the cancellation automatically once you enter your payment information into Make.
Note that if you enter your payment information before you complete the migration, you have 60 days to finish the migration. The 60 days start counting the moment your new payment information is confirmed. After 60 days, your Integromat license is removed, your scenarios deactivate, and your organizations become read-only.
Transferring your extra operations to Make
Extra operations which you purchased on Integromat can't be migrated. However, you will not lose the extra operations you bought.
After completing the upgrade to Make, you will receive an email with coupon codes that you can enter into Make to add your extra operations.
Coupons may have different values:
1,000
2,000
5,000
10,000
20,000
50,000
Make provides a flexible system of coupons distribution, so you can use them one by one as needed.
You have 620,700 extra operations. The maximum coupon value is 50,000. You will receive 12 coupons of 50,000 operations each, 2 coupons of 10,000 operations each, and 1 coupon of 1,000 operations.
You have 201,000 extra operations. The maximum coupon value is 10,000. You will receive 10 coupons of 10,000 operations each, and 1 coupon of 1,000 operations.
You have 9,370 extra operations. The maximum coupon value is 1,000. You will receive 10 coupons of 1,000 operations each.
Important
When you add extra operations using a coupon, these operations will be valid until your chosen billing period ends.
Changing Integromat IP addresses to Make IP addresses
Make runs on different servers than Integromat. That means we changed the IP addresses from which we connect to apps. If you integrate with third-party services, which restrict inbound connections, you must change the configuration of the services to white-list the new IP addresses.
Upgrade statuses explained
The following table explains different situations that you might find yourself in when performing an upgrade to Make. Use the table to determine which steps to take to successfully finish your upgrade.
Note: If you own multiple organizations, each organization needs to be upgraded separately. The only step common for all your organizations is the upgrade of your user account, which you do only once at the beginning of your upgrade journey.
Status | Description | Recommended next steps |
|---|---|---|
Not started | You do not have a Make account. All your scenarios run on Integromat. | Upgrade your user account to Make, then use the Upgrade hub to create a Make organization. |
Make account created | You have a Make user account. You created an empty organization in Make. | Use the Upgrade hub to start migrating your scenarios. |
Partially migrated with payment information still in Integromat | You have a Make user account and a Make organization. Some of your scenarios run on Integromat, and some scenarios run on Make. You have not entered payment information into Make yet. | Use the Upgrade hub to finish the migration. Then, enter your payment information into Make. |
Partially migrated with payment information entered in Make | Some of your scenarios run on Integromat, and some scenarios run on Make. You entered payment information for your organization into Make. | From the moment you confirmed your payment details on Make, a 60-day period starts, in which you need to finish migrating your scenarios. Use the Upgrade hub to finish the migration. After the 60-day period ends, your Integromat organization loses its license, and scenarios become read-only. Note: with your upgrade in this state, you cannot change your Integromat subscription plan anymore. You can change your Make subscription as you see fit. |
Fully migrated with payment information still in Integromat | The migration is considered as complete when you have migrated all scenarios that have been executed in the past 90 days. Your payment and billing information is still on Integromat. Your Integromat account is accessible but all data is in a read-only state and scenarios are deactivated. | Enter your payment information into Make. When you do so, we stop charging your Integromat account and start charging your Make account. Note: after you enter your payment information into Make, you won't be able to change your Integromat subscription plan anymore. You will be able to change your Make subscription as you see fit. |
Fully migrated with payment information in Make | The migration is considered as complete when you have migrated all scenarios that have been executed in the past 90 days. You're all set to use Make. Your Integromat account is accessible but all data is in a read-only state and scenarios are deactivated. | Enjoy Make :-) |