
Introduction
Marketing teams keep asking us the same thing about Marketing Cloud Next (MC Next): move now, or wait until it can do everything Account Engagement (formerly Pardot) or Marketing Cloud Engagement (SFMC) does today?
Both options assume a migration, and you may not need one yet. MC Next may already be in your Salesforce contract, it runs alongside your current platform, and nothing is forcing the move: Salesforce says it has no end-of-life, end-of-sale or end-of-roadmap plans for Engagement or Account Engagement.
So we’d ask a smaller question: which campaign goes first? Choose one whose cost you can estimate, whose audience has consented, and whose result the business will care about. Everything else stays where it is until there’s a good reason to move it.
What a first project can look like
A B2B company on Account Engagement could run one lead capture campaign in MC Next: a form collects new leads, a flow runs the welcome or qualification steps, and sales sees the results. Its Engagement Studio nurture programmes stay untouched.
A B2C company on Marketing Cloud Engagement could build its next welcome journey in MC Next for a small audience that has given consent. Everything else, such as renewal reminders and transactional messages like order confirmations, stays in Journey Builder, and journeys that are already running are completed there.
Salesforce’s own guidance for Account Engagement customers points the same way: start capturing consent in MC Next for « a specific, isolated campaign or journey ». It also advises against sending marketing communications to the same records from both platforms simultaneously, so we’d give each audience a single home during a pilot. Not every preference syncs between the two, so the same person could get a campaign twice, or an email from a list they already left.
Four Questions to Answer Before You Start
Before launching your first MC Next campaign, consider four questions:
1. What result are you after?
Pick one measure, such as qualified leads passed to sales or campaign preparation time, and record today’s figure.
2. Who is in the audience, and have they agreed to hear from you on this channel?
Define the audience precisely, then confirm that each contact has consented to the channel you plan to use and that this consent is recorded in MC Next. A contact without the right consent record won’t receive anything.
3. What will it cost?
MC Next is priced on consumption, so estimate the credits you’ll need.
4. Who runs the journey once it’s live?
That person gets hands-on experience of Flow and Data 360 before any bigger move.
If you can’t answer these yet, finding the answers is your first project.
Check what your contract already includes
Before investing in a new implementation, check what your existing Salesforce contract already includes.
Depending on your current Marketing Cloud product and edition, you may already have access to MC Next.
| Your current product | MC Next edition | Availability |
| Account Engagement Growth | Growth | Already included |
| Account Engagement Plus, Advanced or Premium | Advanced | Already included |
| Marketing Cloud Engagement Pro | Growth | When renewing as Pro+ |
| Marketing Cloud Engagement Corporate or Enterprise | Advanced | When renewing as Corporate+ or Enterprise+ |
Account Engagement customers get Growth or Advanced through permission set licences, with no new SKU to buy, according to Salesforce’s FAQ. Older editions whose names end in -LP may not qualify, so check your contract.
Check your Salesforce edition too: the Winter ’27 release notes typically limit MC Next features to Enterprise and Unlimited editions with the Salesforce Foundations add-on. Account Engagement customers can enable Foundations at no cost, which includes Data 360 and some messaging and Einstein credits. Anything beyond that allowance requires additional purchases.
What you gain and what changes
MC Next runs inside your Salesforce org on top of Data 360, as one part of the wider Agentforce Marketing family. Marketing, sales and service work from the same data: engagement from email and SMS comes back into Data 360, and a change on a CRM record, such as an opportunity moving to a new stage, can start a journey. Much of Salesforce’s newest marketing work lands here too, such as agentic campaigns, which need Advanced-level access.
Engagement users will see the bigger change: there’s no separate tenant, audiences are Data 360 segments or actionable lists of specific leads or contacts, journeys are built in Flow, and consent sits in standard Salesforce objects.
Account Engagement users will find it more familiar, but prospects don’t always have a matching lead or contact record, Engagement Studio programmes give way to flows, and most segmentation moves to Data 360.
Get your data, consent and sending ready
Segments and much of the personalisation draw on the unified profile in Data 360, so any gap there shows up in every journey, as we argued when MC Next launched.
Consent usually takes the most work, because a contact without the right consent record for a channel won’t receive anything. The models also differ:
- Engagement holds email consent per subscriber key, so two subscribers sharing an address can have different preferences. MC Next manages it per subscription on the contact point, so existing lists need mapping to communication subscriptions.
- Account Engagement has an overall opt-out as well as public lists. Salesforce’s consent matching carries over the opt-out but not the list preferences.
Before the first real send, test what happens when someone unsubscribes or changes a preference on either platform, including people who share an email address. For European companies, this is also a GDPR matter, so involve your data protection officer from the start of the project.
Engagement customers can reuse their sending domains, but the emails go out from different IP addresses, so plan a gradual ramp-up and check your email authentication first.
Sort your use cases: what moves now and what stays
Your first campaign is not the only way to start. Reporting can move before it, or alongside it, because it changes nothing for live journeys. Data 360 connectors import engagement data from Engagement and Account Engagement, so you can analyse the results of your current campaigns alongside your sales pipeline while those campaigns keep running on your current platform. Check your licences first: B2B Analytics for Marketers needs Advanced-level access.
This is how we’d sort the rest:
| Can start now | Review first | Keep where it is for now |
| New, simple journeys | Emails with complex AMPscript | Services built on server-side JavaScript |
| Basic lead capture | Advanced forms | CloudPages code resources and custom endpoints |
| Reporting your licences cover | Existing subscription models | Complex legacy integrations |
This classification will vary depending on your own setup. Bear in mind that leaving an existing use case on your current platform does not settle where new developments should be built: each new service built on server-side JavaScript is one more component to rebuild if you migrate later.
Recheck last year’s objections
Salesforce added or changed entries in its MC Next Winter ’27 release notes every week from 30 August to 26 October 2026.
At that pace, a gap you found six months ago may be closed today. Here’s where six objections stand in November 2026:
| The objection | Where it stands |
| No AMPscript | In email since Summer ’26, with row lookups added in Winter ’27. Functions that write to a data extension, such as InsertDE, aren’t supported |
| No completion actions | Available in flows since August 2026. |
| Our data lives in data extensions | Engagement+ customers can import one into a marketing object. It’s a one-time copy, so later changes don’t sync |
| No progressive profiling | Back since late September 2026, with limits on the fields its rules can use |
| No AMPscript on landing pages | Announced for Winter ’27, then removed from the notes on 12 October because the features « aren’t quite ready yet » |
| No server-side JavaScript or CloudPages code resources | Still no equivalent, including for custom API endpoints. Expect a rebuild in Flow or Apex |
Announced features can slip, as the landing pages did, so plan around what’s already in your org. To keep track, use the release you may use notes and Nobuyuki Watanabe’s posts on LinkedIn and in his SFMC Tips series, which we find the quickest way to keep up.
Start with one campaign
Bring us one candidate campaign and an outline of your current setup. Our certified MC Next consultants will guide you through the four areas that determine whether a pilot succeeds: licences, Data 360 readiness, consent model and technical dependencies. You’ll come away with a clear recommendation, pilot now or prepare first, and the next steps in either case. Get in touch with our team to set that up, or see our wider Marketing Accelerator.
Licensing and product details verified November 2026.
Author: Enrique Martinez, Senior Consultant, asUgo



