Migrate your Iterable data

Iterable's primary contact object. Every profile has a dataId, email, userId, and a set of system fields plus unlimited custom fields. We export profiles with their full field map and reimport preserving all custom field values, including multi-value arrays and nested data structures.

Custom events track behavioral data beyond profile updates. Each event has a name, user identification, and arbitrary metadata payload. We migrate the full event history per user, preserving event names and payload schema exactly as they exist in the source.

Lists are collections of user profiles used for audience segmentation and campaign targeting. We map list memberships at the user level and preserve list names and IDs so existing Journey triggers referencing those lists remain valid after migration.

Campaigns are the sendable units in Iterable, each with a name, channel type, template, and sending configuration. We export campaign metadata including channel, status, and schedule but note that template content and campaign settings require manual review post-migration due to the wide variation in campaign configurations.

Journeys are Iterable's workflow engine defining multi-step, multi-channel automation paths. Each Journey has trigger conditions, branching logic, and associated message actions. Journey definitions are complex JSON structures; we export the full Journey configuration and flag re-trigger eligibility settings that may behave differently in the destination platform.

Templates define message content for campaigns and Journey steps, supporting HTML email, plain text, and dynamic personalization via Handlebars syntax. We export template content and metadata but note that template rendering depends on the destination's personalization engine, which may use different syntax than Handlebars.

Catalog is Iterable's product data store used for dynamic content insertion in messages. We export catalog schemas and item records. Note that Catalog relationships to Journey steps must be revalidated after migration since destination platforms use different catalog/attribute data models.

Purchase events record transaction data including orderId, total, items, and associated user. We preserve the purchase event history and link each event to the corresponding user profile. Note that messaging-related metrics include bounces but exclude send skips and proof sends.

Subscription status tracks channel-level opt-in/opt-out states per user. We migrate subscription status per channel (email, SMS, push) and preserve subscription event history to maintain suppression lists correctly in the destination.

Iterable Data Sync is a warehouse export feature gated behind Customer Success and requiring IP allowlisting. We export historical Data Sync records but note that the feature requires CSM coordination to configure and is not a self-serve export path.