Marketing Cloud Next: MC Engagement Convergence - Learning Path
Summary: The goal of this path is to help you get the most out of using both Marketing Cloud Engagement anf Agentforce Marketing (MC Next) together, which can also be a first step toward a migration. This Learning is a Work In Progress
In this Learning Path
- What you’ll learn
- The shared foundations of marketing across MCE and MCN: data, segmentation, activation, and journeys
- The relationship between MCE data structures (Data Extensions, Contact Builder) and Data 360 concepts (DMOs, Unified Individuals)
- The differences and overlaps between MCE segmentation and MCN segments and activations
- How journey orchestration in MCE (Journey Builder) compares to Flows and event-driven logic in MCN
- The evolution from channel-based execution in MCE to modular, flexible activation patterns in MCN
- A capability-first mindset to navigate both platforms without thinking in silos
- Why it matters
- Reuse what you already know from MCE instead of starting from scratch
- Understand what actually changes with MCN, and what doesn’t
- Move faster when transitioning to Data 360 and on-core marketing
- Design marketing strategies that work across both platforms
- Avoid siloed thinking between “old” and “new” architectures
- Collaborate more effectively with teams working in different environments
Step 1 of 1 – From Journeys to Flows: understanding the shift
This is an introduction to how orchestration evolves from Journey Builder to Flow in Marketing Cloud Next. See how entry sources, decision splits, wait activities, and channel actions translate into event-driven logic, Flow nodes, and activation steps on Core.Read: Journey Builder vs Flow
Next: Evaluate if the Convergence approach is best for you.