Migrate from Iterable to HubSpot

Iterable user profiles migrate as HubSpot contacts. 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.

Iterable user profiles often contain company name and domain. 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.

Iterable custom events (arbitrary event names with JSON payloads) translate to HubSpot timeline events. 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.

Iterable purchase events carry order ID, total amount, and product items. 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.

Iterable catalog entries (collections with SKU, name, description, price, metadata) map to HubSpot Product Library records. 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.

Iterable static lists migrate as HubSpot static lists. 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.

Iterable dynamic segments based on behavioral criteria have no direct HubSpot equivalent. HubSpot active lists support static membership and some behavioral triggers but not full nested behavioral logic. We export segment definitions as reference documentation for manual rebuild using HubSpot lists and workflows.

Iterable journeys contain multi-step branching logic, wait conditions, channel routing (email, SMS, push), and A/B testing configurations. HubSpot workflows support enrollment-based automation but lack native SMS and push channels without third-party integrations. Journey definitions are exported as a rebuild reference; channels must be reconnected to HubSpot-approved integrations.

Iterable campaigns (send definitions, templates, A/B tests) do not map to HubSpot CRM objects. We migrate campaign metadata as a reference custom property on contacts who received a campaign email. The campaign content itself must be rebuilt using HubSpot email templates and sequence tools.

Iterable subscription states (email subscribed, SMS opted-in) become HubSpot contact properties. We map channel-specific opt-out flags to HubSpot's marketing email subscription status. SMS consent flags migrate as custom boolean properties since HubSpot SMS requires separate integration configuration. These custom properties can be used in HubSpot workflows to control message delivery and compliance.

Campaign IDs, campaign names, and send timestamps attach to contacts as a custom property (Last_Campaign_Source__c). This preserves marketing attribution history from Iterable in HubSpot without native campaign membership sync. You can use this property in HubSpot reporting to analyze campaign performance and contact engagement over time.

Iterable file attachments linked to user profiles (images, documents) re-upload to HubSpot Files. File size limits (25MB per file in HubSpot) apply. Inline images used in Iterable email templates download and rehost within HubSpot's file manager. If any file exceeds the size limit, FlitStack AI compresses the image or splits the document into smaller parts before upload.