Make to HubSpot
Visual integration and workflow automation platform. Scenarios of modules connect apps, including HubSpot CRM, and run on schedules, webhooks or API calls.
Make data can move into HubSpot, landing mainly in Data Hub. 0 of 5 mapped objects move directly; 4 items need manual work and 3 do not move. Plan roughly 1-2 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Make
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
1-10 scenarios
Simple trigger-action syncs.
Mid migration
10-50 scenarios
Routers, data stores and multiple apps.
Large migration
50+ scenarios
Enterprise orchestration; many stays in Make.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Make: what you need to get in, what lands in HubSpot, and what will not.
REST API (v2)
A Make API token with the required scopes. A HubSpot connection is also needed if the old scenarios are to be inspected or run.
A HubSpot Super Admin must pre-approve the Make app and approve any new scopes before reauthorization.
Make API limits are set by plan: Core 60/min, Pro 120/min, Teams 240/min, Enterprise 1000/min. Exceeding them returns a 429.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Make.
- You need: A Make API token with the required scopes. A HubSpot connection is also needed if the old scenarios are to be inspected or run.
- Permission: A HubSpot Super Admin must pre-approve the Make app and approve any new scopes before reauthorization.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Export blueprint JSON per scenario from the Scenario Builder (three dots > Export blueprint)
- Get scenario blueprint via API
- List scenarios via API
Limits: Make API limits are set by plan: Core 60/min, Pro 120/min, Teams 240/min, Enterprise 1000/min. Exceeding them returns a 429.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Make
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Scenarios (modules, mapped values, filters, routers) | Custom objects | manual | Blueprint JSON is a specification to read and rebuild as HubSpot workflows. It does not import into HubSpot and does not create custom objects. Rows below show the rebuild target. |
| Field maps between apps and HubSpot | Contacts | manual | Mapped values in blueprints are used as the spec for HubSpot properties, import mappings and workflow actions. |
| Routing and sync rules (routers, filters) | Deals | manual | Rebuild as HubSpot workflows, lead or deal routing, and ticket automation where supported. |
| Data stores | Custom objects | manual | Can be exported through the API and loaded as HubSpot custom objects or properties if the data is CRM-relevant. |
| Connections and webhooks | Files | no | Credentials are not portable. Connections must be recreated after a blueprint import. |
What to expect
Users must create connections again after importing a blueprint.
Not part of blueprint export; no evidence found of a bulk export to HubSpot.
Out of scope for HubSpot workflows; keep these in Make.
Blueprints are exported per scenario, or retrieved via the API.
Blueprints are Make-specific JSON that HubSpot cannot ingest.
A Super Admin must approve scopes.
Partial replacement motion.
Disable the Make scenario at cutover and use a feature flag or property.
Review every blueprint and run test cases.
Line up the Super Admin before the cutover.
Throttle calls and back off on 429.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Make API, blueprint export and HubSpot app connection are backed by Make docs. Object mapping, governance and cost rest on category-level analyst knowledge. Make is not a record store, so there is no data migration in the usual sense; the work is rebuilding automations.
Sources
Related migrations
Frequently asked questions
How do I migrate Make to HubSpot?
1. List all scenarios through the Make API and tag each as CRM or non-CRM. 2. Export each blueprint JSON and store it with a date. 3. Document HubSpot modules, triggers and the fields each one maps. 4. Check your plan's API limit via GET /organizations/{id} (apiLimit).
What does not move from Make to HubSpot?
Connection credentials and OAuth tokens, Execution history and logs and Non-CRM workflows, complex ETL and enterprise orchestration. Plan to rebuild or retire these.
How long does a Make to HubSpot migration take?
Small (1-10 scenarios): 1-2 weeks. Mid (10-50 scenarios): 3-8 weeks. Large (50+ scenarios): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Make?
A Make API token with the required scopes. A HubSpot connection is also needed if the old scenarios are to be inspected or run. A HubSpot Super Admin must pre-approve the Make app and approve any new scopes before reauthorization.
Is there a native HubSpot connector for Make?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Make data?
Check: Health, financial or minors' data may be passing through scenarios depending on the customer.. Agree consent, retention and access rules before exporting.
Moving Make into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner