Resources · Make integration

Module Migrator Make integrationAutomate Module Migrator with Make.

Stuck with scenarios built on modules Make has since replaced? The Module Migrator Make integration gives you 2 modules, one search and one action, to spot those scenarios and move them to current versions. This guide shows who it suits and how to run a first migration safely.

Try the Module Migrator integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Module Migrator Make integration do for you?

Module Migrator is one of the built-in apps of Make. It helps you when an app changes and older modules in your scenarios fall behind: instead of rebuilding each scenario by hand, it moves deprecated modules to their latest versions. A scenario is the automation you build in Make, and a module is one brick of it.

Know what needs work before you touch anything. Search scenarios returns the scenarios you ask for, as bundles (one item passed from a module to the next). Start there to see the size of the job instead of opening scenarios one at a time.

Move a scenario to current modules. Migrate outdated modules recreates the scenario with up-to-date modules. The original stays in place, which gives you room to compare both before switching over.

Finish the tricky cases with guidance. Some complex setups cannot be moved automatically. In that case the module hands you specific guidelines, so you know exactly which part to adjust yourself.

Two limits to keep in mind. Migration does not cover every app, and the list of supported apps is shown inside Module Migrator. And a recreated scenario is not live yet: with a polling trigger you pick the first record to start from, activate the new scenario and turn off the old one; with an instant trigger you unlink the webhook from the original and select it in the copy.

If migrations keep piling up, the Make troubleshooting guide and the Make training help you read what broke. Weighing tools more broadly? See n8n vs Make.

Connect

How do you connect Module Migrator to Make?

  1. 01

    Add a Module Migrator module

    Open a scenario, click the +, search for Module Migrator and pick one of its two modules. Then click Create a connection. A connection is your account linked to Make once and reused by every module of the app.

  2. 02

    Name it and authorize Make

    Giving the connection a name is optional, yet a clear name makes it easy to find again later. Next, authorize Make on the page that opens, or paste the key you were given if the window asks for one.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now list what it is able to read through this connection, so you pick values from menus instead of typing them from memory.

First scenario

Your first scenario with Module Migrator

GoalWhen Search scenarios finds the scenarios you target, Make passes each one to Migrate outdated modules and recreates it with current modules.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first module is where your automation begins.

  2. 02

    Add Search scenarios

    Search for Module Migrator, pick Search scenarios and link your connection. Fill in the fields; Make offers the values it can read, so you rarely type anything by hand.

  3. 03

    Chain Migrate outdated modules

    Click the + on the right of the search module and add Migrate outdated modules. Map the scenario returned by the search into it, so every result gets its own migration.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubbles above each module to read the bundles they received, and look for any guidelines about parts left to fix by hand.

  5. 05

    Schedule it and switch it on

    For a one-off cleanup, Run once is enough. To let it run alone, set the clock on the first module (every 15 minutes by default) and switch it on. Then activate each copy and turn off its original.

Modules

What the Module Migrator modules do

Module Migrator gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Module Migrator1

Search scenarios

SearchIn the docs only

Gives you a list of scenarios to work on, one bundle per scenario found. A search can return zero, one or many results, so the next module runs once for each of them.

When to use it
at the start of a migration, to see which scenarios are concerned before changing a single one.
Watch out
each bundle passed on costs operations downstream (an operation is one module run on one bundle, what Make counts on your plan), so run it once and count the results before chaining the migration.
Module Migrator2

Migrate outdated modules

ActionIn the docs only

Saves you from rebuilding a scenario by hand: it recreates it with deprecated modules replaced by their latest versions, and the original keeps running while you review the copy.

When to use it
after an app ships breaking changes and your scenarios still rely on its older modules.
Watch out
not every app is supported, and complex setups may need manual work; the module then gives you guidelines. The copy is not live until you activate it and turn the original off.
Need help

Need help automating Module Migrator with Make?

A person reads every message.

FAQ

Module Migrator and Make: common questions

01Is the Module Migrator Make integration free?
Yes, Module Migrator is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations each month, so keep in mind that every scenario found by the search adds work for the migration module that follows it.
02What do you need to connect Module Migrator to Make?
The documentation lists no specific prerequisite for Module Migrator. You follow the usual Make steps: add one of its modules, click Create a connection, optionally give the connection a name, authorize Make on the page that opens or paste the key you received, then click Save. Once saved, the connection is reused by both modules, Search scenarios and Migrate outdated modules. If the window asks for something the documentation does not describe, the Make troubleshooting guide or the team can help you sort it out.
03Can Module Migrator start a scenario on its own?
No, Module Migrator has no trigger, only a search and an action. To start a scenario anyway, you have two options. Put a trigger from another app first and add Search scenarios after it. Or place Search scenarios as the first module and set its clock: a new scenario runs every 15 minutes by default, and the Free plan does not allow shorter than that. With the first option, the other app's trigger decides the rhythm, scheduled or instant; with the second, the scenario follows its clock.
04What if a module is missing or the migration fails?
It depends on the cause. Migration is not supported for every app, and the list of supported ones is shown inside Module Migrator, so check it first. When a configuration is too complex to move automatically, the module returns guidelines telling you which part to finish yourself. Module Migrator has no Make an API Call module, so there is no generic request to fall back on. For a scenario the tool cannot handle, the practical route is to rebuild the affected part with the current modules of the app concerned, or to ask the team for help.
05Should you pick Make or n8n for Module Migrator?
It depends on where your automations live. Module Migrator is a Make built-in app whose job is to update Make scenarios whose modules have become outdated, so it only makes sense if your workflows already run in Make. If you are still choosing a platform, compare the two on the apps you connect, how your team likes to build and what each plan includes, rather than on this utility alone. The n8n vs Make comparison linked above goes through those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations