Migration is a significant investment, and you expect returns once the system is live. And when results don’t follow, it’s frustrating, to say the least. 

With Marketing Cloud Next, gaps may arise in several areas. For instance, teams might not use available features, workflows may remain outdated, or campaign data and configuration may not leverage the platform’s capabilities. Maximizing value often requires updating how marketing activities are planned, executed, approved, and measured. 

But you almost certainly don’t need to re-implement the project down the line. If you’ve successfully migrated to Marketing Cloud Next, ROI is where the focus ought to be. 

When you’re not seeing the expected ROI, you need to identify where the gaps could be. 

(Salesforce now brands Marketing Cloud as Agentforce Marketing; Marketing Cloud Next is the new platform that runs on Salesforce core + Data 360.)

Why Marketing Cloud Next ROI doesn’t show up on its own after migration

Platform migration is essentially a technical process. Data is mapped, environments are established, integrations are tested, and users are provisioned. 

However, migration alone does not necessarily change how a campaign gets briefed, how audiences get selected, or who signs off before a journey goes live. Unless those changes are designed into the rollout, teams may continue using familiar processes. Notwithstanding access to AI-assisted capabilities, teams may still build audiences using a limited set of filters or have one person build and own the journey end to end. 

Consider data graphs, for instance. Without a clear understanding of data graphs, you may end up creating separate Flow paths and separate emails for each variation, instead of using data graph fields to personalize a single email.

Campaign briefs present a similar challenge. Before Agentforce, briefs were often treated as a formality. With Agentforce, clear objective-setting becomes an important input into campaign creation. Teams can still skip that step if the brief is treated as paperwork rather than as the context the agent needs to produce useful output. 

Marketing Cloud Engagement vs. Marketing Cloud Next consent management

Consent is another area where a migration can create operational gaps.  

As you know, in Marketing Cloud Engagement, email consent sits on the subscriber record. In Marketing Cloud Next, consent is tied to each contact point—the specific email address or phone number—and to each communication subscription, such as a newsletter. This difference matters when teams migrate their consent model, as assumptions about how consent is stored and applied can lead to shrinking audiences, with contacts silently excluded from sends. This is usually a consent-mapping gap from the migration, or teams not knowing how consent is now structured.

These issues often appear to be platform errors but aren’t. 

Part of why these habits and issues crop up is that a migration does not necessarily require teams to change them. Generally, organizations layer the new capability onto existing workflows rather than making a hard cutover, which does help manage migration risk. But it also lets teams keep working as they always have. 

3 underused Marketing Cloud Next capabilities that drive post-migration ROI

1. Campaign griefs

In Marketing Cloud Next, you can automate and co-create campaign briefs using Agentforce, turning strategy documents into execution-ready campaign assets in minutes. The platform manages the mechanical setup, including creating the campaign, the brief, draft emails, and a draft flow, which previously consumed significant time each cycle. 

Now, you can generate a campaign brief and the initial content from a prompt. You can review the brief and approve it. 

However, a stronger way to generate the brief is to ground the prompt in these inputs: 

• Brand: Select your brand on the brief so the agent applies your tone, colours and styles. 
• Goals: Define the business outcome the campaign is intended to drive, such as order revenue, form fills, or closed opportunities.
• KPIs: Specify the metrics that will determine whether the campaign is delivering against its goal.
• Priority: Set how important the campaign is relative to other campaigns competing for the same customer’s attention.
• Guardrails: Establish the boundaries the campaign must stay within, such as no discount language, mandatory legal disclaimers, topics or claims to avoid.

Key Message, Target Audience and Primary CTA also affect the output. Grounding the prompt in these specific inputs gives the tool clearer criteria to work from. 

2. Audience selection

One might still build an audience by selecting recent buyers, filtering by region, and using Einstein Segment Creation only to generate the list quicker than the segment builder. 

However, you can approach audience selection differently. 

Instead of hand-picking filters, describe the campaign’s intent and who to exclude in plain language. Agentforce translates that into segment rules using attributes from your unified data—including related data such as purchase history—and builds a draft segment for you to review. 

You review the segment in the builder, assess which attributes were used, and determine if the logic aligns with the campaign’s intent. 

You can add missing attributes, exclude inappropriate ones, or refine the prompt.

3. Journey triggers: Engagement Signals and Wait Until Event

In Marketing Cloud Next, journeys are built as flows, and a flow can start from a segment, a form submission, or a customer event. Getting the starting event right is important because it determines when and why a customer enters the journey.

Start journeys from the right event

Marketing Cloud Next provides standard customer events that can be used to start a flow. For more specific customer actions, such as a purchase or a support interaction, you can use an Engagement Signal. Engagement Signals are configured in Data 360 on an engagement-type data object and can then be used as the event that starts the journey.

