Marketing Cloud Next Migration: Start Small, Move Faster

Almost every marketing leader running Marketing Cloud Engagement, Account Engagement (formerly Pardot), or both, is being asked some version of the same question: what's our move? Salesforce's roadmap is now firmly anchored to Marketing Cloud Next, the on-core suite that brings marketing onto the same Salesforce platform as Sales, Service, and Data Cloud. Most teams understand the direction. What they're wrestling with is the size and shape of the first step. The default instinct is the one that has worked for previous platform shifts: scope a multi-quarter migration, rebuild journeys, retrain the team, cut over, breathe. Our experience suggests this is the most expensive way to make the move, and often the slowest path to actual value. Here's why.

Marketing Cloud Next is a different model, not a new version

The packaging makes Marketing Cloud Next look like a successor product. The architecture tells a different story. Legacy Marketing Cloud was built around its own data model, batch synchronisation, and channel-specific tools. Account Engagement sat alongside it with a separate prospect database and Engagement Studio for automation. The marketing team's data lived inside marketing systems, with periodic syncs back to the CRM. Marketing Cloud Next inverts that. The data layer is Data Cloud, sitting on the Salesforce core. Identity resolution, calculated insights, and segmentation happen in real time against a unified customer profile. Orchestration moves from Journey Builder and Engagement Studio into Flow, the same automation engine that runs the rest of the Salesforce platform. The practical implication for a marketing leader is this: the patterns optimised over years of running MCE or MCAE don't translate one-to-one. Some assets carry over. The operating model behind them needs to be rebuilt.

The lift-and-shift trap

The most expensive version of this migration is the one that tries hardest to preserve continuity. Rebuilding every existing journey, recreating every list, importing every template, retraining the team to do the same things in different tools. Two problems with this approach.First, the entire program cost goes into reproducing what already exists, with limited new capability to show for it at the end. The business case becomes hard to defend halfway through. Second, the actual benefit gets deferred. Real-time segmentation, unified profiles, cross-cloud orchestration: these are not features that switch on at the end of a migration. They are capabilities that require the team to operate differently. A faithful lift-and-shift rebuilds the old way of working on the new platform, and then asks the team to change everything anyway, once the project is done. The leaders making this look easy treat the move as a learning program, not a re-platforming project.

A different shape: crawl, walk, run

A more useful framing is to size the first move based on starting point and risk appetite, then expand from there. For teams with significant investment in legacy MCE or MCAE, a crawl phase of around four weeks runs Marketing Cloud Next alongside the existing platform. Data Cloud is connected, one or two segments and Flow-based orchestrations are stood up, and the team builds confidence with the new model without migrating any production journeys yet. The legacy platform keeps sending. Next handles the first new patterns. For teams ready to commit to a working baseline, a walk MVP delivers a functional implementation in six to eight weeks for an email-first program, or twelve to fourteen weeks for a multi-channel, data-richer build. Both include Data Cloud as the data layer, a focused set of segments and journeys, and the operating disciplines (consent, governance, monitoring, enablement) that make the new model sustainable. The run phase, with full migration, multiple brands, advanced personalization, and marketing intelligence dashboards, comes later, with the benefit of having operated the new model for a quarter or two first.

What progress looks like

The shift in mindset that makes this work is replacing "migration completion" with "operational learning" as the measure of progress. In a crawl, the unit of progress is one segment built natively in Data Cloud, one Flow replacing one legacy automation, and a team that now understands what real-time segmentation actually changes about how they brief campaigns. In a walk MVP, the unit of progress is a working end-to-end pattern: CRM data flowing into Data Cloud, calculated insights driving segmentation, a journey running in Flow, and a team that can maintain it without depending on the implementation partner.This is a smaller deliverable than a full re-platform. It is also a far better foundation for the next phase, because the patterns being expanded are ones the team has already used in production.

Starting small is the fast path

The reason marketing leaders end up in multi-year migration projects is rarely because the move itself requires it. It's because the wrong question gets asked at the start: how do we move everything? rather than what's the smallest move that lets us learn the new model and build from there? Marketing Cloud Next rewards the second question. Treat it as a different operating model, not a new version of the old one, and the path forward gets considerably shorter. A note on timelines: the four-to-fourteen week ranges in this article reflect typical implementation shapes. Actual timing and scope depend on your existing platform footprint, data quality, integration complexity, governance requirements, and the business outcomes you're optimizing for. The intent of the crawl, walk, run framing is to size the first move to the situation, not to prescribe a fixed path. If you're weighing your move from Marketing Cloud Engagement or Account Engagement to Marketing Cloud Next, contact OSF Digital to talk through what your first phase could look like.

Author: David Spelman

David Spelman is a Senior Marketing Cloud Consultant in OSF Digital's UKI team and a 3x Salesforce certified marketing professional (Marketing Cloud Consultant, Email Specialist, Administrator). With over 20 years in digital marketing and 7+ years working hands-on with Salesforce Marketing Cloud across financial services, healthcare, and B2B sectors, David specializes in CRM, email automation, audience segmentation, and the architectural shift from legacy Marketing Cloud Engagement and Account Engagement (Pardot) to Marketing Cloud Next on the Salesforce core.