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

  • Your contract is up and the name changed.

    Emarsys is now SAP Engagement Cloud, and renewal is a good moment to ask whether an enterprise suite is the right fit for a Shopify brand.

  • Every change goes through a specialist.

    Programs, ESL snippets, Smart Insight feeds and Web Extend all work, but only one or two people know how to change them safely.

  • You want email and SMS to run off the store.

    You want flows that trigger on Shopify behavior, apps that write to the same profile, and a team that improves the program every month.

Should you migrate from SAP Emarsys to Klaviyo?

Yes, if you are a Shopify brand and most of your revenue runs through the store, if your marketing team wants to build and change flows without a specialist, or if you want subscription, loyalty and review apps feeding the same customer profile as your email and SMS.

Maybe not, if your business runs on the SAP stack, with SAP Commerce Cloud or other SAP systems feeding Emarsys, and a team that maintains those connections. That is the setup Emarsys is built for, and the switching cost is higher.

And no, if the real problem is results. A thin welcome series and one cart reminder will underperform on any platform. We would rather tell you that on the first call than after an eight week migration.

Is SAP Emarsys the same as SAP Engagement Cloud?

Yes. On February 19, 2026, SAP renamed the SAP Emarsys solution to SAP Engagement Cloud and launched an enterprise edition with extra administration and governance controls for multi-brand, multi-region teams. SAP says existing Emarsys capabilities remain available inside SAP Engagement Cloud.

For a migration, nothing changes. The contact database, programs, Smart Insight, Web Extend, Loyalty and ESL work the way they did, so everything on this page applies whichever name is on your invoice.

What is the difference between SAP Emarsys and Klaviyo?

SAP Emarsys is an enterprise omnichannel platform. Contacts live in a field-based database with numbered fields, purchase data arrives through Smart Insight sales files, browsing comes from the Web Extend script, programs run journeys across email, SMS, push and web channel, and ESL handles advanced personalization. It is built to connect to large enterprise systems, and it usually needs a specialist to run.

Klaviyo is built around the store. For a Shopify brand, Viewed Product, Added to Cart, Started Checkout, Placed Order and Fulfilled Order arrive straight from Shopify with product, value and category attached, the catalog syncs automatically, and order history is there on day one. Segments update in real time, and apps like Recharge, Skio, Okendo, Yotpo and LoyaltyLion write onto the same profile.

The practical difference: in Emarsys, a new journey often depends on a sales file, an external event or a custom field being set up first. In Klaviyo, the marketer builds most flows from Shopify events the same afternoon.

How do you export your data from SAP Emarsys?

Contacts come out of the Emarsys contact database by list or segment, through the interface or the API, with the fields you choose. The external contact ID, usually your customer ID or email, is the key that keeps every record matched.

Most of the rest does not need to come from Emarsys at all. Purchase history lives in Shopify, so Klaviyo re-syncs it directly instead of rebuilding it from Smart Insight sales files. The product catalog syncs from Shopify too. Browsing data from Web Extend is replaced by Klaviyo's onsite tracking, which starts collecting the day it is installed.

What does need careful export: opt-in fields, any custom fields customers filled in themselves, loyalty balances and tiers, and the list of who is suppressed.

What happens to Emarsys Loyalty and vouchers?

If you run Emarsys Loyalty, members, points and tiers have to land somewhere before Emarsys is switched off. Usually that is a Shopify loyalty app that syncs to Klaviyo, chosen in the audit, with balances imported so nobody loses points.

Order matters here. Emarsys notes that deleting a contact also removes their Loyalty rewards and Smart Insight purchase history. So nothing in Emarsys gets cleaned up, merged or deleted until loyalty balances are exported and checked.

Vouchers move to Klaviyo coupon codes synced from Shopify, so every unique code in a flow is a real, redeemable Shopify discount.

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.

What transfers from SAP Emarsys to Klaviyo and what has to be rebuilt
Moves over Has to be rebuilt
Contacts with external ID, email and phoneEvery program, rebuilt as a Klaviyo flow
Email and SMS opt-in status, mapped to Klaviyo consentESL personalization, rewritten in Klaviyo's template tags
False opt-ins and unsubscribes, uploaded as suppressionsSegments, rebuilt on Shopify events and Klaviyo properties
Custom fields customers filled in, as profile propertiesExternal events, replaced by Shopify events wherever possible
Loyalty members, points and tiers, into your loyalty appPredict recommendations, rebuilt on Klaviyo product feeds
Order history, re-synced from Shopify rather than Smart InsightSignup forms and web channel campaigns, rebuilt as Klaviyo forms
SMS subscribers with consent, and a dedicated number by portingVouchers, 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.

