Can you integrate HubSpot with Kommo?

Explore a HubSpot and Kommo integration with a Stacksync engineer. Stacksync support for Kommo is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can HubSpot and Kommo sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the HubSpot and Kommo initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a HubSpot Super Admin authorize Stacksync through the account connection flow. Identify the Kommo account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the HubSpot to Kommo sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map HubSpot fields to Kommo?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a HubSpot and Kommo integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the HubSpot and Kommo pilot start with?

Start by reviewing Company in HubSpot and Companies in Kommo. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

CRM · Two-way sync platform

HubSpot and Kommo integration

Plan how HubSpot and Kommo should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

HubSpot

Kommo

Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study

Migrated from MuleSoft

Case study

Migrated from Celigo

Migrated from Heroku Connect

Migrated from Matillion

Case study

Migrated from Fivetran

Case study

Migrated from Celigo

Proposed workflow

Company sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving HubSpot Company or Kommo Companies needs a defined result in the other system.

Start with HubSpot Company and Kommo Companies. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve parent organizations, business units, and currency references before dependent transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyUse two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between HubSpot and Kommo
HubSpot record	Kommo record	Record matching	Field ownership
CompanyDocumented record: SupportedRecord matching	CompaniesProposed record; confirm Stacksync object support.	Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.	Assign ownership separately for relationship details and finance-controlled billing details.
ContactDocumented record: SupportedRecord matching	ContactsProposed record; confirm Stacksync object support.	Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.	Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.
TicketDocumented record: SupportedBusiness process handoff	TasksProposed record; confirm Stacksync object support.	Retain separate ticket and task IDs with an explicit relationship; several tasks may resolve one ticket.	Choose which ticket conditions create a work item and which task outcomes may update the support case.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

HubSpot

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Contact Company Deal Line Item Product Ticket Quote Goal Owner Pipeline Stages Audit Subscriptions HubDB Forms Calls Communications Emails Meetings Notes Post Mail Tasks Marketing Emails Invoices Attachments Custom objects (all) Associations Users Services Listings Courses Appointments Commerce Payments Email Events Property History	✅ Supported. Confirm field permissions and sync direction.
Campaigns	🕘 Coming soon. Confirm field permissions and sync direction.
Feedback Submissions	❌ Not supported. Confirm field permissions and sync direction.

Read the HubSpot connector guide

Kommo

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Leads Contacts Companies Pipelines & Statuses Tasks Notes	Confirm support for this record type and the direction you need.

Discuss Kommo requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	HubSpot	Kommo
Integration interface	REST API (CRM v3)	REST API
Authentication	OAuth	Confirm the credentials, API plan, and permissions required for Kommo.
Change detection	Record updates and association changes need separate validation.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Available for supported records	Confirm with Stacksync
Write access	Available for supported records	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

HubSpot

Integration interface: REST API (CRM v3)
Authentication: OAuth (choose HubSpot account and authorize Stacksync); requires a HubSpot 'Super Admin' to grant access; optional "Grant access to sensitive fields" checkbox for sensitive/highly sensitive fields
Change detection: Record updates and association changes need separate validation. Association detection uses full scans unless Associations CDC Boost is configured for an eligible account.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Have a HubSpot Super Admin authorize Stacksync through the account connection flow.
Include association tables when relationships between records are needed. Configure Associations CDC Boost separately when eligible.

Limitations to check

Custom objects require an eligible HubSpot plan. Custom id properties that collide with native record IDs are excluded from sync.
Associations CDC Boost requires setup and is unavailable on Free and Starter accounts; association timing can differ from ordinary records.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

HubSpot setup guide

Kommo

Integration interface: REST API
Authentication: Confirm the credentials, API plan, and permissions required for Kommo.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Kommo account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Kommo, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Kommo and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare HubSpot and Kommo access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

HubSpot setup checklist

Have a HubSpot Super Admin authorize Stacksync through the account connection flow.
Include association tables when relationships between records are needed. Configure Associations CDC Boost separately when eligible.

Setup guides: Authorize HubSpot

Kommo setup checklist

Identify the Kommo account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Kommo, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the HubSpot and Kommo planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Record matching

Company / Companies

Compare whether HubSpot Company and Kommo Companies describe the same company in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

HubSpot: Documented record · ✅ Supported
Kommo: Object support to establish
Record identity: Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
Field ownership: Assign ownership separately for relationship details and finance-controlled billing details.

Fields to include

Source record ID
Legal or display name
Business-unit reference
Lifecycle status

