Migrating from SAP Emarsys to Klaviyo is an export and a rebuild. Contacts come out of Emarsys with their email and SMS opt-in status, programs are rebuilt as Klaviyo flows on Shopify events, and ESL personalization is rewritten in Klaviyo's template tags. Purchase history does not need to come from Smart Insight, because Klaviyo pulls it straight from Shopify. The steps that matter most are opt-in mapping and loyalty: an empty opt-in is not consent, and loyalty balances have to be exported before anything in Emarsys is deleted. Sticky Digital runs the whole migration in eight weeks or less.
SAP Emarsys to Klaviyo Migration for DTC Brands
Sticky Digital is a Klaviyo Platinum Partner and a retention-only email and SMS agency for Shopify brands, running since 2019. We move SAP Emarsys programs, now sold as SAP Engagement Cloud, to Klaviyo in eight weeks or less, and the team that runs the migration is the team that runs your program afterward.
Last updated:
-
8 weeks
Maximum, from audit to cutover
-
25% to 40%
Of store revenue from email within six months, typical for our clients
-
Since 2019
Retention only, email and SMS
Should you migrate from SAP Emarsys to Klaviyo?
Is SAP Emarsys the same as SAP Engagement Cloud?
What is the difference between SAP Emarsys and Klaviyo?
How do you export your data from SAP Emarsys?
What happens to Emarsys Loyalty and vouchers?
What transfers from SAP Emarsys to Klaviyo, and what has to be rebuilt?
The list moves. The logic around it is rebuilt, ideally simpler than before.
| Moves over | Has to be rebuilt |
|---|---|
| Contacts with external ID, email and phone | Every program, rebuilt as a Klaviyo flow |
| Email and SMS opt-in status, mapped to Klaviyo consent | ESL personalization, rewritten in Klaviyo's template tags |
| False opt-ins and unsubscribes, uploaded as suppressions | Segments, rebuilt on Shopify events and Klaviyo properties |
| Custom fields customers filled in, as profile properties | External events, replaced by Shopify events wherever possible |
| Loyalty members, points and tiers, into your loyalty app | Predict recommendations, rebuilt on Klaviyo product feeds |
| Order history, re-synced from Shopify rather than Smart Insight | Signup forms and web channel campaigns, rebuilt as Klaviyo forms |
| SMS subscribers with consent, and a dedicated number by porting | Vouchers, replaced by Shopify coupon codes in Klaviyo |
Opt-in moves as it is. True stays subscribed, false is suppressed, and empty is treated as not subscribed.
How do SAP Emarsys features map to Klaviyo?
The table most Emarsys migrations skip. Porting programs node for node is how you end up on a new platform running the old program.
| SAP Emarsys | Klaviyo equivalent | What changes |
|---|---|---|
| Interactions and Automation Center programs | Flows | Triggered by Shopify events wherever possible, with branches your marketing team can edit. |
| Contact fields | Profile properties | Keep what customers told you. Retire fields that only mirrored order data. |
| Opt-in field and SMS opt-in | Email and SMS consent | False and empty never come across as subscribed. |
| Smart Insight sales data | Shopify order sync | Order history arrives from Shopify, with no daily sales file to maintain. |
| Web Extend | Klaviyo onsite tracking | Viewed Product and Active on Site start tracking the day it is installed. |
| External events | Shopify events or custom metrics | Most commerce triggers come from Shopify natively. Keep custom events only where Shopify has no equivalent. |
| Segments | Segments | Rebuilt on Klaviyo events and properties. Membership updates in real time. |
| ESL and relational data | Template tags and universal content | Every condition, loop and fallback is rewritten and tested on real profiles. |
| Predict recommendations | Klaviyo product feeds | Rebuilt on purchase and browse data from Shopify. |
| Loyalty | Shopify loyalty app synced to Klaviyo | Members, points and tiers imported before Emarsys is switched off. |
| Web channel | Klaviyo signup forms | Targeted by page, behavior and source, A/B tested, and feeding consent straight onto the profile. |
| SMS and push | Klaviyo SMS and push | Subscribers move with consent. Dedicated numbers can usually be ported. |
What is the most common SAP Emarsys to Klaviyo migration mistake?
How does Sticky Digital run a SAP Emarsys to Klaviyo migration?
-
1. Week 1: Audit, before anything moves. We map which programs and campaigns generate revenue, both opt-in fields and how they are set, the ESL, relational data and external events behind your key messages, whether you run Loyalty, which channels beyond email and SMS earn their keep, and when your contract renews. That decides what gets rebuilt, what gets retired, and in what order. If you are keeping a short code, the port request goes in this week.
-
2. Weeks 1 to 2: Data, consent and infrastructure. Contacts are exported with both opt-in fields and the custom fields worth keeping. False opt-ins and unsubscribes are suppressed in Klaviyo before anything else. Loyalty balances are exported and checked. Shopify is connected, order history syncs, the sending domain is authenticated with SPF, DKIM and DMARC, and the account architecture is built before a single flow goes in.
-
3. Weeks 2 to 4: Flow, template and segment rebuild. Revenue programs are rebuilt as Klaviyo flows on Shopify events, the highest earning first. ESL personalization is rewritten in Klaviyo's template tags and tested with real profiles. Segments are rebuilt, recommendations move to product feeds, and signup forms replace any web channel campaigns that collected email or SMS.
-
4. Weeks 3 to 8: Warm-up and cutover. Sending starts with your most engaged subscribers and volume ramps over four to six weeks while complaint and bounce rates are checked daily. Emarsys stays live until Klaviyo is performing, then its programs are stopped so nobody gets messaged twice.
Eight weeks at most, end to end, because the stages overlap instead of waiting on each other. The one thing on someone else's clock is an SMS short code port: carriers set that timeline, and Klaviyo puts it at eight to twelve weeks. We file it in week one and your texts keep sending from Emarsys until it lands. Work backward from your renewal date, not forward from today.
How we price SAP Emarsys to Klaviyo migrations
Can you migrate from SAP Emarsys to Klaviyo yourself?
Sometimes, yes.
| DIY is reasonable when | Bring in an agency when |
|---|---|
| Under 25,000 contacts | Over 50,000 contacts, or a database far larger than the opted-in list |
| Email opt-in only | Email and SMS opt-in, plus contacts with an empty opt-in |
| A handful of simple programs | Many programs on external events, relational data or Predict |
| Little ESL | Heavy ESL and dynamic content |
| No Emarsys Loyalty | Loyalty members, points and tiers to move |
| No peak season or renewal within twelve weeks | BFCM, a launch or your Emarsys renewal within twelve weeks |
The risk in a DIY Emarsys migration is almost never the export file. It is opt-in mapping, loyalty, template rewrites and the warm-up judgment calls.
Who this is not for
SAP Emarsys to Klaviyo migration FAQ
Sticky Digital completes SAP Emarsys to Klaviyo migrations in eight weeks or less. The audit takes about a week, data and opt-in status move in the first two weeks, programs and templates are rebuilt over two to three weeks, and the four to six week warm-up starts as soon as the first flows are tested. An SMS short code port runs on the carriers' schedule, and texts keep sending from Emarsys until it lands.
Yes. SAP renamed the SAP Emarsys solution to SAP Engagement Cloud on February 19, 2026, and says existing Emarsys capabilities remain available within it. The migration process is the same under either name.
We export the email Opt-in field, field ID 31, and the SMS opt-in field for every contact. True becomes subscribed in Klaviyo, false is suppressed, and empty is treated as not subscribed, because an empty opt-in is not consent.
Usually not. For a Shopify brand, Klaviyo syncs order history directly from Shopify, so segments, predicted lifetime value and repeat purchase flows work from day one without rebuilding sales files.
No. Klaviyo uses its own template tags, so every ESL condition, loop and relational data lookup is rewritten and tested. The layout can be reused, but the personalization logic is rebuilt.
Members, points and tiers are exported and imported into a Shopify loyalty app that syncs to Klaviyo, chosen in the audit. Nothing in Emarsys is deleted until balances are checked, because deleting an Emarsys contact also removes their Loyalty rewards.
Usually. Dedicated short codes and toll-free numbers can be ported to Klaviyo, while shared short codes cannot. A toll-free number usually ports in two to four weeks and a short code in eight to twelve. SMS subscribers come across with their consent.
With Sticky Digital, migrations to Klaviyo cost $0 to $25,000, depending on account size and the discount we are able to offer. Some brands qualify for a free migration.
It can, if warm-up is handled badly. Klaviyo starts with no engagement history of its own, so sending begins with your most engaged subscribers and volume ramps over four to six weeks while complaint and bounce rates are watched daily. Emarsys stays live until Klaviyo is performing.
Work backward from your Emarsys renewal date. We do not recommend starting within twelve weeks of a peak season such as BFCM, because warm-up caps sending volume while it runs.