Marketing Cloud Next: A First-Project Readiness Checklist

Marketing Cloud Next is built on the Salesforce platform with Data Cloud — now presented as Data 360 — as its data foundation, and Flow as its automation engine. That single sentence decides most of what readiness means. You are not migrating a tool. You are moving marketing execution onto the platform your CRM already lives on.

Confirm the data foundation first

Segments and journeys read from unified data. If your customer data is not yet ingested, mapped and resolved into a unified individual, nothing downstream will behave the way the demo did. This is the work, and it is not marketing work.

Confirm identity

• Which source systems contribute profiles.
• What the match rules are, and who signed them off.
• How consent survives a merge.
• What the unified individual is keyed on when you activate.

Confirm channel scope

Check the channels you need against current documentation for the release you will actually be on, not against a keynote. Capability moves quickly here, and "it is on the roadmap" is not a plan you can staff.

Confirm the team

The skill profile shifts. Less AMPscript and SQL activity chaining, more Flow, more platform data modelling, more admin-adjacent thinking. If your team's strength is deep Engagement development, plan the learning curve explicitly rather than hoping it transfers.

Confirm the exit criteria

Write down what "done" means for the first project, and keep it small: one audience, one journey, one channel, measured. First projects that try to prove the whole platform tend to prove nothing.

Checked against current Salesforce Help, Trailhead and developer documentation for Marketing Cloud Next. Product capability changes by release — verify against the official docs for your release before committing.