HubSpot CRM Migrations and Integrations
A CRM migration is judged on one question after it completes: can the business still answer what it could answer the week before. Record counts matching is necessary and proves very little, because the counts can match while every association that made the records useful has been lost.
Two shapes of engagement sit in this category and they are not the same problem. A migration ends with one system. A coexistence keeps both, permanently, and needs a conflict policy rather than a cutover plan.
Deciding which one is being attempted, in writing, before any export runs, is the step most often skipped.
15 systems in this category, 3 of them documented in a published case study.
What survives a migration, and what quietly does not
Records move easily. What breaks is everything that gave them meaning: associations between objects, historical activity, the stage a deal was in when it was lost, custom fields whose type has no equivalent on the other side, and automation that fired against values that no longer exist.
A fidelity check is the only defence, and it has to be agreed before the move rather than constructed afterwards to explain a discrepancy. It asks a small number of questions of both systems and requires the same answer from each.
A rollback position matters more than a rehearsal. A migration that cannot be reversed is a decision taken under time pressure with no way back, and the window in which reversal stays possible is shorter than most plans assume.
The checks that have to return the same answer on both systems
Where two CRMs coexist, which system owns which record and which field
Systems in this category
Coexistence or migration, with a system of record agreed per field before anything moves.
Migration with a rehearsal, a reconciliation and a documented rollback position.
Built to a regulatory constraint where the packaged connector could not meet it.
Pipeline and activity history carried across without flattening the stage model.
Google-native records mapped onto HubSpot's object model.
Custom modules resolved to objects rather than dropped into notes.
Campaign and contact history preserved through the move.
Projects and opportunities separated on arrival rather than merged.
Call and sequence history retained against the contact.
Board columns mapped to properties with types decided rather than inferred.
Relational records reconciled against HubSpot associations.
Relationship and coverage data joined to the commercial pipeline.
Forecast submissions read against the pipeline that produced them.
Conversation signals attached to the deal, with retention agreed first.
Call analysis surfaced on the record rather than in a second tab.
Documented engagements
Each of these is a published study of one build, with the object model, the decisions taken and what the approach does not establish.
Common Questions
Frequently Asked Questions
The export is days. The decisions are weeks. Time is spent on the object model, on which historical activity is worth carrying, and on reconciling identity between systems that each minted their own identifiers. A migration quoted on record volume alone has been quoted on the cheapest part of it.
Yes, and it is a legitimate architecture rather than a failure to decide, provided ownership is settled per field. It is also permanently more expensive than one system, because every schema change has to be made twice and reconciled once.
Association history, field-level audit trails, attachments over a size limit, and the meaning of any custom field whose options were free text. None of that appears in a record count, which is why record counts are a poor acceptance test.
Selectively. Activity attached to open relationships almost always earns its place. Activity attached to records closed years ago is volume that slows every subsequent operation and is consulted rarely, and it can be archived outside the CRM and referenced.
Further reading
Long-form already published on the argument this category turns on.
- The CRM Data Migration MethodThe fidelity checks a migration is accepted against, agreed before anything moves.
- What CRM Modernisation Failure CostsWhere these programmes fail, and what the failure is actually priced at.
- Salesforce and HubSpot in Revenue OperationsThe comparison made on architecture rather than on feature lists.
Related categories
A system in this category that is not listed
The directory shows range rather than limits. A scoped build is quoted from the object model on each side and the fields that have to cross between them.