Leaving Salesforce Marketing Cloud Engagement
A Migration Readiness Assessment for Marketing Ops, Data Engineering, and Deliverability Teams
Salesforce isn’t retiring Marketing Cloud Engagement, but its own guidance points toward Marketing Cloud Next, a different product on a different platform. So the question isn’t whether to re-architect. It’s where.
This technical assessment shows what transfers cleanly, what has to be rebuilt, what can’t be recovered once it ages out, and where migrated journeys quietly behave differently.
Table of Contents
Executive summary
The question is not whether to re-architect. It is where.
If you are reading this, someone has asked whether leaving Marketing Cloud Engagement is realistic. The honest answer depends less on your appetite for change than on five facts, all of which come from Salesforce.
What is true today
Salesforce is not retiring Marketing Cloud Engagement. Its pricing FAQ states there are no End-of-Life, End-of-Sale, or End-of-Roadmap plans, and Engagement received feature updates in the Summer ’26 release. We take that at face value, and this document does not argue otherwise.
Salesforce’s own guidance is to run Marketing Cloud Next alongside Engagement, not to migrate onto it. Its Trailhead module frames the model as “keep what works and add what’s next,” with Engagement retaining high-volume messaging.
Marketing Cloud Next is a different product on a different platform. It is available in Growth and Advanced editions, requires Salesforce Enterprise or Unlimited, and is assembled from Data 360, Experience Cloud, Flow Builder, and Agentforce. Enabling Data 360 is a documented prerequisite, including identity resolution rulesets and data kits.
Therefore adopting Next is itself a re-architecture. Your data model moves to Data 360, your orchestration moves to Flow, and your content moves to Handlebars. Those are the same three workstreams as any platform change.
One constraint runs on a clock you do not control. Since 16 June 2025, Salesforce retains engagement data for 730 days, after which it is inaccessible through the UI, reports, and the API. For contracts signed on or after 10 April 2024 the data is deleted. Salesforce’s published remediation is to configure automated extracts and store the data outside Marketing Cloud.
THE CONSEQUENCE
If you are going to rebuild your data model, orchestration, and content either way, the switching cost to a different vendor is no longer meaningfully higher than the switching cost to Salesforce’s own next generation product. That is the real decision on the table, and it is worth making deliberately rather than by default.
Thinking about leaving Salesforce Marketing Cloud?
Migrating doesn’t have to mean starting from scratch. Get a clear picture of what it takes to move off Salesforce Marketing Cloud Engagement, including data migration considerations, technical requirements, and potential risks.
Download our free migration readiness assessment and checklist to plan your next move with confidence below.