Migrate from Iterable to HighLevel

Iterable User Profiles map directly to GoHighLevel Contacts. The dedupe key is email address. We preserve the full Iterable field map including dataId, userId, email, and all custom profile fields. System fields from Iterable (createdAt, lastUpdated, signupSource) migrate as GoHighLevel Contact custom fields. Iterable's subscriptionStatus per channel migrates to the Contact's emailStatus and SMS status fields.

Iterable Custom Events carry arbitrary metadata payloads that have no direct GoHighLevel equivalent. We evaluate the event set during scoping: high-cardinality behavioral events (page views, feature interactions) become GoHighLevel Custom Fields with string or number types on the Contact object. Low-cardinality events with structured schemas (purchase events, subscription changes) are candidates for GoHighLevel custom objects with lookup to Contact. We flag event-to-field collisions where the same field name is used with different types across different event payloads.

Iterable Lists are collections of User Profiles used for audience segmentation. We export list memberships at the user level and create corresponding GoHighLevel Tags. Each Iterable list becomes one or more Tags; list names are preserved as tag names. If the customer uses list-based suppression (unsubscribed users on a suppression list), we map that to GoHighLevel contactStatus = inactive rather than a tag. GoHighLevel's Contact Groups provide an additional segmentation layer that we populate from Iterable list metadata.

Iterable Purchase events record transaction data (orderId, total, items, associated user). We extract the purchase event history per user and map order data to GoHighLevel Contact custom fields for recent purchases or to a custom Order object with Contact lookup for historical order records. The migration scope specifies whether to store purchase data on the Contact or in a separate custom object based on the customer's reporting needs.

Iterable Subscription status tracks channel-level opt-in and opt-out states (email, SMS, push) per user. We migrate subscription status per channel to GoHighLevel contactStatus and SMS fields. The full subscription event history (timestamps of each opt-in or opt-out) migrates as GoHighLevel Tasks or Notes attached to the Contact for audit trail purposes. Suppression lists from Iterable become inactive status records in GoHighLevel.

Iterable Campaigns (sendable units with channel type, template, and schedule) have no direct GoHighLevel equivalent. GoHighLevel uses Workflows for automated messaging sequences. We export campaign metadata including channel, name, status, and schedule, but note that campaign logic, A/B test configurations, and send-time optimization rules do not migrate. We deliver a written campaign inventory with recommended GoHighLevel Workflow equivalents for the customer's admin to rebuild.

Iterable Journeys are multi-step, multi-channel automation paths with trigger conditions, branching logic, and message actions. GoHighLevel Workflows are the equivalent automation construct. We export Journey definitions including trigger events, step sequence, branching conditions, wait timers, and message content references. We do not rebuild Journeys as Workflow code; we deliver a written Journey inventory documenting the trigger, conditions, actions, and recommended GoHighLevel Workflow structure for the customer's admin to rebuild.

Iterable Templates define message content for campaigns and Journey steps, supporting HTML email and dynamic Handlebars personalization. GoHighLevel Email Templates store HTML content with merge fields. We export template content, subject lines, and personalization tokens. Dynamic Handlebars expressions in Iterable require manual conversion to GoHighLevel merge field syntax. We deliver a template inventory with source content and field mapping so the customer's admin can recreate templates with dynamic content re-implemented in GoHighLevel's syntax.

Iterable Catalog stores product data used for dynamic content insertion in messages. GoHighLevel has no native Catalog equivalent. We export catalog schemas and item records and map them to GoHighLevel custom objects with custom fields matching the source schema. Catalog-to-Journey associations (which items appear in which Journey steps) are documented as part of the Journey inventory for manual reconfiguration in GoHighLevel. Product catalog migrations require custom object schema design during scoping.

Iterable Owners (users who created or are assigned to records) map to GoHighLevel Users by email match. We extract all distinct ownerIds from User Profiles, Custom Events, and Lists and match against the GoHighLevel destination's User table. Any Owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before import resumes.