Skip to content
Get a quote

Customer.io to HubSpot migration

Moving from Customer.io to HubSpot consolidates behavioral messaging data into a full CRM with native deal tracking, ticket management, and sales reporting. FlitStack AI maps every Customer.io profile attribute and event to HubSpot properties and engagement logs, preserving original create timestamps and segment membership so your HubSpot workflows start with complete contact history.

Short answer

FlitStack AI migrates contacts, companies, custom objects, engagement log + custom event properties and contact original_create_date__cs from Customer.io to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 24–72 hours for under 50,000 records.

By

Source Customer.io
DestinationHubSpot
ContactCompanyCustom ObjectEngagement log + custom event propertiesContact Original_Create_Date__c
Mapped field by field · sample run · one-click rollback

What moves from Customer.io to HubSpot?

Customer.io organizes data around people profiles, companies, and behavioral events — it functions as a customer engagement platform rather than a traditional CRM.

Read the full summary

HubSpot structures data as contacts, companies, deals, and tickets with a property-based field model that uses camelCase naming (lifecycle_stage, createdate, hs_object_id) and a marketing-contact billing flag that distinguishes engaged from non-marketing contacts. The migration carries all Customer.io people and company data into HubSpot contacts and companies, maps custom attributes to HubSpot custom properties, and transfers event history as engagement logs or custom event properties. Custom objects migrate 1:1 to HubSpot custom objects, but deal and ticket equivalents must be created as custom objects in HubSpot since Customer.io has no native deal or ticket model. Workflows, journeys, and campaign logic cannot migrate — FlitStack exports your workflow definitions as a rebuild reference for HubSpot's automation tools. The migration runs via HubSpot's native API and bulk import endpoints, with a delta-pickup window capturing any changes during cutover.

direct

Person (profile) → Contact

Customer.io people map directly to HubSpot contacts.

How it maps

Email serves as the primary identifier for both platforms. Custom traits on the profile become HubSpot custom properties — we create each property in HubSpot's schema before migration and preserve the original attribute values.

transformed

Person (segment membership) → Contact (list membership + custom property)

Customer.io segment membership is a dynamic filter result, not a static list.

How it maps

We capture segment membership at migration time and write each segment name as a HubSpot custom property (Segment_Membership__c) so you can rebuild equivalent segments in HubSpot using list membership or static lists.

direct

Company → Company

Customer.io companies map 1:1 to HubSpot companies.

How it maps

The company identifier (id or external_id from Customer.io) is stored as a custom property for traceability. HubSpot company properties like domain, industry, and employee count map from corresponding Customer.io company attributes. All standard HubSpot company properties receive data where Customer.io provides equivalent attributes.

direct

Person-to-Company association → Contact-Company association

Customer.io's person-to-company relationship (identifying which people belong to which company) migrates to HubSpot's contact-company association.

How it maps

HubSpot supports primary and secondary company associations — the primary company from Customer.io becomes the primary association in HubSpot. Multi-company memberships are preserved as secondary associations in HubSpot.

direct

Custom Object (type) → Custom Object (type)

Customer.io custom objects (Accounts, Employers, etc.) map 1:1 to HubSpot custom objects.

How it maps

We create the custom object type in HubSpot, map all custom attributes to HubSpot custom properties, and preserve object-to-object relationships using HubSpot's association labels. Each custom object requires schema configuration in HubSpot before migration data is loaded.

transformed

Event (track call) → Engagement log (email/call/meeting) + custom event properties

Customer.io events are arbitrary behavioral track calls with custom event names and properties.

How it maps

We categorize common event patterns (page_view → logged page view, purchase → deal activity) and map them to HubSpot engagement types where semantically equivalent. Less common events migrate as custom event properties on the contact record for reference and future HubSpot workflow triggers.

What moves11 objects
Customer.ioHubSpot
  • PersonContact1:1
  • PersonContacttransformed
  • CompanyCompany1:1
  • Person-to-Company associationContact-Company association1:1
  • Custom ObjectCustom Object1:1
  • EventEngagement logtransformed

+ 5 more in the mapping below

