Skip to content
Get a quote

Iterable to Salesforce migration

We migrate user profiles, custom events, campaign histories, and list memberships from Iterable into Salesforce Marketing Cloud with profile field schemas preserved, subscription states migrated across channels, and every active Journey documented for your team to rebuild in SFMC Journey Builder before cutover.

Short answer

FlitStack AI migrates contact + data extensions, data extensions, audience or data extensions, campaign reference records and journey builder reference inventories from Iterable to Salesforce, 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: 4-8 weeks.

By

Source Iterable
DestinationSalesforce
Contact + Data ExtensionData ExtensionAudience or Data ExtensionCampaign reference recordJourney Builder reference inventory
Mapped field by field · sample run · one-click rollback

What moves from Iterable to Salesforce?

Iterable and Salesforce Marketing Cloud are both cross-channel marketing platforms, but they organize data differently and require deliberate mapping during migration.

Read the full summary

Iterable uses a flat user-profile model with unlimited custom fields, lists for segmentation, and Journeys as the automation engine. Salesforce Marketing Cloud uses a Contact data model tied to a Data Extension architecture, with Journey Builder as the orchestration layer and separate Subscription Management for channel-level opt-out tracking. We map Iterable user profiles to SFMC Contacts and Data Extensions, migrate active list memberships as Audience membership, export campaign metadata and templates as reference records, and deliver a written Journey inventory so your SFMC admin can rebuild automation logic in Journey Builder. We do not migrate Journeys as code, Templates as code, or Automations. SMS configuration requires re-verification with carriers post-migration because SFMC manages sender IDs and long-codes independently from Iterable.

1:1

User Profile → Contact + Data Extension

Iterable user profiles map to SFMC Contact records using email as the Subscriber Key.

How it maps

System fields (dataId, userId, email, createdAt, updatedAt) map to standard SFMC Contact attributes. Custom profile fields migrate to a primary Data Extension with the same field names and types, linked to Contact via Subscriber Key. We flag any fields approaching Iterable's 8,000-field soft limit during scoping and consolidate redundant or deprecated fields before migration to avoid Data Extension schema bloat in SFMC.

1:1

Custom Events → Data Extension (event-log table)

Iterable custom events with their full metadata payloads migrate to a dedicated Data Extension that logs event name, user identification (Subscriber Key), event timestamp, and all custom event metadata columns.

How it maps

We flatten nested event metadata to top-level Data Extension fields during the transform phase. For recurring behavioral triggers that the customer wants to replicate in Journey Builder, we document the event schema and recommend Triggered Send or API Event entry sources.

configuration

List → Audience or Data Extension

Iterable Lists are flat user collections used for campaign targeting.

How it maps

We migrate list memberships as Contact membership in SFMC Audiences or as rows in a List-Name Data Extension keyed by Subscriber Key. Dynamic Lists require SQL Query Activities to replicate using Contact data and event filters. We preserve the original Iterable list names and IDs in the migration metadata for reference during Journey rebuild.

mapping

Campaign → Campaign reference record

Iterable campaign metadata (name, channel type, status, schedule, template reference, send configuration) exports as a reference record that we store outside SFMC as a migration artifact.

How it maps

SFMC does not have a native Campaign object equivalent to Iterable's campaign model. We deliver the campaign inventory as a structured CSV and a written summary so the customer's SFMC admin can recreate campaign reference data in SFMC Email Sends, Journey Builder entry configurations, or a custom Campaign object if the customer builds one in Salesforce CRM and links it via the SFMC-CRM connector.

mapping

Journey → Journey Builder reference inventory

Iterable Journeys define multi-step, multi-channel automation paths.

How it maps

We export Journey definitions including trigger conditions, branching logic, wait steps, and message action configurations as a written inventory document. SFMC Journey Builder uses a different event and activity model. We do not migrate Journeys as code. The inventory document maps each Iterable Journey to a recommended Journey Builder structure with entry source, activities, and split logic so the customer's admin or SFMC partner can rebuild them post-migration.

mapping

Template → Content Builder asset

Iterable HTML and Handlebars-templated message content migrates as asset records in SFMC Content Builder.

