The migration story behind this comparison
A lot of people searching Iterable vs Salesforce Marketing Cloud are already on SFMC. The typical situation: a retail, media or subscription brand has run SFMC for years, the lifecycle team wants to launch and test journeys faster, and every change seems to need a developer, a SQL query or an agency ticket. Iterable is one of the platforms those teams evaluate.
Other teams search the reverse: they are growing on Iterable and the company has standardised on Salesforce, so the question becomes whether to consolidate. Both directions are covered below. For the vendors on their own, see our Iterable comparison and Salesforce Marketing Cloud comparison.
Why teams leave SFMC for Iterable
Autonomy. In Iterable, a lifecycle marketer can create a segment, build a Studio journey, write a Handlebars template and launch an experiment without engineering help. In SFMC, the same work often means a SQL query activity to build the audience, AMPscript for dynamic content and a data extension change, each of which needs someone who knows SFMC well.
One place for channels. Iterable puts email, push, SMS, WhatsApp, in-app and embedded messages in the same journey. SFMC splits them across Email Studio, MobileConnect and MobilePush, each with its own configuration.
Testing whole journeys. Iterable's journey experiments compare different paths, not only different emails, which is how lifecycle teams want to optimise.
Simpler personalisation data. Iterable's Catalog stores products, content or locations that templates look up at send time. In SFMC the equivalent is a lookup data extension and AMPscript, which is more flexible and harder to maintain.
Why teams stay on SFMC
Salesforce is the system of record. Marketing Cloud Connect syncs Sales and Service Cloud objects, and Journey Builder can create tasks, update records and trigger from CRM changes. Marketing Cloud Next builds on Data Cloud and adds Agentforce campaign creation. If your customer data and teams live in Salesforce, moving away creates integration work.
Data complexity. When audiences come from many systems (commerce, loyalty, stores, call centres) and must be joined, SFMC's SQL on data extensions is powerful. Iterable expects data to arrive clean through its API, data feeds or a CDP.
Suite breadth. Advertising Studio, CloudPages, personalisation, loyalty and intelligence add-ons come from the same vendor.
Existing investment. Certified staff, agency contracts and years of AMPscript templates are sunk costs that make switching expensive.
Pricing reality and the channel cliff
Salesforce publishes Engagement+ list prices, billed annually: Pro+ $2,000 per month with 15,000 contacts and 2.5M emails, Corporate+ $5,500 with 45,000 contacts, and Enterprise+ $30,000 with 500,000 contacts. Marketing Cloud Next Growth and Advanced list at $1,500 and $3,250 per month. Most SFMC customers also pay an implementation partner.
Iterable does not publish prices. Quotes are based on audience size, channels, message volume, data needs and support level, on an annual contract. Ask for platform fees, channel costs and services to be separated so you can compare fairly.
The list prices hide a jump that matters to lifecycle teams. Take a subscription brand with 12,000 contacts sending about 2 million emails a year, which fits inside Pro+. Now add push notifications for its app.
| Plan need | SFMC edition | List price | What it includes |
|---|---|---|---|
| Email only | Engagement+ Pro+ | $2,000/month ($24,000/year) | 15,000 contacts, 2.5M emails |
| Email plus push | Engagement+ Corporate+ | $5,500/month ($66,000/year) | 45,000 contacts, 10M emails, 1M mobile app messages |
Pro+ lists no mobile app messages, so on list prices the step to Corporate+ is $42,000 a year before implementation. Ask Salesforce whether mobile messaging can be added to Pro+ for your case. On Iterable, push and in-app are part of the core platform, so ask instead how channel volume affects the quote.
Questions to put to both vendors
Because neither evaluation is self-serve, the quality of your decision depends on what you ask during the sales process.
- Who will build a new journey after launch? Ask each vendor to show a marketer, not a solutions engineer, building a three-step journey with a branch on purchase data. Time it.
- How fresh is the audience? Ask how quickly a behaviour in your product can change what someone receives. In SFMC, find out whether your journeys would run on scheduled data extension refreshes or API events. In Iterable, ask how your data feeds and CDP sync will be configured.
- What does personalisation cost in maintenance? Ask to see a real template with dynamic product content in AMPscript and in Handlebars with a catalog lookup, and decide which your team can maintain.
- What is in the contract? For SFMC, confirm which studios, contact counts, email allowances and add-ons are included. For Iterable, confirm channels, message volumes, data limits and support tier.
- What does the first year really cost? Include implementation partners, IP warm-up, parallel running and training.
A proof of concept worth running
If you can, run one real journey on both before signing. A good candidate is a browse or cart abandonment flow that needs product data, a wait, a branch on whether the person converted, and a second channel. It exercises data freshness, catalog or lookup data, templating, channel orchestration and reporting in a single test, and it quickly shows how much of the work your marketers can do alone.
Skills, training and partners
SFMC has a large ecosystem around it: Trailhead training, official certifications such as Marketing Cloud Email Specialist and Marketing Cloud Developer, and many consulting partners. That makes it easier to hire for, and it is also a sign of how much specialist knowledge the platform needs.
Iterable's ecosystem is smaller. Most customers rely on Iterable's own onboarding and customer success, plus a handful of agencies. Because more of the daily work is done by lifecycle marketers rather than developers, you usually need fewer specialists, but you will find fewer experienced Iterable operators on the job market than SFMC ones.
Personalisation in practice
Most of the day-to-day difference shows up in templates.
In SFMC, dynamic content usually means AMPscript: set variables, look up rows in a data extension, loop over results and format output. SSJS covers heavier logic, and Content Builder stores reusable blocks. It is expressive, but it lives in code that a marketer cannot safely edit.
In Iterable, templates use Handlebars expressions and helpers. User profile fields and event payloads are available directly, and catalog lookups replace most data extension lookups. Snippets hold reusable pieces. Marketers can usually read and adjust a Handlebars template, and developers step in for complex logic.
If you migrate, the template rewrite is often the longest single task, because every AMPscript lookup needs a new data source in Iterable.
Migration checklist
Most enterprise moves take several months end to end, with both platforms running during IP warm-up.
| Workstream | SFMC to Iterable | Iterable to SFMC |
|---|---|---|
| Data model | Map data extensions to user fields, events and catalogs | Design data extensions and sendable audiences for users and events |
| Data flows | Replace Automation Studio imports with API, data feeds or CDP syncs | Replace feeds and API updates with imports, Marketing Cloud Connect or Data Cloud |
| Templates | Rewrite AMPscript and SSJS as Handlebars; Content Builder blocks become snippets | Rewrite Handlebars and catalog lookups as AMPscript and lookup data extensions |
| Journeys | Rebuild Journey Builder and Automation Studio logic in Studio | Rebuild Studio journeys in Journey Builder |
| Consent | Import publication lists, unsubscribes and suppressions | Import subscription preferences into All Subscribers and publication lists |
| Channels | Move MobilePush and MobileConnect to Iterable's push and SMS | Set up MobilePush and MobileConnect modules |
| Deliverability | Warm new IPs over several weeks | Same |
Use-case matchups
| Situation | Better fit | Why |
|---|---|---|
| Retailer whose lifecycle team waits weeks for SFMC changes | Iterable | Marketers build journeys and templates themselves |
| Insurer joining policy, claims and CRM data for campaigns | SFMC | SQL on data extensions and native Salesforce data |
| Media app mixing email, push and embedded messages | Iterable | App channels in the same Studio journey |
| Enterprise with SFMC developers and a Salesforce-first IT policy | SFMC | Existing skills, contracts and security reviews |
| SaaS team sending lifecycle and billing email | Sequenzy | Self-serve, email-focused, Stripe-triggered |
Where Sequenzy fits
Sequenzy is not built for brands messaging millions of consumers across app channels. It fits SaaS teams who want the thing people move to Iterable for, marketer autonomy, at a smaller scale and price. Campaigns, segments and lifecycle sequences are built in the UI, billing emails trigger from Stripe, and transactional email runs from the same account. It has no in-app, ad audiences or Salesforce sync.
Decision checklist
- Do marketers need to launch journeys without a developer? Iterable.
- Is Salesforce your system of record for customers? SFMC.
- Do you need SQL-level joins across many data sources? SFMC.
- Do push, in-app or embedded messages sit next to email in your journeys? Iterable, or budget for SFMC Corporate+.
- Do you already employ SFMC developers or an agency? Staying on SFMC is lower risk.
- Is your program mostly SaaS lifecycle email at thousands, not millions, of users? Sequenzy.
