Migrate from Make to Heym
Move Make scenarios to Heym. Paste an exported blueprint, watch AI Convert rebuild every module on a live canvas, then run it on your own infrastructure.
Make presents a hosted visual automation platform where scenarios chain app modules together, with routers, filters, iterators, and aggregators shaping how data moves between them.
When it is worth moving a workflow
Operations bills by the run, which is fine until an agent loop makes the run count unpredictable. The other common trigger is data residency: once a scenario starts handling documents or customer records that cannot leave your network, a hosted execution model becomes the constraint rather than the convenience.
If you are still deciding rather than moving, the Heym and Make comparison covers the evaluation side with links to first-party documentation.
How the move works
- 1
Export from Make
Open the scenario in Make, use the scenario menu to export the blueprint as JSON, and copy the file contents.
- 2
Paste it into AI Convert
A safety check runs, then each construct is mapped to the closest native Heym node and streamed onto a live canvas while you watch.
- 3
Review, download, and import
Read the rebuilt workflow, download or copy it, import it into your own instance, and attach your credentials.
What each Make concept becomes
A reviewer's guide to the rebuilt workflow. Constructs without an exact equivalent are mapped to the closest Heym primitive, which is why the result is worth reading before it handles real traffic.
| In Make | In Heym | What changes |
|---|---|---|
| Scenario | Workflow | One scenario becomes one workflow on the canvas, with the same module order preserved as edges. |
| Module | Node | Each module becomes the closest native node, or an HTTP node when the service has no dedicated one. |
| Router | Switch node | Each route becomes a labelled outgoing edge, and independent routes run in parallel rather than in sequence. |
| Filter on a route | Condition node | A filter that gates a route becomes an explicit branch, so the decision is visible on the canvas rather than hidden on the connector. |
| Iterator | Loop node | Splitting an array into separate bundles becomes per-item iteration, with independent items free to run concurrently. |
| Aggregator | Merge node | Collecting bundles back into one structure happens at a Merge, which is also where parallel branches fan in. |
| Data store | DataTable node | Structured records move to a DataTable in your own database rather than to the platform vendor. |
| Custom webhook | Workflow webhook trigger | The entry point becomes a property of the workflow, so the URL is new and callers need updating. |
| Scheduling | Cron node | Interval and time-based scheduling carries over as a cron expression with a timezone. |
| Error handler routes | Error Handler node | A handler route becomes a real branch you wire, and the workflow-level error workflow catches anything without one. |
| Built-in functions in mappings | Expression DSL | Mapping functions become expressions that evaluate the same way in the editor preview and in a production run. |
| Connections | Credentials tab | App authorizations are recreated as encrypted credentials in your own instance; nothing transfers automatically. |
Check these before it goes live
- Recreate every connection in the Credentials tab. A blueprint carries module configuration, not authorizations.
- Check the routers. Routes that ran one after another in Make can run at the same time in Heym, which exposes any ordering assumption.
- Verify iterator and aggregator pairs. Bundle semantics differ from per-item iteration, so confirm the shape of the merged output.
- Update the webhook URL anywhere an external system calls into the scenario.
- Run one test execution and compare the output against a recent run on the source side.
Make migration FAQ
Can AI Convert read a Make blueprint?
Yes. Export the scenario as a blueprint JSON and paste it into AI Convert. Each module is mapped to the closest native Heym node and streamed onto a live canvas you can download and import.
What happens to bundles and the iterator or aggregator pattern?
Heym passes structured data between nodes rather than bundles, so an iterator becomes a Loop node and an aggregator becomes a Merge. The behavior is equivalent for most scenarios, but confirm the shape of the merged output before you rely on it.
Do my credentials come across?
No, and that is deliberate. Exported workflow files hold no API keys or secrets, so AI Convert rebuilds the structure only and you attach your own credentials in the Heym Credentials tab afterwards. Nothing copies a secret between two systems on your behalf.
Is the converted workflow ready to run?
Treat it as a reviewed starting point rather than a finished port. Open it on the canvas, attach credentials, run one test execution, and adjust any node that was mapped to the closest Heym primitive rather than an exact equivalent.
Can I run the result on my own infrastructure?
Yes. Heym is source-available under an MIT license with a Commons Clause and runs on your own servers with Docker or Kubernetes, so migrated workflows, their credentials, and their model calls stay inside your environment.
Moving from something else
AI Convert reads exports from 12 tools, and it also accepts a plain description of the automation when there is no file to export.