Update legacy modules with new modules
This document provides instructions for updating legacy modules manually. To automate this process, please use the Module Migrator instead.
Important: Migration is not supported for all apps. You can view the full list of currently supported apps in the Module Migrator itself.
Most Make apps rely on external services, particularly their APIs (Application Programming Interfaces). As services evolve, so do their APIs. When services release a new API version, their Make app eventually becomes deprecated and shuts down. The result is a legacy (outdated) module in Make.
Make regularly implements new app versions that align with services' latest APIs. To keep your scenarios running, make sure to update legacy modules to the latest versions.
Here's a step-by-step guide to updating legacy modules in Make, using Google Drive as an example.
Step 1. Identify the legacy scenario
A green double arrow icon (below) indicates a legacy module:
Step 2. Clone the legacy scenario
Clone the scenario to make a copy. You will use this scenario from now on.
- In the scenario diagram, open the Options drop-down menu in the top-right corner.
- Select Clone.
- In Name of new scenario, name the copied scenario.
- To enable the scenario to pick up where its old version left off, select Yes in Keep the states of any modules the same as those being duplicated.
- Click Save.
We recommend opening the legacy scenario in a new tab to easily compare its configuration settings with those of the new scenario.
Step 3. Access and select new modules
- In your new (copied) scenario, choose the legacy module you need to upgrade and click on its green double arrow icon.
- Click Show me new modules and select the corresponding module. The new module will appear in the scenario builder, but remains unconnected.
In the new modules list, some modules may no longer be available. In this case, choose the next-best fit.
Step 4. Update the trigger module
- Move the clock icon from the legacy module to the new module.
- Unlink the legacy module and subsequent module, and link the new module with the desired module.
- Set the values of the new module. Keep in mind that some fields may be different.
Step 5. Update other modules
- Update the next legacy module, following the same process outlined in Step 3 (Access and Select New Modules).
- Connect the new module to (after) its legacy module.
- Set the values of the new module. If any items are missing in the mapping panel, see our Mapping documentation.
- Repeat this process for any remaining legacy modules.
Step 6. Clean up and finalize
- Remove all legacy modules from your new scenario with right-click and Delete module.
- Click Save to save your scenario.
You have now updated your legacy modules to their newest versions. This process ensures your scenarios continue to run properly as external services evolve their APIs.