Iterable is a well-rated ESP, and the departures here do not point to one recurring product failure. More of its buyers rate it 8 or above than 6 or below, and its lower raters are the ones who describe it as complex to run and expensive. The departures often reflect a change in requirements rather than a single recurring product failure: one platform for several apps, a compliance requirement, a commerce replatform. Buyers also move onto Iterable from heavier suites, which is part of the picture too. The two head-to-heads are Braze vs. Iterable and Klaviyo vs. Iterable.
The alternatives, by what they are
Every destination buyers name, grouped by the kind of platform. Five went to a cross-channel platform, four to an ecommerce ESP, and two to an enterprise suite.
What lower-rating Iterable buyers complain about
That it is complex to run, and leans on engineering. It is one of the two complaints that most separate lower raters from higher ones. “Technically, you can accomplish a lot in scope, but you're kind of on your own,” says a buyer rating it 6. Another, also at 6, says that when they need to act on data that is not already in Iterable, “we need engineers.”
That journeys are hard to change once built. One low rater describes having to “create journeys that can be months long, and they're very difficult to edit or change.”
And that it costs a lot, and more as you grow. “Honestly, the biggest issue with Iterable is our cost is way too high,” says a buyer rating it 5. Another, at 6, says “the price of Iterable just increases as you scale your businesses.”
Where buyers go
Eleven buyers here have left Iterable or are leaving it. The destinations show different patterns. The Braze moves include consolidation, compliance and channel requirements; three of four Klaviyo moves coincide with Shopify replatforms. The remaining two went to enterprise suites: one was explicitly mandated by an enterprise-wide contract, and the reason for the Salesforce Marketing Cloud move is not established here. Ten more are weighing a move, mostly at renewal, and name Braze, MoEngage, Klaviyo, Customer.io and HubSpot.
Cross-channel platform
The reasons differ. One company “sunset Iterable to wrap all of our apps into one primary app with Braze.” Another left because “There were some compliance legal things that Iterable wasn't able to hit for us.” A third switched only because “we wanted an ESP that had subscription at the time,” and a fourth used a renewal to look around. One of them finds Braze has “a much steeper learning curve than Iterable.”
Ecommerce ESP
Three moved alongside a move to Shopify. One “switched over from Iterable mostly because of the ease of the Shopify Klaviyo connection and the pre-built automations”; for another, “Iterable was our ESP prior to Shopify.” The fourth found Klaviyo “a lot better integrated across other tools and was easier to work with from a design and performance perspective.”
Enterprise suite
A move the buyer did not choose: “there's no choice to stay on the platform, and that's due to an enterprise-wide contract.” They would rather stay — “a lot of the features that are sort of out of the box for Iterable aren't the same for Adobe Journey Optimizer.”
No head-to-head published yet
A consumer app company is “in the process of migrating over to Salesforce Marketing Cloud,” and expects it to take a while: “we have a lot of journeys in Iterable to migrate.”
The two main destinations do not look interchangeable. The Braze moves describe what the business needed from one platform — several apps in one place, a compliance standard, a subscription channel. Three of the four Klaviyo moves coincided with a move to Shopify. None of these Braze or Klaviyo departures is described here simply as Iterable failing at email or lifecycle messaging.
Want this read against your own stack?
Get my read →When does staying on Iterable make sense?
Most of its buyers rate it well, and some are moving onto it from heavier platforms.
Segmentation, journeys and flexible data. “There's a lot that they offer from a segmentation standpoint or from a customer journey standpoint,” says a buyer rating it 8. Another, also at 8, says “It handles data fields really well, is pretty flexible on that side in terms of customizing data fields and data events and attributes.”
A marketer-friendly interface. “I think we like Iterable because the interface is really user-friendly,” says a buyer rating it 8. Teams moving onto it from Salesforce Marketing Cloud describe the same thing: one says Iterable “has a lot more drag-and-drop and features that make work a lot more efficient and faster,” and another is moving mainly for “the in-app communication.”
For one buyer, favorable contract economics. A buyer weighing Klaviyo says replacing Iterable is on hold “because we have a really good contract with Iterable, which makes it a little bit difficult for us to move on to a different platform.”
Our read — ours, not a buyer’s — is that these departures do not point to one recurring Iterable failure. Several reflect changed requirements around channels, compliance or the surrounding commerce stack, while buyers moving onto Iterable from heavier suites describe advantages in usability and marketer workflow.
Common questions
Why do buyers leave Iterable?
There is no single exit reason in these interviews. The five who moved to Braze describe consolidating several apps onto one platform, compliance requirements Iterable could not meet for them, wanting subscription support, and a renewal used as a chance to look around. Three of the four who moved to Klaviyo did so alongside a move to Shopify. Across current Iterable buyers, complexity and cost are the complaints that most separate lower raters from higher ones.
What do buyers replace Iterable with?
Of eleven departures here, five went to Braze, which rates 7.5/10, and four to Klaviyo, which rates 7.7/10, against Iterable's 7.1/10. One is moving to Adobe Journey Optimizer under an enterprise-wide mandate, and one to Salesforce Marketing Cloud. Buyers weighing a move at renewal also name MoEngage, Customer.io and HubSpot.
Is Braze better than Iterable?
The interviews do not establish one as universally better; Braze rates 7.5/10 against Iterable's 7.1/10. Buyers who moved to Braze describe specific needs — consolidating apps, compliance, subscription support — and one finds Braze has a much steeper learning curve than Iterable. Buyers who stayed on Iterable or moved onto it describe its segmentation, journeys and drag-and-drop interface.
Do Shopify brands move from Iterable to Klaviyo?
Three of the four Klaviyo moves here coincided with a move to Shopify. One buyer explicitly says it switched largely because of the Shopify connection and Klaviyo's pre-built automations; the other two are observed alongside the replatform. The fourth cites broader integration, design and performance advantages. None of the Braze movers describe a Shopify move.
Is Iterable expensive?
Cost is one of the two complaints that most separate its lower raters from its higher ones, and buyers weighing a move at renewal raise it often — one describes paying an extraordinary amount for the platform. Others describe pricing that rises as the business scales. It is not what most departures here cite, though: those describe changed requirements — channels, compliance or a commerce replatform.
Get this research made for your stack
Weighing a move off Iterable, or deciding between it, Braze and Klaviyo? Do a 15-minute interview about your channels, your stack and your team, and get a personalized read.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.