How SAP Emarsys features map to Klaviyo equivalents
SAP Emarsys Klaviyo equivalentWhat changes
Interactions and Automation Center programsFlowsTriggered by Shopify events wherever possible, with branches your marketing team can edit.
Contact fieldsProfile propertiesKeep what customers told you. Retire fields that only mirrored order data.
Opt-in field and SMS opt-inEmail and SMS consentFalse and empty never come across as subscribed.
Smart Insight sales dataShopify order syncOrder history arrives from Shopify, with no daily sales file to maintain.
Web ExtendKlaviyo onsite trackingViewed Product and Active on Site start tracking the day it is installed.
External eventsShopify events or custom metricsMost commerce triggers come from Shopify natively. Keep custom events only where Shopify has no equivalent.
SegmentsSegmentsRebuilt on Klaviyo events and properties. Membership updates in real time.
ESL and relational dataTemplate tags and universal contentEvery condition, loop and fallback is rewritten and tested on real profiles.
Predict recommendationsKlaviyo product feedsRebuilt on purchase and browse data from Shopify.
LoyaltyShopify loyalty app synced to KlaviyoMembers, points and tiers imported before Emarsys is switched off.
Web channelKlaviyo signup formsTargeted by page, behavior and source, A/B tested, and feeding consent straight onto the profile.
SMS and pushKlaviyo SMS and pushSubscribers move with consent. Dedicated numbers can usually be ported.

What is the most common SAP Emarsys to Klaviyo migration mistake?

Importing everyone with an email address as subscribed.

The Emarsys contact database holds far more people than the marketing list: buyers who only got order confirmations, people added by integrations, contacts whose opt-in was never set. Treat the whole database as subscribed and you email people who never agreed to it, and deliverability pays for it in the first week.

The second mistake is deleting or merging contacts in Emarsys to tidy up before the export. That can wipe Loyalty rewards and purchase history you still need.

The third is rebuilding Smart Insight. Brands spend weeks recreating sales files and revenue fields that Klaviyo gets from Shopify for free.

How does Sticky Digital run a SAP Emarsys to Klaviyo migration?

  1. 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. 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. 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. 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.

  • Opt-in mapped field by field.

    Email and SMS opt-in are carried over exactly, so nobody who said no is emailed and nobody who said yes is lost.

  • Loyalty lands safely.

    Points, tiers and members are exported and checked before anything in Emarsys is touched.

  • Eight weeks, not a quarter.

    Audit to cutover in eight weeks or less, with the stages overlapping, so you are not paying for two platforms for months.

  • A Klaviyo Platinum Partner with brands you know.

    Retention specialists since 2019 for brands like Murad, U Beauty and ZO Skin. Our clients usually see 25% to 40% of store revenue coming from email within six months.

How we price SAP Emarsys to Klaviyo migrations

Sticky Digital migrations to Klaviyo cost $0 to $25,000, depending on account size and the discount we are able to offer, and some brands qualify for a free migration. Emarsys accounts with many programs, Loyalty, heavy ESL or channels beyond email and SMS sit toward the higher end; a store-first program with a handful of programs sits toward the lower end.

Tell us what you are moving and we will tell you where you land.

Can you migrate from SAP Emarsys to Klaviyo yourself?

Sometimes, yes.

When a DIY SAP Emarsys migration is reasonable and when to bring in an agency
DIY is reasonable when Bring in an agency when
Under 25,000 contactsOver 50,000 contacts, or a database far larger than the opted-in list
Email opt-in onlyEmail and SMS opt-in, plus contacts with an empty opt-in
A handful of simple programsMany programs on external events, relational data or Predict
Little ESLHeavy ESL and dynamic content
No Emarsys LoyaltyLoyalty members, points and tiers to move
No peak season or renewal within twelve weeksBFCM, 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

We work with DTC brands on Shopify, primarily beauty, wellness, food and beverage, and apparel.

If your commerce, service and data all run on SAP and Emarsys is wired into those systems, staying may be the better call, and we will tell you so. We are retention only: no paid media, no SEO, no commerce platform builds, and no brand design.

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.

Get your SAP Emarsys migration scoped

Send us your Emarsys renewal date and a rough picture of your program: programs, opt-in setup, whether you run Loyalty, and which channels beyond email and SMS you use. We will tell you whether migrating is the right move, map an eight week plan that lands before the renewal, and show you what it costs. If the answer is that your program needs work rather than a new platform, we will tell you that instead.