MIGRATING TO ITERABLE
Leave your old platform without leaving what works behind.
Every platform is different. We’ve mapped the common migration risks, so you know what to expect and how we’ll handle them.
Teams that made the move.
MIGRATION PLAYBOOKS
See exactly how your platform translates to Iterable.
What moves, what gets rebuilt, and what we protect along the way. We plan your migration around your current renewal, so you can start now without paying for two platforms longer than you need to.
From Braze
- Canvases rebuilt as cross-channel Journeys
- Liquid translated to Handlebars
- SDK transition planned to protect push tokens and in-app messaging
- Event data mapped to preserve key segment
From Salesforce Marketing Cloud
- Data extensions mapped to profiles and events
- AMPscript translated to Handlebars
- Preference centers rebuilt for Iterable
- Business units mapped to Iterable projects
From Klaviyo
- Flows rebuilt as Journeys
- Segments rebuilt as dynamic lists
- Klaviyo.js replaced with Iterable’s Web SDK
- Commerce data connected via API
From Attentive
- Number transfers managed with carriers
- Consent audited before subscribers move
- Keywords, sign-up units, and SMS journeys tested before launch
- Top SMS journeys expanded to email and push
From Bloomreach
- Jinja translated to Handlebars
- Web tracking transitioned without data gaps
- Product data structured for Iterable Catalog
- Purchase history mapped to events
From SAP Emarsys
- Automation Center programs rebuilt as real-time Journeys
- ESL translated to Handlebars
- Web Extend replaced with Iterable’s Web SDK
- Sales, product, and relationship data mapped to events and Catalog
Moving from another platform? The same method applies.
A MIGRATION PLAN BUILT AROUND YOUR PROGRAM
Know what moves first, what can wait, and what needs to work on day one.
Together, we map your migration around four things:
Your approach
Move as-is, redesign, or rebuild around new use cases.
Your priorities
Decide which channels and brands move first.
Your must-haves
Identify what needs to work on day one.
Your timing
Plan around contracts, peak seasons, and dependencies.
BUSINESS CONTINUITY
Protect your program during the move.
Whatever you decide to move, we safeguard it along the way, so your customers never notice the switch.
No gap in sending
Your current campaigns keep running until their Iterable versions are tested and live.
Deliverability
You warm up gradually, starting with your most engaged audiences, and our deliverability team steps in if inbox placement dips.
Data accuracy
Your schema is built and tested in a sandbox project before anything reaches production.
Consent and preferences
Opt-ins and subscription preferences are audited and mapped before any subscriber moves.
TIMELINE
Send your first campaign in weeks.
Your timeline depends on what you’re moving. We sequence the work around your priorities and your current renewal, so you can start sending safely while the rest of your migration continues.
From signature to kickoff
To your first send once the build begins
For a focused email migration
For multi-channel migration
From moving over to running campaigns on Iterable
“The Iterable support team was quick to respond with answers to our questions.”
Loren Elia, Honeybook
COMMON QUESTIONS
What teams ask before they switch.
No. You choose what moves, with a focus on high-value history like purchases and recent engagement.
Plan for roughly 45–60 hours per brand for pipelines and SDK work. We’ll refine this during discovery.
We use a warm-up plan to protect it, starting with your most engaged audiences and monitoring deliverability.
Your team, a partner, or both. You choose the model that fits.
Yes. Certified Partners can lead the migration. If yours isn’t certified, we can train and support them.
Yes. We’ll hand you off to Customer Success, your Account Manager, Technical Support, and an Executive Sponsor.
Choose from Standard, Plus, or Premier support. Premier includes 24/7 coverage, phone, Slack, and a named Support Specialist.