Migrating from Salesforce Marketing Cloud to Klaviyo is a rebuild of your data model, not just your automations. Subscribers and their status sync through Klaviyo's Salesforce Marketing Cloud integration, which can also import opens and clicks from the last 180 days. Data extensions become Klaviyo profile properties and events, Journey Builder journeys become flows, and AMPscript is rewritten, because Klaviyo does not run a live database lookup in the middle of a send. Sticky Digital runs the whole migration in eight weeks or less and plans it backward from your Salesforce renewal date.
Salesforce Marketing Cloud 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 Salesforce Marketing Cloud programs to Klaviyo in eight weeks or less, turn developer-run journeys into flows your marketing team can run, 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 Salesforce Marketing Cloud to Klaviyo?
How much does Salesforce Marketing Cloud cost compared with Klaviyo?
What is the difference between Salesforce Marketing Cloud and Klaviyo?
What transfers from Salesforce Marketing Cloud to Klaviyo, and what has to be rebuilt?
Klaviyo's Salesforce Marketing Cloud integration syncs your lists and their subscribers and can import open and click history for campaigns sent in the last 180 days. Everything that depends on data extensions, AMPscript or Journey Builder logic is rebuilt.
| Moves over | Has to be rebuilt |
|---|---|
| Subscribers and lists, through Klaviyo's integration | Every Journey Builder journey, rebuilt as a Klaviyo flow |
| Bounced and Held contacts, globally suppressed from email in Klaviyo | Data extension joins, rebuilt as profile properties and events |
| Unsubscribed and Deleted contacts, unsubscribed under your Klaviyo settings | AMPscript and SSJS personalization, rewritten in Klaviyo's template tags |
| Opens, clicks and receives from the last 180 days, if you choose to import them | Automation Studio SQL queries, replaced by Klaviyo segments |
| SMS subscribers with consent timestamps, and a dedicated short code or toll-free number by porting | Content Builder templates and content blocks, rebuilt as Klaviyo templates |
| Order history, re-synced from Shopify rather than exported from Salesforce | Transactional and triggered sends, inventoried and rebuilt before anything else |
Reconcile the counts before any flow goes live. The integration syncs Clicked Email, Opened Email and Received Email, and nothing about purchases, so order history has to come from your Shopify connection. Contacts that live only in a data extension, outside the synced lists, are exported and imported separately.
How do Salesforce Marketing Cloud features map to Klaviyo?
The table most Marketing Cloud migrations skip. Porting journeys step for step is how you end up on a new platform running the old program.
| Salesforce Marketing Cloud | Klaviyo equivalent | What changes |
|---|---|---|
| Data extensions | Profile properties and custom events | Each join is redesigned as data that already sits on the profile, synced ahead of the send. |
| Journey Builder | Flows | Triggered by Shopify events wherever possible, with branches your marketing team can edit. |
| Automation Studio SQL queries | Segments | Built with conditions instead of SQL. Membership updates in real time. |
| AMPscript and SSJS | Template tags and dynamic blocks | No live lookups mid-send. The data each block needs is on the profile first. |
| Content Builder | Templates and universal content | Shared blocks are rebuilt once and reused across flows and campaigns. |
| Publication lists | Lists plus email and SMS consent | Consent sits on the profile per channel. Lists hold source and opt-in. |
| Auto-suppression lists | Suppressions | Imported and checked before the first send. |
| MobileConnect | Klaviyo SMS | Dedicated short codes and toll-free numbers port. Subscribers move with consent timestamps. |
| Triggered and transactional sends | Shopify-triggered flows | Order and shipping messages are mapped first, because customers notice when they stop. |
| Einstein send time and engagement scoring | Smart Send Time and predictive analytics | Predictions are built from order history, such as predicted next order date and CLV. |
| Business units | Separate Klaviyo accounts or one structured account | Decided in the audit, based on brands, regions and who runs each program. |
| Sales Cloud and data warehouse events | Custom events through Klaviyo's API | Only the events a flow actually needs are piped in. |
What is the most common Salesforce Marketing Cloud to Klaviyo migration mistake?
What should you leave behind in Salesforce Marketing Cloud?
How does Sticky Digital run a Salesforce Marketing Cloud to Klaviyo migration?
-
1. Week 1: Audit, starting from your renewal date. We get your contract end date and non-renewal notice deadline from your Salesforce team, then map every data extension, journey, automation, AMPscript block and transactional send, and which ones sent in the last 90 days. That decides what gets rebuilt, what gets retired, and the order of work. If you are keeping a short code, the port request goes in this week.
-
2. Weeks 1 to 2: Data, consent and infrastructure. Klaviyo's integration syncs your lists and statuses, with Bounced and Held contacts suppressed and unsubscribes carried over. We reconcile the counts, design the profile properties and events that replace your data extension joins, connect Shopify, authenticate your sending domain with SPF, DKIM and DMARC, and build the account architecture before a single flow goes in.
-
3. Weeks 2 to 4: Transactional sends, then flows. Transactional and triggered sends move first, because customers notice when an order email stops. Then revenue journeys are rebuilt as Klaviyo flows on Shopify events, highest earning first, with AMPscript personalization rewritten and tested on real profiles.
-
4. Weeks 3 to 8: Warm-up and cutover. Campaigns start with subscribers who opened or clicked in the last 30 days, which is also how Klaviyo's own Salesforce migration guide begins, and widen in stages while complaint and bounce rates are checked daily. Campaigns move last, and if a major sale falls in the window, they stay in Salesforce until it is over.
Eight weeks at most, end to end, because the stages overlap instead of waiting on each other. Klaviyo itself does not recommend running both platforms past the switch, and every month of overlap is a month you pay for both. Work backward from your renewal date, not forward from today.
What does this look like in practice?
How we price Salesforce Marketing Cloud to Klaviyo migrations
Can you migrate from Salesforce Marketing Cloud to Klaviyo yourself?
Sometimes, yes.
| DIY is reasonable when | Bring in an agency when |
|---|---|
| A few lists and simple journeys | Many data extensions joined at send time |
| Little or no AMPscript | AMPscript or SSJS across your key emails |
| One business unit and one brand | Several business units, brands or regions |
| Email only | MobileConnect SMS with a short code to port |
| Someone on staff who understands the current build | The person who built it has left |
| No peak season or renewal within twelve weeks | BFCM, a launch or your Salesforce renewal within twelve weeks |
The risk in a DIY Marketing Cloud migration is almost never the subscriber sync. It is the data extension joins, the AMPscript, the transactional sends nobody inventoried, and the warm-up judgment calls.
Who this is not for
Salesforce Marketing Cloud to Klaviyo migration FAQ
Sticky Digital completes Salesforce Marketing Cloud to Klaviyo migrations in eight weeks or less. The audit takes about a week, data and consent move in the first two weeks, transactional sends and flows are rebuilt over two to three weeks, and the 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 Marketing Cloud until it lands.
Yes. Klaviyo's Salesforce Marketing Cloud integration syncs your lists and subscribers, globally suppresses Bounced and Held contacts, carries over Unsubscribed and Deleted statuses, and can import opens and clicks for campaigns sent in the last 180 days.
They do not move as tables. Klaviyo stores data on the profile and as events, so each data extension is reviewed for what it actually does, then rebuilt as profile properties, custom events or segments. Order history comes from Shopify instead.
No. Klaviyo uses its own template tags and cannot run a database lookup while an email renders. Every AMPscript block is rewritten so the data it needs is already on the profile before the email sends.
Yes, as Klaviyo flows. Journeys triggered by ecommerce behavior map directly to Shopify events. Journeys triggered by Sales Cloud or warehouse events need those events sent into Klaviyo through its API first.
Salesforce lists Marketing Cloud Engagement at $2,000 a month for Pro+, $5,500 for Corporate+ and $30,000 for Enterprise+, per org and billed annually, with 15,000, 45,000 and 500,000 included contacts. It marks those prices as subject to change and sends quotes through sales.
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.
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 timestamps.
It can, if warm-up is handled badly. Sending starts with subscribers who opened or clicked in the last 30 days and widens in stages while complaint and bounce rates are watched daily. Marketing Cloud stays live only as long as the switch needs.
Work backward from your Salesforce contract end date and notice deadline. If your renewal is a quarter or more away, there is time to rebuild properly. If it is closer, cut the scope, not the testing, and keep campaigns out of any window that overlaps a major sale.