Migrate your HubSpot data

HubSpot's foundational object. We migrate all standard and custom contact properties. We apply the marketing-contact billing flag at import time to prevent customers from being charged for contacts that should remain non-marketing records.

Companies are linked to contacts via associations. We preserve all company properties and the contact-to-company associations during import. HubSpot allows personalized object names (e.g., 'Account' instead of 'Company'), which we map from the source schema.

We migrate deal records with all associated properties, pipeline stages, and owner assignments. We validate that the target plan supports the pipeline count: Professional allows 15 pipelines, Enterprise allows 100, Starter allows 1.

Leads is a distinct object introduced in 2023 and only available on Sales Hub Enterprise. Where the destination CRM does not have a separate Lead object, we merge Leads into Contacts and preserve Lead_Status as a custom Contact property.

Activities are first-class objects in HubSpot but are not supported by HubSpot's native CSV importer. We migrate them via the CRM API in chronological batches, handling token-bucket rate limits (100-200 req/10sec burst, 4 req/sec on search endpoints) to preserve the activity timeline for each contact and deal.

Custom objects are Enterprise-only in HubSpot. We can migrate custom object records via the v2 custom objects API, but the custom object schema must already exist in the target HubSpot portal. We create the schema definition before migrating any records.

We migrate pipeline configurations including all stages, stage probabilities, and custom pipeline properties. The target plan tier limits apply: Starter is capped at 1 pipeline, Professional at 15, Enterprise at 100.

Products and line items are migrated as associated records linked to deals. We preserve the product catalog and all deal-product associations during import.

Tickets migrate with all custom ticket fields, conversations, and team assignments. We handle the ticket pipeline stages separately from the deal pipeline.

Owner records must exist in HubSpot before deals and contacts can be assigned to them. We migrate owner records first and resolve any missing owner references before importing associated records.

HubSpot supports tag-based categorization across objects. We migrate tags as flat string arrays and apply them to the corresponding records during import.

Sequences are Professional-gated and are not data objects in the traditional sense — they are templates. We migrate sequence templates as configuration, not as enrolled records. Active enrollments are not migratable across CRMs.