Should you move from MC Engagement to Marketing Cloud Growth?
Data Cloud-native Marketing Cloud is the future — but only some orgs are ready today. A checklist for the migration decision.
- MC Growth wins on segmentation power, unified identity and Einstein journeys — if you already run on Data Cloud.
- It loses on scale (SMS / high-volume email) versus MC Engagement — for now.
- Migration cost is dominated by journey re-authoring, not tech.
What actually changed
MC Growth is built on Core (single object model, Flow, Data Cloud). MC Engagement is a separate stack with its own contact model. If your identity graph lives in Data Cloud, Growth removes an integration seam.
The three readiness gates
1) Data Cloud in production with unified profiles. 2) Send volumes within Growth's current envelope. 3) Willingness to re-author journeys rather than lift-and-shift.
How we phase it
Route new campaigns and new brands to Growth; leave high-volume transactional and complex existing journeys on Engagement until parity closes. Revisit quarterly.
How to make this specific, measurable and shipped.
A concrete goal shape for turning this insight into a board-defensible programme.
Migrate net-new campaign programmes for two brands to MC Growth; keep transactional on Engagement.
Time-to-launch a new journey, unique-open lift, CPL, marketing-attributed pipeline.
3-month per-brand plan with segmentation moved to Data Cloud first, journeys second.
Aligns marketing with a shared identity graph the CDO/CMO already agreed to.
Brand 1 live at month 3; brand 2 live at month 6; retire duplicate segmentation by month 9.
Put numbers on it.
An interactive model calibrated to the shape of programmes we run. Tune the inputs to your reality — the outputs recompute instantly.
MC Engagement → MC Growth value estimate
Model pipeline uplift from unified identity, faster journey launch and reduced tooling overlap.
- Identity uplift benchmark 8–18% (retail / FSI B2C).
- Excludes creative production savings from templatised journeys.
- Migration cost varies widely with journey count — validate in discovery.
- 01Do not migrate for its own sake — migrate when identity + volume gates are green.
- 02Re-author journeys, don't lift and shift.
- 03Treat Data Cloud as prerequisite, not concurrent workstream.
Pressure-test this against your org.
A Principal Architect will validate the assumptions, pull in your baselines and turn this into a defensible business case.
Book a working sessionAgentforce vs Copilots: what enterprises actually need in 2026
Copilots suggest; agents act. A field guide to picking reasoning-first agents for service, sales and RevOps — and where copilots still win.
Read →Zero-copy or full ingestion? A decision framework for Data Cloud
When to federate with Snowflake, Databricks or BigQuery, when to ingest, and how to model the FinOps consequences.
Read →CPQ+ to Revenue Lifecycle Management: a pragmatic migration path
The legacy CPQ+ and Billing footprint isn't going away tomorrow — here's how to phase RLM without breaking quote-to-cash.
Read →