How Customer.io and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionCustomer.ioHubSpot
Core data modelPeople (profiles) + Companies + Events as first-class objects with track-call behavioral dataContacts + Companies + Deals + Tickets with property-based field schema and marketing-contact flag
Deal / pipeline trackingNo native deal or pipeline model — requires custom objectsNative Deals object with pipelines, stages, amounts, close dates, and contact roles
Contact lifecycle modelProfile-level attributes + segment membership — no lifecycle stage by defaultHubSpot lifecycle_stage property (subscriber, lead, MQL, SQL, customer, evangelist) with stage-transition history
Event / activity trackingEvent stream via track() calls — arbitrary event names and properties stored as time-seriesEngagement logs (emails, calls, meetings, notes) + custom event properties on contact/company records
Billing modelProfile-based pricing ($100/mo for 5k profiles, scales with stored people count including deleted within billing period)Per-user or per-seat pricing with marketing-contact distinction affecting HubSpot Marketing Hub billing
Custom object modelCustom object types with object_type_id, object_id, and arbitrary custom attributesHubSpot custom objects with object type configuration, custom properties, and association labels

Customer.io to HubSpot field mapping

The 27 most-used fields of 27 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
Customer.ioHubSpot
  1. emailPerson emailContact
  2. first_namePerson firstnameContact
  3. last_namePerson lastnameContact
  4. phonePerson phoneContact
  5. created_atPerson Original_Create_Date__cContact
Customer.io fieldHubSpot fieldMappingNote
Person.emailContact.emaildirect
Person.first_nameContact.firstnamedirect
Person.last_nameContact.lastnamedirect
Person.phoneContact.phonedirect
Person.created_atContact.Original_Create_Date__ccustom_field_requiredHubSpot CreatedDate is set at migration time; original timestamp preserved as custom datetime for reporting continuity.
Person.updated_atContact.Original_Update_Date__ccustom_field_requiredHubSpot LastModifiedDate is set at migration time; original update timestamp preserved as custom datetime.
Person.idContact.Source_System_ID__ccustom_field_requiredCustomer.io person ID stored as custom text field for traceability and delta-run de-duplication.
Person.cityContact.citydirect
Person.stateContact.statedirect
Person.countryContact.countrydirect
Person.postal_codeContact.zipdirect
Person.companyContact.associatedcompanyidtransformedCustomer.io stores company name as a string attribute; migrates as a lookup to the corresponding HubSpot Company record.
Person.job_titleContact.jobtitledirect
Person.browser_languageContact.languagedirect
Person.email_verifiedContact.hs_email_verification_statusdirect
Company.idCompany.Source_System_ID__ccustom_field_requiredCustomer.io company ID stored for traceability and association resolution.
Company.nameCompany.namedirect
Company.domainCompany.domaindirect
Company.created_atCompany.Original_Create_Date__ccustom_field_requiredOriginal company creation date preserved as custom datetime.
Company.updated_atCompany.Original_Update_Date__ccustom_field_requiredOriginal company update timestamp preserved as custom datetime.
Company.cityCompany.citydirect
Company.stateCompany.statedirect
Company.countryCompany.countrydirect
Company.postal_codeCompany.zipdirect
Company.employee_countCompany.numberofemployeesdirect
Event.name (event identifier)Contact (engagement log).hs_activity_event_typetransformedCustomer.io event names map to HubSpot engagement log types. Standard events (page_view, email_clicked) become engagement notes or tasks; custom events preserved as custom contact properties.
Event.created_at (event timestamp)Contact (engagement log).hs_timestampdirectEvent timestamp preserved as engagement timestamp for chronological activity tracking.

What to watch for in a Customer.io to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Workflow and journey logic has no migration path — must be rebuilt in HubSpot

Customer.io workflows and journeys encode trigger conditions, time delays, branching logic, and action steps that cannot be exported in a runnable format.

How we handle it

HubSpot's workflow engine uses different trigger types (form submissions, list membership, property changes, deal stage changes) that don't accept imported logic. We export your workflow definitions as a documented reference (trigger names, conditions, action sequence) so your HubSpot admin can rebuild them in HubSpot's workflow builder. This is a manual step that must be planned as part of the migration timeline.

high

Event history maps to engagement logs, not native HubSpot event objects

Customer.io's track() calls store arbitrary behavioral events (purchase, feature_used, page_viewed) as first-class event records.

How we handle it

HubSpot's native event model is limited to engagement logs (emails, calls, meetings, notes) tied to contacts and companies. We categorize common Customer.io events to their closest HubSpot engagement equivalents, but arbitrary custom events without a semantic HubSpot counterpart become custom contact properties rather than native event records. This affects how you build HubSpot workflows based on historical event data.

medium

Customer.io's profile-based billing doesn't map to HubSpot's contact model

Customer.io bills by profile count — including profiles deleted within the billing cycle if your integrations re-add them.