Record dependencies: Resolve parent organizations, business units, and currency references before dependent transactions.
Validation: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Recovery: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

References: HubSpot: Company documentation

Record matching

Contact / Contacts

Compare whether HubSpot Contact and Kommo Contacts describe the same contact in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

HubSpot: Documented record · ✅ Supported
Kommo: Object support to establish
Record identity: Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
Field ownership: Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.

Fields to include

Source person ID
Display name
Email address
Organization reference
Consent state

Record dependencies: Resolve the organization relationship and any owner or consent references required by the destination.
Validation: Test an email change, two records sharing an email, and a person associated with multiple organizations.
Recovery: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

References: HubSpot: Contact documentation

Business process

Ticket / Tasks

Support-to-work-item handoff: HubSpot Ticket provides context for Kommo Tasks. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

HubSpot: Documented record · ✅ Supported
Kommo: Object support to establish
Record identity: Retain separate ticket and task IDs with an explicit relationship; several tasks may resolve one ticket.
Field ownership: Choose which ticket conditions create a work item and which task outcomes may update the support case.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record dependencies: Resolve requester, organization, team, and status references before ticket updates.
Validation: Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.
Recovery: Check whether a reply or notification was already sent before replaying ticket actions.

References: HubSpot: Ticket documentation

Record matching

Users / Users

Compare whether HubSpot Users and Kommo Users describe the same application user or identity in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

HubSpot: Documented record · ✅ Supported
Kommo: Object support to establish
Record identity: Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.
Field ownership: Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes.

Fields to include

Source user ID
Tenant reference
Account status
Group references

Record dependencies: Resolve tenant and group references and establish a protected administrative-account policy.
Validation: Test a renamed login, disabled account, missing group, and a user existing in two tenants.
Recovery: Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.

References: HubSpot: Users documentation

Record matching

Tasks / Tasks

Compare whether HubSpot Tasks and Kommo Tasks describe the same task or work item in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

HubSpot: Documented record · ✅ Supported
Kommo: Object support to establish
Record identity: Use a stable task/work-item ID and preserve its project or parent-ticket reference.
Field ownership: Choose the owner of task status and assignment; destination workflow states may require an explicit transition.

Fields to include

Source task ID
Parent reference
Assignee
Status
Due date

Record dependencies: Resolve project, user, and parent-item references before the task.
Validation: Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones.
Recovery: Reconcile the destination state before retrying a transition to avoid reopening completed work.

References: HubSpot: Tasks documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Company / Companies to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your HubSpot and Kommo record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Company / Companies, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Ticket / Tasks handoff.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit: Consider for a one-time HubSpot / Kommo migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Company sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Company or Companies record needs a defined result in the other system.

Start with HubSpot Company and Kommo Companies. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve parent organizations, business units, and currency references before dependent transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

Contact sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Contact or Contacts record needs a defined result in the other system.

Start with HubSpot Contact and Kommo Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the organization relationship and any owner or consent references required by the destination.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an email change, two records sharing an email, and a person associated with multiple organizations.

If it fails: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Support case or ticket process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Ticket or Tasks record needs a defined result in the other system.

Start with HubSpot Ticket and Kommo Tasks. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve requester, organization, team, and status references before ticket updates.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.

If it fails: Check whether a reply or notification was already sent before replaying ticket actions.

Plan the customer lifecycle across HubSpot and Kommo

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A customer-facing change in HubSpot needs operational context in Kommo.

Select the relevant Contact or Company records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
Choose a representative reopened deal, changed contact identity, or reassigned account to test the handoff before expanding.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated company change

Investigate

Inspect HubSpot Company and Kommo Companies, their IDs, and the destination error.

Next action

Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

Rejected or repeated contact change

Investigate

Inspect HubSpot Contact and Kommo Contacts, their IDs, and the destination error.

Next action

Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Rejected or repeated support case or ticket change

Investigate

Inspect HubSpot Ticket and Kommo Tasks, their IDs, and the destination error.

Next action

Check whether a reply or notification was already sent before replaying ticket actions.

A record type or update is unavailable

Investigate

Check the HubSpot and Kommo connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between HubSpot and Kommo

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

HubSpot Kommo Direction requires confirmation

Detect changesRecord updates and association changes need separate validation. Association detection uses full scans unless Associations CDC Boost is configured for an eligible account.

Apply updatesConfirm that Stacksync can create or update the records you need in Kommo.

Kommo HubSpot Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in HubSpot.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Associations CDC Boost requires setup and is unavailable on Free and Starter accounts; association timing can differ from ordinary records.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