Skip to content
Get a quote

Iterable to HubSpot migration

Moving from Iterable to HubSpot puts your customer engagement data inside a full CRM with native contact management, deal pipelines, and sales automation. FlitStack AI maps Iterable user profiles and behavioral events to HubSpot contacts and timeline activities, preserving original create dates and event metadata so your HubSpot reporting reflects the full customer history from day one.

Short answer

FlitStack AI migrates contacts, companies, timeline activities, deal + line items and products from Iterable 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: 48–72 hours for under 50,000 contact records.

By

Source Iterable
DestinationHubSpot
ContactCompanyTimeline ActivityDeal + Line ItemProduct
Mapped field by field · sample run · one-click rollback

What moves from Iterable to HubSpot?

Iterable is a cross-channel customer engagement platform organized around user profiles, custom events, catalogs, and journeys.

Read the full summary

HubSpot is a CRM organized around contacts, companies, deals, and tickets with native pipeline management. The data models are fundamentally different — Iterable stores behavioral event streams and product catalog data, while HubSpot stores record-centric CRM objects. FlitStack AI migrates Iterable user profiles to HubSpot contacts with company associations, custom events to timeline activities, catalog entries to HubSpot products, and purchase events to deals with line items. HubSpot's lifecycle stage system (subscriber, lead, MQL, SQL, opportunity, customer) is applied to migrated contacts based on their most-recent Iterable event type and list membership. Journey logic and campaign workflows cannot migrate — they require manual rebuild in HubSpot using lists and workflows. We sequence the migration so foreign keys resolve correctly: companies first, then contacts with company associations, then deals referencing those contacts. A delta-pickup window captures in-flight changes during cutover.

direct

User Profile → Contact

Iterable user profiles migrate as HubSpot contacts.

How it maps

Email address becomes the primary identifier. First name, last name, phone, and address properties map directly. Profile-level custom fields become HubSpot contact properties. We preserve the original Iterable created_date and last_updated_date as custom datetime fields for reporting continuity.

transformed

User Profile → Company

Iterable user profiles often contain company name and domain.

How it maps

We extract these to create HubSpot company records first, then link each contact to its primary company via the company_id field. Multiple company associations per user collapse to one primary company link in HubSpot.

transformed

Custom Event → Timeline Activity (Contact)

Iterable custom events (arbitrary event names with JSON payloads) translate to HubSpot timeline events.

How it maps

Each unique event name becomes a timeline activity type. Event metadata from JSON payloads flattens into activity properties. Up to 10 custom event types per HubSpot portal requires aggregation of high-cardinality event names.

merged

Purchase Event → Deal + Line Item

Iterable purchase events carry order ID, total amount, and product items.

How it maps

We create a HubSpot deal per order with amount mapped from the purchase total, and line items for each product purchased. The contact who triggered the purchase links to the deal via Opportunity Contact Role. Purchase timestamp becomes deal create date.

direct

Catalog → Product

Iterable catalog entries (collections with SKU, name, description, price, metadata) map to HubSpot Product Library records.

How it maps

Product images and metadata become custom properties on the HubSpot product. Catalog variants map to separate HubSpot products or as product variants via custom fields.

direct

Static List → HubSpot List

Iterable static lists migrate as HubSpot static lists.

How it maps

List name and membership (contact email addresses) transfer directly. Static list create dates are preserved. These lists serve as enrollment bases for HubSpot workflows post-migration. If a list references contacts not yet migrated, FlitStack AI queues those contacts for the next batch and updates the list membership after load. You can view list statistics in the HubSpot list dashboard.

What moves12 objects
IterableHubSpot
  • User ProfileContact1:1
  • User ProfileCompanytransformed
  • Custom EventTimeline Activitytransformed
  • Purchase EventDealmerged
  • CatalogProduct1:1
  • Static ListHubSpot List1:1

+ 6 more in the mapping below

How Iterable 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.