How we handle it

HubSpot's CRM-level pricing is per-user or per-seat (Sales Hub, Service Hub) or based on marketing contact count (Marketing Hub). There is no equivalent billing flag in HubSpot for the distinction Customer.io makes between engaged and non-engaged profiles. If you rely on Customer.io's profile count for billing reconciliation, you will need to establish new counting logic in HubSpot using marketing contact flags or list membership.

medium

Segment membership is a point-in-time snapshot, not a migratable list

Customer.io segments are dynamic filters that evaluate continuously — the segment result at migration time reflects current conditions.

How we handle it

HubSpot's equivalent is static list membership or enrollment in HubSpot workflows. We capture segment membership as a custom contact property at migration time so you can recreate those segments as HubSpot lists. However, the dynamic refresh behavior of Customer.io segments does not carry over — HubSpot lists require manual or workflow-based maintenance to keep current.

low

HubSpot's marketing contact flag has no Customer.io equivalent

HubSpot Marketing Hub bills based on the number of contacts designated as marketing contacts — contacts who receive marketing emails.

How we handle it

Customer.io has no equivalent distinction; all profiles in the workspace are treated uniformly for billing and engagement purposes. When migrating to HubSpot with Marketing Hub, you must decide which migrated contacts should be designated as marketing contacts based on their engagement history. We preserve the original Customer.io engagement status as a custom property to inform this decision and provide a baseline count of potentially billable marketing contacts.

How the migration runs

  1. Extract Customer.io data via API and bulk export

    FlitStack connects to Customer.io via API using your workspace credentials and exports all people (with all attributes), companies, and event data.

    What this step covers

    We run a preliminary scan to identify unique event names, custom object types, and attribute counts. The export runs in batches to handle large workspaces without rate-limit impact. All exports are stored in a staging environment with PII handling compliant with your data residency requirements.

  2. Map Customer.io schema to HubSpot objects and properties

    Based on the extraction results, we create the target HubSpot schema before migration.

    What this step covers

    This includes creating custom properties on contacts and companies for each Customer.io attribute that has no direct HubSpot equivalent, configuring custom object types, and setting up association labels for custom objects. We deliver a schema plan document for your HubSpot admin to review and approve before the migration run.

  3. Resolve person-to-company associations and owner resolution

    Customer.io people may reference companies by name or ID.

    What this step covers

    We resolve these references to HubSpot company IDs by matching on company name and domain. For owner resolution, we match Customer.io user identifiers (if present) to HubSpot user emails — unmatched owners are flagged for your team to assign to a fallback HubSpot owner before the migration commits. Association resolution ensures all contact-company relationships are established correctly in HubSpot upon migration.

  4. Run sample migration with field-level diff

    A representative slice (typically 100–500 records spanning people, companies, events, and custom objects) migrates to HubSpot first.

    What this step covers

    We generate a field-level diff between the source Customer.io data and the destination HubSpot records so you can verify attribute mapping, event categorization, and association resolution before the full run commits. You approve the sample results before we proceed to ensure mapping accuracy across all data types.

  5. Execute full migration with delta-pickup window

    The full migration runs against HubSpot's native API and bulk import endpoints.

    What this step covers

    A delta-pickup window (typically 24–48 hours after initial run completion) captures any new or modified records in Customer.io during the cutover period. Audit logs track every operation, and one-click rollback is available if reconciliation identifies data integrity issues. After delta-pickup, your HubSpot instance reflects Customer.io's final state at go-live.

Customer.io HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

24–72 hours for under 50,000 recordsTypical, smaller accounts
5–10 days for over 500,000 records or complex custom-object / event-property setupsLarge or heavily customised accounts

A quote scales with record count, custom attribute volume, and event property complexity. Customer.io setups with heavy event history (high event-per-profile ratios) fall in the upper range because each unique event type requires HubSpot custom property or engagement-log mapping. Custom object count and association depth also affect scope — HubSpot's custom object association model differs from Customer.io's object_type_id approach, requiring transformation work. Profile counts drive base cost; custom field counts drive mapping validation time. Additional factors include the number of distinct event names that need semantic mapping to HubSpot engagement types and the complexity of preserving original created_at timestamps across contacts and companies. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Customer.io to HubSpot →