The starting event should reflect the customer action the journey is designed to respond to. If the required signal has not been configured, the journey may not respond to the customer behavior that actually matters.

Wait for the right event inside the journey

Starting a journey from an event is different from waiting for an event after a customer has entered the journey. Marketing Cloud Next lets you use a Wait Until Event activity to pause the flow until a specified event occurs. Standard events include actions such as email opens, link clicks, and delivery failures.

More specific customer actions require the relevant Engagement Signal to be configured before the journey can wait for that event. There is also a timing consideration: an event does not necessarily reach the journey the moment it happens. There can be a delay of 2-15 minutes between the customer action and the flow recognizing the trigger. 

That matters when the campaign promises a rapid response. The journey needs to be designed around the platform’s event-processing behavior.

Every Wait Until Event activity also has a maximum wait time. Once that period expires, the contact takes the configured timeout path. The important consideration is what that path does next. Someone who does not click, purchase, or complete the required action should be routed to a meaningful next step once the wait expires, not simply dropped.

Without that planning, the journey can fail in at least two ways:

• It may start from the wrong event or lack the specific Engagement Signal needed to respond to the customer action that matters.
• The timeout path may end the journey or repeat a generic message without accounting for why the expected event did not occur, resulting in an unhelpful customer experience.

In both cases, trigger design is part of the problem. 

The platform can respond to much richer customer activity; only the right signals, timing expectations, and timeout paths have to be designed before the journey goes live.

When low ROI is a data problem: identity resolution and Data Graph limits

What if the core issue behind a lack of ROI is unreliable customer data?

To assess this, use identity resolution to determine the consolidation rate. Data 360’s identity resolution consolidation rate shows how many source records were merged into unified profiles. A rate far higher or lower than you’d expect for that data source is the warning sign: too high can mean different people are being merged; too low can mean duplicates aren’t being matched. 

Remember to plan carefully, as configuration changes can be costly to correct. Data Graph has a limit of 200 fields and 25 data objects per data graph. After “Save & Build”, objects and fields you added cannot be removed. Begin with only the essential fields to minimize future rework and avoid reaching the limit unexpectedly.

90-day post-migration plan for Marketing Cloud Next

You don’t need to rebuild the entire marketing operation. 

A focused 90-day program gives you enough time to understand what is configured, test the new workflow, and see whether it moves the needle.

Timeline	Focus area	Core actions	Strategic objective
Days 1–30	Audit & analysis	• Audit active Agentforce Marketing configurations against usage. • Capture baseline metrics (time-to-launch, rework rate, conversion) • Run a data and consent health check (identity resolution, consent records, data graph fields) • Meet with campaign teams to categorize features into used, abandoned, and unclear.	Map needs and identify capability gaps before configuring to minimize rework.
Days 31–60	Low-risk pilot	• Select 2–3 low-risk campaigns. • Execute full workflow: Brief → Content → Audience → Consent & audience-size check → Trigger & wait logic → Test → Pre-launch review	Establish best practices, prove the operational model, and identify issues safely.
Days 61–90	Measurement & expansion	• Compare pilot campaign performance against baseline metrics. • Scale workflows intentionally only after proving effectiveness.	Validate actual ROI and expand capability footprint with clear evidence.

Metrics to measure Marketing Cloud Next ROI

Overall engagement rate is a fairly unreliable indicator on its own, as it can fluctuate for reasons unrelated to platform usage. 

The following metrics provide a more accurate assessment:

• Time-to-launch: Focus on reducing the brief-to-live cycle without eliminating steps that help identify issues. Confirm that any administrative time saved is redirected to strategic work rather than lost.
• Engagement lift: Measure engagement lift on triggered sends compared to the scheduled sends they replace. This approach isolates the effectiveness of trigger logic, rather than attributing improvements to the platform overall. You can use Path Experiment in Flow, which splits contacts across paths and can pick the winner automatically.
• Rework: Track how often campaigns are paused, corrected, or relaunched after going live. A decrease in rework often indicates that effective review practices from the pilot phase are being maintained at scale.
• Downstream business impact: Track signals beyond marketing, such as pipeline created, orders, revenue, and retention or renewals, if and where they exist.

Duplicate records, inconsistent consent statuses, or fragmented customer profiles can undermine even a well-executed pilot. So process discipline cannot fully compensate for fundamental data-quality problems. 

Marketing Cloud Next ROI depends on the quality and connectivity of the customer data it uses for segmentation, personalization, and orchestration. 

This is usually where an external perspective is often valuable, as teams involved in a migration may struggle to identify the underlying cause of stalled campaigns. 

If results are lacking, review whether the data foundation from the previous environment is intact or requires remediation before process improvements can be effective.