DimensionIterableHubSpot
Primary data modelEvent-stream architecture: user profiles hold attributes, events are separate time-stamped recordsRecord-centric architecture: contacts, companies, deals are standalone objects with properties and associations
Product catalogIterable Catalog: collection-based product definitions with nested attributes and pricingHubSpot Product Library: flat product records with SKU, price, and optional custom properties
Behavioral trackingCustom Events API: arbitrary event names with JSON payload, unbounded per userTimeline events: typed activities (email_opened, form_submitted) with property fields, 10 custom event types per portal
Lead lifecycleIterable: list membership and event history determine segment; no explicit lifecycle stagesHubSpot: lifecycle_stage pick-list (subscriber through customer) on every contact record
Campaign executionIterable Journeys: multi-step branching workflows with wait conditions and message channelsHubSpot Workflows: enrollment-based automation with if/then branches, limited to in-app and email without native SMS/Push channel orchestration
Billing modelIterable: contract-based pricing per monthly active user and message volumeHubSpot CRM: per-seat pricing with separate marketing-contact billing for email campaigns
Data export methodIterable Data Sync or API: export of users, events, catalogs via project-scoped API endpoints with configurable destinationHubSpot: HubSpot API v3 or native import/export with CSV; Bulk API for large record sets

Iterable to HubSpot field mapping

The 30 most-used fields of 32 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
IterableHubSpot
  1. emailUser Profile emailContact
  2. firstNameUser Profile firstnameContact
  3. lastNameUser Profile lastnameContact
  4. phoneNumberUser Profile phoneContact
  5. companyUser Profile associatedcompanyidContact
Iterable fieldHubSpot fieldMappingNote
User Profile.emailContact.emaildirect
User Profile.firstNameContact.firstnamedirect
User Profile.lastNameContact.lastnamedirect
User Profile.phoneNumberContact.phonedirect
User Profile.companyContact.associatedcompanyidtransformedCompany name in Iterable becomes a HubSpot company record first, then linked via Contact's associated company association.
User Profile.createdAtContact.Original_Create_Date__ccustom_field_requiredHubSpot CreatedDate reflects migration time. Original Iterable creation date preserved in custom datetime field for reporting continuity.
User Profile.updatedAtContact.Original_Update_Date__ccustom_field_requiredOriginal Iterable last-modified date preserved as custom datetime field.
User Profile.userIdContact.Source_System_ID__ccustom_field_requiredIterable internal user ID stored for traceability and delta-run de-duplication.
User Profile.emailSubscriptionsContact.hs_email_optoutvalue_mappingIterable email subscription boolean maps to HubSpot's marketing email opt-out flag.
User Profile.smsSubscriptionsContact.SMS_Opt_In__ccustom_field_requiredSMS consent from Iterable preserved as a custom boolean. HubSpot SMS requires separate third-party integration.
User Profile.cityContact.citydirect
User Profile.stateContact.statedirect
User Profile.countryContact.countrydirect
User Profile.zipContact.zipdirect
User Profile.profileAttributes (custom)Contact.custom propertiescustom_field_requiredAny Iterable custom profile field becomes a HubSpot contact property. Field type preserved (text, number, date, boolean). Pick-list values require value mapping.
Custom Event.eventNameTimeline Activity.eventTypetransformedUnique Iterable event name becomes a HubSpot timeline activity type. High-cardinality event names aggregated into generic 'custom_event' type with event name stored as property.
Custom Event.createdAtTimeline Activity.timestampdirectEvent creation timestamp preserved as timeline activity timestamp.
Custom Event.data (JSON payload)Timeline Activity.propertiestransformedJSON payload flattened into timeline activity properties. Nested objects stored as JSON string in a custom property.
Purchase Event.orderIdDeal.dealnametransformedIterable order ID becomes HubSpot deal name in format 'Order-{orderId}'.
Purchase Event.totalDeal.amountdirectPurchase total amount mapped directly to deal amount.
Purchase Event.createdAtDeal.closedatedirectPurchase timestamp becomes deal close date.
Purchase Event.userIdDeal.contact_id (via Opportunity Contact Role)transformedContact resolved by email match and linked via Opportunity Contact Role.
Purchase Event.itemsLine Item.name, quantity, pricemergedEach item in Iterable purchase items array becomes a HubSpot line item linked to the deal. Product resolved by SKU match in HubSpot product library.
Catalog Entry.skuProduct.hs_skudirect
Catalog Entry.nameProduct.namedirect
Catalog Entry.descriptionProduct.descriptiondirect
Catalog Entry.priceProduct.pricedirect
Catalog Entry.metadata (custom attributes)Product.custom propertiescustom_field_requiredCustom catalog attributes become HubSpot product custom properties.
Static List.listNameHubSpot List.listNamedirect
Static List.createdAtHubSpot List.createdatedirect

What to watch for in a Iterable 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

Iterable custom events require aggregation before HubSpot timeline import

Iterable allows unlimited custom event names per project.

How we handle it

HubSpot portals are limited to 10 custom event types in the timeline. High-cardinality event streams (hundreds of unique event names) must be aggregated into HubSpot-compatible event types before import. We group events by naming prefix or behavior category and store the original event name as a property on the timeline activity. This preserves behavioral data while fitting within HubSpot's schema constraints. Teams with complex event taxonomies should validate event type mapping before migration.

medium

Iterable purchase events need catalog-product resolution before deal creation

Iterable purchase events reference catalog entries by ID.

How we handle it

HubSpot deals with line items require product records to exist first. We resolve each purchase item's catalog ID against HubSpot's Product Library during mapping. Unmatched catalog items either create HubSpot product records on-the-fly or exclude the line item with a flag for manual review. Teams with large catalogs should pre-create products in HubSpot using Iterable catalog exports before migration day. This ensures that each line item links to a valid product, preventing orphaned deal entries and maintaining accurate revenue reporting in HubSpot. You can also set product pricing and images during the pre-creation step.

medium

HubSpot lifecycle stage must be derived from Iterable behavioral data

Iterable has no native lifecycle stage field — leads and customers are distinguished by list membership and event history.

How we handle it

HubSpot requires lifecycle_stage on every contact for proper segmentation. We derive HubSpot lifecycle stage from Iterable behavioral signals: contacts with purchase events become 'customer', contacts with high-frequency engagement events become 'opportunity', and all others default to 'lead'. Teams should validate lifecycle assignment logic against HubSpot reporting requirements before go-live. If your Iterable data includes scoring models or engagement scores, we can translate those into custom numeric properties that influence stage assignment. Adjustments to the mapping can be made in the FlitStack console before the final run.

medium

Iterable journey and campaign logic cannot migrate to HubSpot workflows

Iterable journeys contain multi-step branching logic, time delays, channel routing, and A/B testing configurations.

How we handle it

HubSpot workflows support enrollment-based automation but lack native SMS and push channels without third-party integrations. We export journey definitions as a reference document for manual rebuild. SMS and push channels require connection to HubSpot-approved integrations (e.g., Twilio, Pushwoosh) post-migration. Teams relying heavily on Iterable journeys should plan 2–4 weeks for workflow rebuild. FlitStack AI also provides a mapping matrix that links each Iterable journey node to equivalent HubSpot workflow actions, helping your team plan the rebuild timeline. You can import this matrix into project management tools to track progress.

low

Iterable data export rate limits affect migration window sizing

Iterable API enforces rate limits on data export endpoints.

How we handle it

Large user profiles (millions of records) require chunked extraction with exponential backoff. We use Iterable's Data Sync feature where available for incremental exports, falling back to API-based extraction for custom field and event data. Export failures due to rate limit errors add time to the migration window. Teams with large datasets should coordinate export scheduling with Iterable's API usage policies. We monitor API response headers to detect throttling and automatically pause requests, resuming once limits reset. This approach minimizes retries and keeps the migration timeline predictable.