Why teams move from Customer.io to HubSpot

  • Customer.io charges by profile count including deleted profiles re-added by integrations within the same billing cycle — teams with high churn or frequent re-engagement see unpredictable bills. HubSpot's per-user or marketing-contact model offers better cost predictability at scale for sales-driven organizations.
  • Customer.io has no native deal pipeline, deal tracking, or quote management — teams managing B2B sales processes must build deal equivalents as custom objects, losing native reporting and stage automation. HubSpot's deal and pipeline model provides this out of the box.
  • Customer.io's event-based model stores behavioral data as arbitrary track-call streams with no native contact-role concept — associating events to deal context requires custom engineering. HubSpot's engagement logging and contact-role model provides structured activity history tied to deals, enabling sales teams to view all related communications directly within the deal record.
  • Teams using Customer.io for both messaging and CRM-like features find the platform becomes technically complex at scale — steep learning curve and need for developer assistance to set up advanced workflows pushes teams toward HubSpot's more accessible automation builder. HubSpot's visual workflow editor reduces the technical barrier for marketing teams managing automation.
  • HubSpot's all-in-one ecosystem (CRM, marketing, sales, service hubs) reduces tool sprawl and integration maintenance compared to running Customer.io alongside a separate CRM. Unified reporting across marketing and sales data drives the consolidation decision. Single-vendor relationships also simplify contract negotiations and support escalations.

Questions, answered

Customer.io to HubSpot migration questions

How long does a Customer.io to HubSpot migration take?

Most Customer.io-to-HubSpot migrations complete in 24–72 hours of clock time for under 50,000 records. Large datasets exceeding 500,000 records or setups with extensive custom object schemas extend to 5–10 days. The longest planning step is configuring HubSpot's custom properties and custom object types to receive Customer.io's attribute and object definitions before migration data lands. Pre-migration preparation time varies based on schema complexity.

Will my Customer.io workflows and journeys migrate to HubSpot?

No. Customer.io workflows and journey logic cannot migrate — they encode trigger conditions and branching that don't export in a runnable form. HubSpot's automation tools (workflows, sequences, bots) must be rebuilt from scratch using HubSpot's native interface. FlitStack exports your workflow definitions as a documented reference with trigger names, conditions, and action sequences so your HubSpot admin has a complete rebuild blueprint to follow.

What happens to Customer.io segment membership in HubSpot?

Customer.io segments are dynamic filters that evaluate continuously. We capture segment membership as a custom contact property at migration time, so each HubSpot contact reflects which Customer.io segments they belonged to on migration day. Dynamic segment behavior cannot be replicated in HubSpot — you will need to rebuild segments as HubSpot lists or workflow enrollment criteria based on the preserved membership data.

Can I migrate Customer.io custom objects to HubSpot custom objects?

Yes. Customer.io custom objects (Accounts, Employers, Job Postings, etc.) map 1:1 to HubSpot custom objects. We create the custom object type in HubSpot, map all custom attributes to HubSpot custom properties, and transfer object-to-object relationships using HubSpot's association labels. The custom object type must be configured in HubSpot before migration data is loaded to ensure proper schema alignment.

How does Customer.io event history map to HubSpot?

Customer.io events (track() calls with custom event names and properties) are categorized and mapped to HubSpot engagement log types where semantically equivalent. Standard events like page views become logged engagement notes; purchase events map to deal activity where deal objects exist. Custom events without a HubSpot equivalent become custom properties on the contact record for reference and future HubSpot workflow triggers.

Does the migration affect my Customer.io account during cutover?

No. FlitStack AI uses scoped read access to Customer.io via API — your team continues working in Customer.io throughout the migration process without interruption. A delta-pickup window (24–48 hours) captures any new people, updated profiles, or new events created during the cutover period so HubSpot reflects Customer.io's final state at go-live. No data is modified or deleted in Customer.io during the migration.

Why did my Customer.io bill increase unexpectedly before migration, and how does that affect planning?

Customer.io bills by profile count including profiles deleted within the billing cycle if integrations re-add them. This billing behavior means profile counts can spike unexpectedly before migration, increasing costs on the source side. We recommend auditing your Customer.io profile count and integration re-add behavior before migration planning to establish baseline scope and avoid billing surprises in the final billing cycle before cutover.

How do we handle Customer.io people who have no email address?

HubSpot requires an email address to create a contact record. Customer.io people without emails are flagged before migration. Options include: (1) create placeholder emails using a known domain for internal tracking, (2) merge these records into existing contacts if a phone number or other identifier matches, or (3) exclude them from migration and retain as a CSV reference. We surface the count of email-less profiles in the migration planning phase so your team decides the handling approach.

Get a quote

Moving from Customer.io to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote