Common Migration Challenges When Moving to Marketing Cloud Next

Every Account Engagement to Marketing Cloud Next migration encounters a predictable set of challenges. Teams that know what to expect can prepare for these challenges in advance. Teams that do not know tend to discover them mid-migration — at the worst possible time.

This guide covers the eight most common migration challenges, why they happen, and the specific resolution for each.

Challenge 1: Identity Resolution Over-Merging

What happens: After running identity resolution, some Unified Individuals represent two or more different people who have been incorrectly merged. This produces a profile with contradictory data: two different names, two companies, engagement history from completely different contexts.

Why it happens: The identity resolution match rules are too aggressive — typically because a fuzzy name match rule is matching people with common names and similar titles at different companies.

Resolution:

1. Review merged Unified Individuals by looking for profiles with multiple Contact Point Emails from clearly different domains
2. Identify the match rule responsible for the false merge
3. Add a negative condition to the match rule (e.g. "do not match on name if Account/Company is different")
4. Split the incorrectly merged Unified Individuals manually in the Data Cloud admin interface
5. Re-run identity resolution validation

[Screenshot: Identity resolution over-merge example showing incorrectly merged profiles]

A Unified Individual profile showing two names (John Smith and John Smithson), two companies (Acme Corp and Apex Inc), and email addresses from two different corporate domains — a clear false merge that should be two separate Unified Individuals

id: identity-resolution-over-merge

Challenge 2: Segment Counts Significantly Lower Than Expected

What happens: You rebuild an Account Engagement dynamic list as a Data 360 Segment, but the segment count is 30–50% lower than the equivalent AE list. Some audience members are clearly missing.

Why it happens: Several possible causes:

• Contacts without a valid opted-in Contact Point Email are excluded from the default segment scope
• The CRM data stream is not including all records (row-level filters applied during stream configuration)
• Identity resolution merged records that should have remained separate, reducing the individual count
• Field values in Data Cloud are not matching the condition values (data format difference — "Financial Services" vs "financial_services")

Resolution — diagnostic approach:

1. Create a segment with a single broad condition (all Contacts with a non-null email) and check the count against your CRM Contact count. This establishes the baseline.
2. If the baseline count is lower than expected, investigate the data stream configuration for filters.
3. If the baseline is correct but a specific segment is too low, add conditions one at a time to identify which condition is filtering too aggressively.
4. Check field value formats in Data Cloud against the values in your CRM (case sensitivity, whitespace, enum values).

Challenge 3: Consent Data Gaps

What happens: After migrating, a significant number of contacts have null consent status in Data Cloud. They are excluded from email campaigns because their consent state is unknown.

Why it happens: Account Engagement and Salesforce CRM sometimes have inconsistent consent field population. Contacts who were imported into AE directly (not via CRM sync) may not have corresponding CRM records with consent fields populated. Or the specific CRM field used to indicate consent was a custom field that was not included in the Data Cloud data stream.

[Screenshot: Consent data gap analysis showing contacts with null consent status]

A segment count comparison showing: Total Unified Individuals (15,240), Opted In (11,870 = 77.9%), Opted Out (890 = 5.8%), Null consent (2,480 = 16.3%) — the null segment highlighted as a data quality issue requiring resolution

id: consent-data-gap-analysis

Resolution:

1. Create a segment of contacts with null consent status to understand the scope
2. Investigate the source of the null contacts — are they from a specific data stream or time period?
3. If null contacts were legitimately opted in (they were receiving AE campaigns successfully), make the business decision about whether to apply a default opted-in status with a documented rationale, or require explicit re-consent
4. Update the consent field on the relevant CRM records and wait for the data stream to sync

Challenge 4: Engagement Studio Logic Without a Flow Builder Equivalent

What happens: You attempt to rebuild a specific Engagement Studio programme in Flow Builder and discover that the trigger logic you relied on in AE does not have a direct equivalent in MCN's Flow Builder.

Common specific gaps:

• AE "Prospect time in stage" trigger (fires after a contact has been in a list for X days) — MCN equivalent requires a more complex scheduled-entry condition
• AE "Tag" completion action — MCN does not have a direct tagging system; use custom Contact fields instead
• AE "Notify sales rep" completion action with specific routing logic — MCN creates Tasks, but the routing logic may need CRM automation rule support
• AE prospect field changes as a trigger — this requires a Change Data Capture stream in MCN

[Screenshot: Account Engagement feature with no direct Marketing Cloud Next equivalent]

A side-by-side comparison showing an Account Engagement Engagement Studio using a 'Prospect field change' trigger, next to the Marketing Cloud Next Flow Builder equivalent using a Segment-Triggered Flow with Change Data Capture as the entry mechanism — noting the additional Data Cloud configuration required

id: engagement-studio-no-equivalent

Resolution: For each missing equivalent:

1. Document the specific AE behaviour you are trying to replicate
2. Evaluate whether the MCN equivalent requires additional configuration (CDC stream, CRM automation, external integration)
3. If the functionality requires something MCN cannot currently provide natively, assess whether the underlying marketing goal can be achieved differently — often a slightly different architecture achieves the same business outcome

Challenge 5: Lost Engagement History for Personalisation

What happens: After migration, personalisation conditions based on prior engagement history ("contacts who engaged with Topic X content last year") are not available because AE's engagement history was not migrated.

Why it happens: Account Engagement Prospect activity history does not import into Data Cloud. MCN builds engagement history from day one of platform use — it cannot retroactively populate historical activities.

Resolution:

• For segments that depended on AE engagement history, rebuild them using available CRM data (custom fields updated by AE completion actions that are on the CRM Contact record are available)
• Accept that the first 3–6 months of MCN operation will have less rich engagement segmentation than AE had after years of history accumulation
• Prioritise building the highest-value engagement-based segments as soon as MCN has sufficient history (typically 90 days of active campaigns)

Challenge 6: Form and Tracking Script Gaps

What happens: After deploying the MCN Website Engagement tracking script, some forms are not recording submission events. Or the old AE tracking script and the new MCN script are creating duplicate event records.

Why it happens: Form submission tracking in MCN requires either the native MCN form builder or a custom Website Engagement event definition for third-party forms. If your forms use JavaScript submit handlers, the event may not be captured by the default page view tracking script.

Resolution:

1. Identify all forms on your website that should trigger Marketing Cloud Next events
2. For MCN native forms: verify the form is connected to the correct Data Cloud data stream
3. For third-party forms (Unbounce, Typeform, HubSpot embed): create a custom Website Engagement event triggered by the form's completion callback
4. Test each form by submitting from a test email address and verifying the event appears in Data Cloud

Challenge 7: Attribution Reporting Discontinuity

What happens: After migrating to MCN, your pipeline attribution reports show a gap or unexplained drop in influenced pipeline. Deals that were influenced by marketing activity during the migration period appear unattributed.

Why it happens: Contacts who received AE campaign emails during the migration period have those touches in AE's reporting system. When they later appear as Opportunity Contact Roles in Salesforce CRM, MCN's Opportunity Influence only credits MCN campaign touches — the AE history is not visible to MCN.

[Screenshot: Attribution reporting showing the gap during the migration transition]

A monthly Opportunity Influence chart showing normal attributed pipeline in months 1-4, a significant drop in months 5-6 (the parallel running period), and recovery in months 7-8 as MCN-touched contacts begin appearing in Opportunity Contact Roles

id: attribution-discontinuity-chart

Resolution:

• Accept this as an expected temporary gap — document the migration dates in your reporting annotations
• For executive reporting during the transition, present AE attribution (for AE-period touches) and MCN attribution (for MCN-period touches) separately with a clear explanation
• After 6 months of full MCN operation, the attribution picture will normalise as MCN-touched contacts accumulate and appear in new Opportunities

Challenge 8: Team Adoption and Muscle Memory

What happens: Team members revert to Account Engagement for new campaigns because it is familiar, despite the organisational decision to migrate to MCN.

Why it happens: Platform muscle memory is powerful. When a team member is under deadline pressure, they use the tool they know. This is a people and process challenge, not a technical one.

Resolution:

• Establish a clear, written policy: "New campaigns go in Marketing Cloud Next. Exceptions require approval."
• Run internal training sessions focused specifically on the campaign types your team runs most frequently — not generic feature overviews
• Identify one team member as the MCN champion who handles questions and helps others get unstuck
• Remove the temptation: revoke Account Engagement campaign creation permissions for team members who should no longer be using it, keeping access read-only for historical reference

Summary

None of these challenges are unique to specific organisations — they appear on virtually every Account Engagement to MCN migration. Teams that know about them in advance can test proactively, implement mitigations before they become issues, and respond to them faster when they do arise.

The migration challenges that cause the most disruption are the ones discovered mid-campaign: a consent gap that meant a live campaign sent to opted-out contacts, or an attribution problem discovered at a board review. Prevention through pre-migration testing is significantly cheaper than post-launch remediation.

Planning a Marketing Cloud Next migration and want to get ahead of these challenges? Pardive's migration programme includes proactive challenge prevention and a structured testing protocol for each of these known issues. Book a free migration consultation.