Kommo to HubSpot
Messenger-centric sales CRM (formerly amoCRM) with leads, contacts, companies, pipelines, tasks, notes and a Salesbot automation builder.
Kommo data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (Contacts, Companies and Leads (deals)); 5 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for Kommo
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
<10k records, 1 pipeline
CSV export and import is feasible.
Mid migration
10k-100k records, 2-4 pipelines
API extraction plus workflow rebuild.
Large migration
>100k records, many pipelines and chat history
Custom ETL, activity audit and role redesign.
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 Kommo: what you need to get in, what lands in HubSpot, and what will not.
REST API v4 (JSON over HTTPS, per-account subdomain)
Account subdomain plus a long-lived token, or an OAuth integration (client ID and secret).
API results follow the user's rights. UI export needs export permission, which admins can restrict.
About 7 requests per second per IP, returning 429 when exceeded. Repeated violations can lead to a 403 block. List calls return at most 250 entities, and writes are capped at 250 per request (50 recommended). API access closes 30 days after a subscription ends.
Choose your route
How will you move the data?
No native connector was found.
- You need: Account subdomain plus a long-lived token, or an OAuth integration (client ID and secret).
- Permission: API results follow the user's rights. UI export needs export permission, which admins can restrict.
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.
- UI export of leads to Excel/CSV/Google Sheets, split at 500 records per file
- Contacts and companies export to Excel/CSV/Google Sheets/vCard
- Tasks export to iCal/Outlook/Google Calendar
- REST API v4 extraction of leads, contacts, companies, tasks, notes, users and entity links
Limits: About 7 requests per second per IP, returning 429 when exceeded. Repeated violations can lead to a 403 block. List calls return at most 250 entities, and writes are capped at 250 per request (50 recommended). API access closes 30 days after a subscription ends.
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: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In Kommo
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | Move by CSV export or API. Custom fields are available via the API custom-fields endpoint. |
| Companies | Companies | yes | Linked contacts and leads can be retrieved with the 'with' parameter, which gives the association keys. |
| Leads (deals) | Deals | yes | Export includes responsible user, stage, value, tags, custom fields, notes and timestamps. Pipeline and status IDs are also available via the API. |
| Tasks | Tasks | partial | Tasks are in the lead export and the task export. API retrieval is supported. |
| Notes | Notes | partial | Notes are in the lead export. Notes are also an API endpoint. |
| Users (responsible users) | Contacts | manual | Map responsible_user_id to HubSpot owners. Users must be created in HubSpot first. |
| Pipelines and stages | Deals | manual | Rebuild the pipelines and stages in HubSpot, then map the IDs. |
| Calls and chat messages | Calls | partial | Calls and notes are available via the API. Messenger conversation history coverage is unverified. |
What to expect
Automation logic is not covered by the data export. Rebuild it as HubSpot workflows.
Not part of the export. Rebuild them in HubSpot.
Kommo robots and Salesbots have no import path.
Kommo rights differ from HubSpot's permission model.
No report export. Reconcile metrics against HubSpot.
The CSV export carries only the main contact and company names, so use the API for full coverage.
Chat history and attachments are not clearly covered by the UI export.
Finish extraction before the plan lapses.
Use the API with pagination and the updated_at filters, and reconcile counts.
Throttle requests, use If-Modified-Since, and avoid repeated full scans.
Extract the notes and tasks endpoints and compare them against the UI export.
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.
Export paths and API access are backed by Kommo docs. HubSpot-side import mechanics, the object mapping, and the governance, residency and certification details rest on category-level knowledge. No HubSpot-native Kommo connector was found.
Sources
Related migrations
Frequently asked questions
How do I migrate Kommo to HubSpot?
1. Inventory pipelines, stages, custom fields, tags and users, using the API custom-fields and users endpoints. 2. Confirm the export permission, or create an admin API long-lived token. 3. Count leads, contacts and companies, and note the volume per pipeline. 4. Document robots, Salesbots and triggers to rebuild as HubSpot workflows.
What data can move from Kommo to HubSpot?
These objects move directly: Contacts, Companies and Leads (deals). Check the mapping table for partial and manual items.
What does not move from Kommo to HubSpot?
Salesbot and automation (robots/triggers) and Permission roles and reports/analytics. Plan to rebuild or retire these.
How long does a Kommo to HubSpot migration take?
Small (<10k records, 1 pipeline): 1-2 weeks. Mid (10k-100k records, 2-4 pipelines): 3-6 weeks. Large (>100k records, many pipelines and chat history): 6-12 weeks. These are planning estimates, not a quote.
What access do I need to export from Kommo?
Account subdomain plus a long-lived token, or an OAuth integration (client ID and secret). API results follow the user's rights. UI export needs export permission, which admins can restrict.
What compliance issues apply when moving Kommo data?
Check: Chat and call content may hold sensitive or financial data and Possible minors' data depending on the business. Agree consent, retention and access rules before exporting.
Moving Kommo 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