How it maps

We export template content, metadata, and personalization syntax. Handlebars conditionals and merge tags require manual conversion to SFMC AMPscript or Marketing Cloud Personalization (Interaction Studio) syntax during the SFMC implementation phase. We flag templates with complex dynamic logic for admin review before migration.

What moves12 objects
IterableSalesforce
  • User ProfileContact1:1
  • Custom EventsData Extension1:1
  • ListAudience or Data Extensiontransformed
  • CampaignCampaign reference recordtransformed
  • JourneyJourney Builder reference inventorytransformed
  • TemplateContent Builder assettransformed

+ 6 more in the mapping below

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

DimensionIterableSalesforce
Contact data modelFlat user profile with unlimited custom fields per projectContact record + Data Extensions as relational tables attached to Contact
Audience segmentationLists as flat user collections with dynamic membershipData Extensions as typed tables; Contacts segmented via SQL Query Activities or Audience Builder
Automation engineJourneys with trigger conditions, branching, and multi-channel message actionsJourney Builder with entry sources, activities, and decision splits; different event model
Channel supportEmail, SMS, push, in-app in a single platformEmail via Content Builder and Sends; SMS via separate MobileConnect; Push via separate MobilePush; In-app via separate Interaction Studio
Subscription managementPer-channel opt-in/opt-out stored on user profileAll Subscriptions center on the Contact record with channel-specific suppression lists
Template modelHTML and Handlebars-templated messages stored as named TemplatesContent Builder asset library; HTML templates as content blocks; Template as entry-point in Journey Builder
Data center separationSeparate API endpoints for USDC (api.iterable.com) and EDC (api.eu.iterable.com)SFMC uses tenant-specific subdomains; tenants are US or EU based with data residency constraints

What to watch for in a Iterable to Salesforce migration

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

high

Journeys do not migrate to Journey Builder

Iterable Journeys and SFMC Journey Builder are architecturally different.

How we handle it

Iterable uses event-triggered branching with a built-in delay engine; Journey Builder uses entry sources, activities, and decision splits that must be reconstructed manually. We export a written Journey inventory documenting every active Journey's trigger, conditions, branches, wait steps, and message actions with a recommended Journey Builder equivalent. The customer's SFMC admin or a certified SFMC partner rebuilds them post-migration. Skipping this step leaves marketing automation with gaps that are discovered only after cutover.

high

Iterable's USDC and EDC data centers require correct API targeting

Iterable operates api.iterable.com for USDC and api.eu.iterable.com for EDC.

How we handle it

API keys are scoped to a single data center and are not interchangeable. SFMC tenants are also region-specific (SFMC pods such as s7.s1, s6.s1, or EU pods). We confirm the customer's Iterable data center and SFMC tenant region during scoping and use the correct base URLs for extraction and loading. Cross-region mismatches result in authentication failures and silent data loss.

medium

Handlebars template syntax requires manual conversion to AMPscript

