Marketing Cloud Migration Checklist
A phase-by-phase checklist for migrating from another email platform to Marketing Cloud, or from Marketing Cloud Engagement to Marketing Cloud Next.
Most marketing platform migrations fail on the details nobody listed: a consent flag that did not map, a triggered email that nobody knew existed, or a sending domain that went live cold. This checklist covers two routes: moving from another email service provider (ESP) into Marketing Cloud, and moving from Marketing Cloud Engagement to Marketing Cloud Next. The phases are shared, and the table below shows where the routes differ.
Choose your route
How the two routes differ
| Question | From another ESP | Engagement to Marketing Cloud Next |
|---|---|---|
| Commercial path | Salesforce says new customers start with Marketing Cloud Growth Edition or Advanced Edition | Existing customers get Marketing Cloud Next capabilities by renewing into a "+" version, such as Engagement+ |
| Data foundation | Marketing Cloud Next runs on the core Salesforce platform and Data 360 | Data moves from data extensions and Contact Builder towards Data 360 objects |
| Consent | Export opt-in status with dates and sources from the old platform | Map existing subscriptions to the Marketing Cloud Next consent objects |
| Content | Rebuild templates; personalization syntax will differ | A third-party summary reports AMPscript reached Marketing Cloud Next personalization in Summer '26; check Help |
Confirm licences and editions with your Salesforce account team before you plan the timeline. For a deeper comparison, see Marketing Cloud Next vs Marketing Cloud Engagement.
Phase 1: Inventory
- Every active send listed: campaigns, journeys, automated programmes and transactional or triggered emails.
- Every data feed listed, with source, schedule, owner and fields.
- Every integration that calls the old platform's API identified.
- Templates, content blocks, images and landing pages catalogued, with owners deciding what to retire.
- Reporting needs captured, including any history you must keep.
Phase 2: Data and consent
- Subscriber identifier agreed before any load. In Marketing Cloud Engagement this is the Contact Key.
- Opt-in and opt-out status exported with timestamps and source. Unsubscribes must arrive before the first send.
- For Marketing Cloud Next, consent mapped to Contact Point, Communication Subscription, Engagement Channel Type, Communication Subscription Channel Type and Communication Subscription Consent. Consent is stored as Data 360 objects and checked at send time.
- Load method chosen. Salesforce documents Preference Pages, a Consent Status component, CSV Consent Imports and certain Flow types. Its Trailhead module warns against using the MessagingConsent actions.
- Retention and deletion rules agreed with your legal adviser.
Phase 3: Sending domain and reputation
- SPF, DKIM and DMARC published and passing for the new platform, as in the implementation checklist.
- One-click unsubscribe tested on commercial mail.
- A volume ramp planned, starting with engaged contacts. Gmail asks bulk senders to keep spam rates below 0.1% and never reach 0.3%.
Phase 4: Rebuild journeys and automations
- Each programme rebuilt and tested against its original logic, not just its original look.
- Engagement-based logic reviewed. Marketing Cloud Next includes Einstein Send Time Optimization, enabled per channel in Setup.
- Follow-up actions mapped. A third-party summary of the Winter '27 release notes reports completion actions arriving in Marketing Cloud Next through Flow.
- Messaging spend understood. On Engagement+ and Marketing Cloud Next, a Digital Wallet tracks messaging-credit spend for Email, SMS and WhatsApp.
Phase 5: Parallel run and cutover
- 01
Freeze changes
Stop building new programmes on the old platform once the rebuild starts.
- 02
Run in parallel
Send low-risk programmes from the new platform while the old one handles the rest.
- 03
Compare results
Check delivery, bounce, complaint and unsubscribe rates against the old platform's baseline.
- 04
Switch triggers
Repoint forms, APIs and transactional sends, one integration at a time, with a rollback plan.
- 05
Final sync
Re-export unsubscribes and bounces from the old platform on cutover day.
Phase 6: Decommission
- Historical data archived in line with your retention rules.
- Old API credentials and users disabled.
- DNS records for the old platform removed once no mail depends on them.
- Runbooks updated. The migration runbook template gives a structure for this.
Questions we hear
How long should the parallel run last?
Can we convert journeys automatically from another ESP?
Do we need Data 360 for Marketing Cloud Next?
Related reading
Marketing Cloud migration services
How we scope and run a migration
→Migrating from a legacy ESP
The solution blueprint for ESP moves
→Moving to Marketing Cloud Next
Planning the move from Engagement
→Consent in Marketing Cloud Next
Designing subscriptions and consent
→Sources
- https://salesforce.com/blog/marketing-cloud-next-details/
- https://trailhead.salesforce.com/content/learn/modules/consent-management-fundamentals-for-marketing-cloud-next/explore-consent-tools-and-concepts
- https://trailhead.salesforce.com/content/learn/modules/ai-in-marketing-cloud-next/boost-your-marketing-campaigns-with-einstein
- https://support.google.com/mail/answer/14229414?rd=1
Planning a migration?
We can build your inventory, map data and consent, and run the parallel sends and cutover with your team.