How the migration runs

  1. Extract Iterable data via API and Data Sync

    We connect to Iterable's API using project-scoped credentials and extract user profiles, custom events, catalog entries, purchase events, lists, and campaign metadata.

    What this step covers

    For large datasets, we use Iterable's Data Sync feature to stream incremental exports. All extraction runs against Iterable's read-only API — no data modification or message sending occurs during export. We capture original created_at and updated_at timestamps for every record.

  2. Map Iterable objects to HubSpot data model

    We transform Iterable data shapes to fit HubSpot's CRM model: user profiles become contacts with company associations, purchase events become deals with line items, catalog entries become HubSpot products, and custom events become timeline activities.

    What this step covers

    We apply lifecycle stage derivation logic based on behavioral signals. Custom event names with high cardinality aggregate into HubSpot-compatible event types with original event name preserved as a property.

  3. Create HubSpot products and custom properties

    Before contacts and deals load, we create HubSpot product records from Iterable catalog data.

    What this step covers

    Custom properties on contacts, deals, and products are created in HubSpot via API using the field names and types from Iterable's schema. Any value mappings (subscription flags, custom pick-lists) are applied during this phase. HubSpot's portal limits (10 custom event types, property count caps) are validated against the migration scope.

  4. Run sample migration with field-level diff

    A representative slice migrates first — typically 100–500 user profiles spanning multiple event types, a sample of purchase events, and catalog entries.

    What this step covers

    We generate a field-level diff between the source Iterable data and the destination HubSpot records so you can verify lifecycle stage assignment, company-contact associations, product-deal linkage, and timeline activity mapping before the full run commits. This diff includes counts of mapped and unmapped fields, highlighting any data loss or transformation issues.

  5. Execute full migration with delta-pickup window

    Full data migration runs against HubSpot API, loading contacts, companies, deals, line items, products, and timeline activities in the correct sequence (companies first, then contacts with associations, then deals referencing contacts).

    What this step covers

    A delta-pickup window (typically 24–48 hours) captures any records modified in Iterable during the cutover. Audit log captures every operation, and one-click rollback is available if reconciliation fails. The rollback uses snapshot copies created before the run, allowing you to revert to the pre-migration state instantly.

Iterable 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

48–72 hours for under 50,000 contact recordsTypical, smaller accounts
5–7 days for over 500,000 records or heavy catalog / custom event setupsLarge or heavily customised accounts

A quote scales with record count, custom event volume, catalog complexity, and HubSpot custom property requirements. Iterable setups with large behavioral event histories (millions of rows) fall in the upper range because we flatten event metadata into timeline activities with preserved timestamps. Catalog migrations requiring HubSpot product record creation add scope. Migrations exceeding 500,000 user profiles or 50+ custom event types require extended mapping validation and fall outside the standard range. Setup complexity, data hygiene, and any required custom property creation also influence final pricing. Additional phases such as data cleansing, duplicate resolution, and post-migration verification can be quoted separately. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Iterable to HubSpot →

Why teams move from Iterable to HubSpot

  • Iterable's contract-based pricing at $20,000+ annually becomes unpredictable as contact and message volumes grow. HubSpot CRM's per-seat model offers better cost visibility for sales teams managing a separate engagement layer. Customer feedback cites billing surprises when MAU thresholds shift mid-contract.
  • Iterable lacks native CRM capabilities — contact records, deal management, and pipeline tracking require external tools. Teams migrate to HubSpot to consolidate customer data under one platform with built-in sales automation and marketing-contact management. Reddit threads from r/CRM document teams seeking unified tools after outgrowing point solutions.
  • Iterable's steep learning curve and unclear documentation slow campaign implementation. G2 reviews cite missing features in conversion tracking and limited template flexibility. Teams moving to HubSpot report better onboarding and more intuitive workflow builders for sales-driven campaigns. This reduces time-to-value for marketing teams managing frequent campaign updates.
  • Iterable's event-stream model requires engineering resources for custom event tracking. HubSpot's native property model and automation triggers reduce reliance on developer support for day-to-day campaign adjustments. Customer feedback indicates this friction as a driver for platform consolidation. This shift empowers marketing teams to iterate quickly without waiting for development cycles.

Questions, answered

Iterable to HubSpot migration questions

How long does an Iterable to HubSpot migration take?

