amoCRM to HubSpot
Messenger-first SMB CRM with pipelines, leads, contacts, companies, tasks, notes and Salesbot automation. It was rebranded Kommo in 2022 for markets outside Russia and the CIS.
amoCRM data can move into HubSpot, landing mainly in Sales Hub. 5 of 10 mapped objects move directly (Contacts, Companies, Leads (deals) and Tasks); 5 items need manual work and 3 do not move. Plan roughly 2-3 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for amoCRM
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 doneAfter
0 of 6 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
<10k records
One pipeline, few automations.
Mid migration
10k-100k records
Multiple pipelines, activity history and automation rebuild.
Large migration
>100k records
Heavy chat history, custom objects, permissions and reporting rebuild.
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 amoCRM: what you need to get in, what lands in HubSpot, and what will not.
REST API v4 (JSON). Kommo serves the same API on kommo.com, and the legacy v2 API existed earlier.
Subdomain plus an OAuth integration (client id/secret) or a long-lived token.
Per third-party docs: 7 requests/sec per integration and 50/sec per account. HTTP 429 on excess, and repeated flooding can trigger an IP block (403). Up to 50 leads per write request.
Choose your route
How will you move the data?
No native connector was found.
- You need: Subdomain plus an OAuth integration (client id/secret) or a long-lived token.
- Permission: To confirm
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.
- REST API v4 extraction of leads, contacts, companies, tasks, notes, pipelines, users and catalogs
- Webhooks for change events
- Third-party iPaaS connectors (Zapier, Make)
Limits: Per third-party docs: 7 requests/sec per integration and 50/sec per account. HTTP 429 on excess, and repeated flooding can trigger an IP block (403). Up to 50 leads per write request.
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-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In amoCRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | Available via API; custom fields need pre-created HubSpot properties. |
| Companies | Companies | yes | Available via API; contact-to-company links come from embedded relations. |
| Leads (deals) | Deals | yes | amoCRM 'leads' are deals; pipeline and status ids must map to HubSpot pipeline and stage ids. |
| Pipelines/statuses | Deals | partial | Readable via API but must be rebuilt as HubSpot pipelines and stages. |
| Users | Contacts | manual | Users are read via API; map them to HubSpot owners by email. Owners are not records and must be created as HubSpot users. |
| Tasks | Tasks | yes | Task API exists; linked entity type and id are needed for associations. |
| Notes | Notes | yes | Notes API exists; message and chat history coverage is unconfirmed. |
| Calls, emails, chat messages | Calls | partial | Coverage of the activity export is not confirmed in sources; audit before scoping. |
| Catalog elements (products) | Products | partial | Catalogs service exists in API clients; line-item links need verification. |
| Customers/Unsorted | Custom objects | manual | No direct HubSpot equivalent; decide on a custom object or an existing object. |
What to expect
Platform-specific logic must be rebuilt as HubSpot workflows.
Must be recreated in HubSpot permission sets and teams.
Saved reports are not portable; rebuild in HubSpot.
Status ids differ between platforms.
No portable format.
Different permission models.
Channel connections do not transfer.
Not confirmed in sources.
Test export on a sample; archive transcripts externally if needed.
Keep an id crosswalk and dedupe before import.
Throttle below 7 requests/sec and extract in batches.
Confirm the account domain and API base URL up front.
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.
Rebrand, API v4, OAuth and rate limits are supported only by Kommo's rebrand post and third-party sources. I did not open the vendor's current API reference or export help pages. Object mapping to HubSpot, export options and HubSpot connector details rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate amoCRM to HubSpot?
1. Confirm account domain (amocrm.ru, amocrm.com or kommo.com) and plan. 2. Create an OAuth integration or long-lived token with admin rights. 3. Inventory pipelines, statuses, custom fields, tags and users. 4. Create matching HubSpot properties, pipelines and stages.
What data can move from amoCRM to HubSpot?
These objects move directly: Contacts, Companies, Leads (deals), Tasks and Notes. Check the mapping table for partial and manual items.
What does not move from amoCRM to HubSpot?
Salesbot and automation rules, Role/permission configuration and Reports and dashboards. Plan to rebuild or retire these.
How long does a amoCRM to HubSpot migration take?
Small (<10k records): 2-3 weeks. Mid (10k-100k records): 4-8 weeks. Large (>100k records): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from amoCRM?
Subdomain plus an OAuth integration (client id/secret) or a long-lived token.
What compliance issues apply when moving amoCRM data?
Check: Messenger conversations may contain sensitive or financial data and GDPR applies to EU contacts. Agree consent, retention and access rules before exporting.
Moving amoCRM 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