Iterable templates use Handlebars syntax for dynamic personalization ({{firstName}}, {{#if}} conditionals).

How we handle it

SFMC uses AMPscript and Template Language (GTL) for dynamic content. We export template content and flag any templates using Handlebars conditionals, loops, or partials for manual conversion to AMPscript or GTL. Templates migrated without conversion render as plain text or show literal Handlebars syntax in SFMC-sent messages.

medium

Iterable Catalog relationships require AMPscript lookup reconstruction

Iterable Catalog stores product data and references it directly in Journey message content.

How we handle it

SFMC does not have a Catalog equivalent; product data lives in Data Extensions and is accessed via AMPscript Lookup functions inside email content. We migrate Catalog schemas and items to SFMC Data Extensions but flag that every message referencing catalog data must be updated to use LookupAmpscript or LookupRows functions pointing at the migrated Data Extension.

low

Iterable field deletion is impossible; deprecated fields persist

Iterable does not allow field deletion once created.

How we handle it

Custom fields created during experimentation accumulate in the profile schema indefinitely. During migration scoping, we audit the active field set and recommend which deprecated fields to exclude from the SFMC Data Extension schema. If the destination SFMC tenant has a Data Extension column limit (255 columns per Data Extension), we consolidate related fields or split into multiple linked Data Extensions to avoid truncation.

How the migration runs

  1. Scoping and data center confirmation

    We audit the Iterable project including data center (USDC or EDC), user profile field count, custom event types and volumes, active Lists and list sizes, active Journeys, campaign history, Catalog schemas, and subscription event volumes.

    What this step covers

    We confirm the SFMC tenant region and edition. We deliver a written migration scope document specifying which objects migrate, which map to written inventories, and which require post-migration manual setup.

  2. Profile schema design and Data Extension architecture

    We design the SFMC contact schema and Data Extension structure based on the Iterable profile and event field audit.

    What this step covers

    This includes mapping Iterable custom fields to SFMC Data Extension columns with correct data types, designing linked Data Extensions for nested event payloads, and configuring Contact attribute relationships for use in Journey Builder entry conditions. Schema is validated in SFMC Sandbox or a parallel tenant environment before production migration.

  3. Contact and profile migration

    We extract all Iterable user profiles via the /api/users/getUsers endpoint with pagination, preserving the full field map including system fields and custom fields.

    What this step covers

    Profiles load into SFMC Contacts via the Contacts API or Bulk API with Subscriber Key as the dedupe key. Subscription status loads into Contact attributes and suppression lists simultaneously to maintain compliance throughout the migration window.

  4. Custom events, purchase history, and catalog data

    We export Iterable custom events, purchase events, and Catalog items to CSV or JSON format, transform nested metadata to flat columnar format, and load into the corresponding SFMC Data Extensions via Bulk API or Data Loader.

    What this step covers

    For large event histories (over 5 million events), we chunk the export and load in batches with exponential backoff to avoid Iterable API rate limits.

  5. List and audience migration

    We export all Iterable list memberships and recreate them in SFMC as Audience memberships or as rows in a List-Name Data Extension keyed by Subscriber Key.

    What this step covers

    Dynamic Lists require SQL Query Activity definitions that we document and hand to the customer's SFMC admin for configuration in Automation Studio. Suppression lists import to SFMC Suppression Lists and MobileConnect suppression data to ensure unsubscribed contacts remain suppressed at cutover.

  6. Journey and template inventory delivery

    We export Journey definitions as written documentation including trigger configuration, branching logic, message actions, and wait-step timing.

    What this step covers

    We export template content with metadata as Content Builder reference records. We do not rebuild Journeys or convert templates to AMPscript inside the migration scope. We deliver the inventory and a recommended rebuild guide to the customer's SFMC admin or partner.

  7. Cutover, validation, and post-migration handoff

    We freeze Iterable sends during cutover, run a final delta migration of any profiles modified during the window, validate contact counts and suppression list integrity in SFMC, and enable SFMC as the active sending platform.

    What this step covers

    We conduct a one-week hypercare window to resolve any data integrity issues. We do not provide ongoing SFMC admin support, Journey Builder configuration, or AMPscript development as part of the migration scope.

Iterable Salesforce
  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 · SalesforceRollback 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

4-8 weeksTypical, smaller accounts
12-20 weeksLarge or heavily customised accounts

A quote scales with contact volume, custom field count, campaign history depth, and Journey complexity. SFMC licensing costs (Contact-level pricing in Marketing Cloud Growth and Advanced editions, or edition-based in Legacy Professional and Enterprise) sit outside the migration fee and remain the customer's recurring cost. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Iterable to Salesforce →

Why teams move from Iterable to Salesforce

  • Iterable customers report opaque contract pricing that increases when usage is reduced, creating a billing model that penalizes teams who downscale. Salesforce Marketing Cloud editions provide clearer per-contact or per-send pricing tiers, and teams already paying for Salesforce CRM licenses may qualify for bundled Marketing Cloud pricing that reduces total stack cost versus a standalone Iterable contract.
  • SMS deliverability issues with accounts suspended or blocked without clear accountability are a recurring complaint in Iterable reviews. SFMC MobileConnect manages its own sender IDs, long-codes, and short-codes with dedicated deliverability tooling and SFMC support escalation paths, giving teams more visibility into carrier-level issues than they report receiving from Iterable.
  • Teams already running Salesforce CRM often cite platform consolidation as a driver. Reviewers on Reddit and G2 mention that using Iterable alongside Salesforce CRM creates duplicate Contact records, sync lag, and integration maintenance overhead that disappears when marketing automation lives inside the same Salesforce org via Marketing Cloud.
  • Iterable's cluttered UI requiring multiple nested clicks to complete common campaign tasks drives teams to evaluate alternatives. SFMC's Content Builder, Email Studio, and Journey Builder interfaces are widely documented, have established UI patterns familiar to Salesforce admins, and integrate with Salesforce CRM data without a separate integration layer.
  • Limited reporting consistency in Iterable makes cross-channel performance measurement difficult. SFMC provides Advertising Studio reporting, Email Studio tracking, and Marketing Cloud Intelligence (Datorama) integration for unified multi-channel attribution, addressing the measurement gap that drives teams to consolidate reporting inside Salesforce.

Questions, answered

Iterable to Salesforce migration questions

How long does an Iterable to Salesforce Marketing Cloud migration take?

Migrations under 250,000 contacts with straightforward profile schemas and no complex Data Extension relationships typically complete in four to eight weeks. Migrations with large custom event histories, multiple active Journeys, Catalog data requiring Data Extension schema design, or EU data-center constraints move to twelve to twenty weeks. Discovery and scoping account for one to two weeks regardless of size.

Do Iterable Journeys migrate to SFMC Journey Builder?

No. Iterable Journeys and SFMC Journey Builder use different automation models. We do not migrate Journeys as code. We deliver a written Journey inventory that documents every active Journey's trigger, conditions, branches, message actions, and wait steps with a recommended Journey Builder structure. Your SFMC admin or a certified SFMC partner rebuilds the automation logic post-migration.

Can we keep Iterable for SMS while moving email to SFMC?

Yes. A hybrid approach is feasible where SFMC handles email campaigns and Journey Builder while Iterable continues managing SMS and push channels. We migrate the email-relevant contact data, subscription status, and list memberships to SFMC and leave SMS data in Iterable. The customer manages two sending platforms during the transition. Full migration to SFMC for all channels is recommended once Journey rebuild is complete to eliminate dual-platform overhead.

Do Iterable Templates migrate as SFMC Content Builder assets?

Template content migrates as HTML assets in SFMC Content Builder. However, Handlebars personalization syntax in Iterable templates requires manual conversion to AMPscript or GTL before the templates will render dynamic content correctly in SFMC. We export the template content and flag any templates with Handlebars conditionals, loops, or dynamic partials for admin review. Simple static templates migrate without conversion work.

What happens to Iterable Catalog data in SFMC?

Iterable Catalog schemas and item records migrate to SFMC Data Extensions. However, the dynamic content insertion that references Catalog items in Iterable Journeys and templates requires reconstruction using AMPscript Lookup functions inside SFMC email content. We deliver the catalog data in SFMC-ready format and document the required AMPscript changes for each message that previously referenced catalog data.

Will migrated contacts retain their unsubscribe preferences?

Yes. We migrate Iterable channel-level opt-out states to SFMC Contact attributes (HasOptedOutOfEmail) and to channel-specific suppression lists in MobileConnect and MobilePush. Subscription event history also migrates to maintain suppression logic. Contacts who unsubscribed in Iterable remain suppressed in SFMC and cannot receive messages until they re-subscribe through an SFMC preference center.

What happens to historical campaign performance data?

Iterable campaign performance metrics (open rates, click rates, conversion data) do not migrate because SFMC does not have a campaign-level analytics object equivalent to Iterable's campaign reporting. We export campaign metadata (send dates, subject lines, channel, audience size) as a reference document. The customer's SFMC admin can use SFMC Analytics Builder, Datorama, or Marketing Cloud Intelligence to establish new performance baselines post-migration.

Get a quote

Moving from Iterable to Salesforce?

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

Get a quote