Migrate from Make.com to n8n
Move Make.com scenarios into n8n by first exporting scenario blueprint JSON from Make, then dropping those files into migromat. The converter reads modules, routers, filters, schedules, and field mappings so your team can review the generated n8n workflow before activation.
Source workflow
Upload or document your Make.com workflow so migromat can inspect the structure and dependencies.
AI-assisted mapping
Map triggers, actions, routers, filters, schedules, and fields into n8n concepts where possible.
Review and reconnect
Review the generated output, reconnect credentials in n8n, then test with representative data.
Translate visual scenarios into flexible n8n workflows
This route is useful when teams outgrow Make.com operations, need deeper control over workflow execution, or want n8n's self-hosting and developer-friendly ecosystem without manually recreating every scenario. The cleanest input is a Make scenario blueprint JSON file, which migromat can inspect and convert into n8n structure.
Prepare your Make.com workflow
- Use Make's scenario blueprint template to generate JSON files for the scenarios you want to migrate.
- Download the generated blueprint JSON files from Google Drive and upload them to migromat.
- Keep related JSON files together when scenarios share webhooks, data stores, or downstream operations.
- Flag any custom apps, advanced error handlers, or iterator-heavy flows before conversion.
Move into n8n
- Review the generated n8n workflow structure, mapped nodes, and conversion notes in migromat.
- Import the generated JSON into n8n Cloud or a self-hosted n8n instance.
- Reconnect credentials, test bundle-to-item behavior, and verify router logic before activation.
Make.com to n8n pricing
Start with a single scenario, or batch migration work when you are moving a larger Make.com account.
Workflow batch migration
per 50 scenarios
- Works for Make scenario blueprint JSON
- AI-assisted Make.com to n8n conversion
- Reviewable output with manual checks
- Generated n8n workflow output with credential reconnect steps
Account-scale migration
for larger Make.com batches
- Good for teams moving 50+ scenarios
- Bulk migration planning
- Router and iterator review notes
- Credential reconnect guidance
Make.com to n8n migration FAQ
Practical details to check before you import or rebuild the converted workflow.
How do I export Make.com scenario JSON for migromat?
Use Make's scenario blueprint template to list scenarios, fetch each scenario blueprint, and upload the JSON files to Google Drive. Then download those JSON files and upload them to migromat.
Can Make.com routers be converted to n8n?
migromat maps routers into n8n branching logic where possible. Complex routers should be reviewed because filter order and item handling can differ.
Will Make.com connections transfer automatically?
No. Connections and credentials need to be reconnected in n8n after conversion.
What should I test after importing into n8n?
Test schedules, webhooks, router filters, iterator behavior, aggregations, and any modules with app-specific field mappings.
Ready to move from Make.com to n8n?
Upload your source workflow, review the converted structure, and reconnect credentials in your target platform before activation.