Most Iterable to HubSpot migrations complete in 48–72 hours for under 50,000 contact records. Larger setups with millions of event rows, large catalogs, or complex custom event aggregation extend to 5–7 days. The longest planning step is mapping custom event names to HubSpot's 10-event-type limit and validating lifecycle stage derivation logic before data loads. During the migration, a sample slice of records is validated first, and a delta-pickup window captures any changes made in Iterable during cutover, ensuring the final HubSpot state reflects the latest data.

Will my Iterable journeys and campaigns migrate to HubSpot workflows?

No. FlitStack AI migrates data and schema only — Iterable journeys, campaigns, and behavioral logic do not transfer to HubSpot. They must be rebuilt manually using HubSpot lists and workflows. SMS and push channels require HubSpot-approved integrations (Twilio, Pushwoosh) post-migration. We export your Iterable journey definitions as a rebuild reference for your HubSpot admin. FlitStack AI also provides a step‑by‑step mapping guide that translates each Iterable journey node to equivalent HubSpot workflow actions, helping your team rebuild campaigns efficiently. After the migration, you can import the exported definitions into HubSpot and configure enrollment triggers to activate the new automations.

What does Iterable user profile data become in HubSpot?

Iterable user profiles migrate as HubSpot contacts with first name, last name, email, phone, and address properties preserved as direct mappings. Custom profile fields become HubSpot contact properties. Company associations from Iterable extract to HubSpot company records first, then link to contacts. Original created dates and user IDs are preserved in custom datetime and ID fields for reporting continuity. FlitStack AI also maps any custom profile attributes to corresponding HubSpot contact properties, preserving data types such as text, number, date, and boolean. The original Iterable user ID is stored in a custom field (Source_System_ID__c) for traceability and to support delta runs after migration.

Can I migrate Iterable custom events to HubSpot timeline activities?

Yes. Iterable custom events map to HubSpot timeline activities on contact records. Event names become activity types and original timestamps are preserved. HubSpot limits portals to 10 custom event types — we aggregate high-cardinality event names by prefix or behavior category and store the original event name as a property. Complex event taxonomies should be validated against this limit before migration.

What happens to Iterable catalog data in HubSpot?

Iterable catalog entries (products with SKU, name, description, price) migrate to HubSpot Product Library records directly. Product metadata and custom attributes become HubSpot product custom properties. Catalog variants map to separate products or custom fields. Purchase events then link to these products via line items on HubSpot deals. FlitStack AI also transfers product images and key metadata (inventory, weight) as custom properties. Variants in the catalog are either created as separate HubSpot products or stored in a custom variant field, per your configuration. After migration, you can manage pricing and stock directly in HubSpot's Product Library.

Does the migration affect my Iterable account during cutover?

No. FlitStack AI uses scoped read access on Iterable — your team keeps working in Iterable during migration. A delta-pickup window (24–48 hours) captures any records created or modified in Iterable during the cutover so HubSpot reflects Iterable's final state at go-live. No messages send and no workflow triggers fire during extraction. FlitStack AI only reads from Iterable using project‑scoped API credentials, never writing or modifying any data. During extraction, you can monitor progress in the FlitStack dashboard and see real‑time counts of exported records. The process respects Iterable's API rate limits, pausing and retrying as needed to avoid throttling.

How does HubSpot lifecycle stage get assigned from Iterable data?

Iterable has no native lifecycle field — we derive it from behavioral signals. Contacts with purchase events receive lifecycle_stage='customer'. High-frequency engagement without purchase receives 'opportunity' or 'lead'. No behavioral data defaults to 'subscriber'. You can customize this mapping logic before migration runs. Teams with complex lead scoring should validate against HubSpot reporting requirements. FlitStack AI maps each Iterable event type to a HubSpot lifecycle stage using configurable rules that you can adjust before migration. The mapping engine evaluates event frequency, recency, and purchase history to assign the appropriate stage. You can preview stage assignments on a sample dataset and tweak the logic in the FlitStack console.

Get a quote

Moving from Iterable 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