Coexisting with Account Engagement During Your Marketing Cloud Next Transition

The cleanest way to migrate from Account Engagement to Marketing Cloud Next is not a hard cutover. It is a planned parallel running period — a phase where both platforms are active simultaneously, each running a defined portion of your marketing programme.

This approach reduces risk, allows side-by-side performance comparison, and gives your team time to build confidence in Marketing Cloud Next before fully committing to it. But it introduces its own operational complexity: contacts could be in active journeys in both platforms, consent changes in one system might not immediately reflect in the other, and attribution reporting becomes fragmented.

This guide shows how to manage the parallel period cleanly.

Why a Parallel Running Period Is the Right Approach

A hard cutover — deactivating Account Engagement on Day 1 of Marketing Cloud Next — has significant risk:

• If MCN is misconfigured (a common scenario in the first weeks), you have no fallback
• Contacts in active AE Engagement Studios need to complete their journeys or be migrated mid-flow (complex and error-prone)
• Your team has no muscle memory with MCN and is simultaneously trying to run all campaigns on an unfamiliar platform

A parallel period solves these problems. You transition campaigns progressively, gaining confidence with each migration, while maintaining a known-good fallback.

Typical parallel period duration: 6–12 weeks for most mid-market B2B teams.

The Parallel Period Campaign Allocation Framework

Define which types of campaigns run in which platform during the parallel period.

Run in Marketing Cloud Next from Day 1:

• All new campaigns (any campaign created after the MCN go-live date)
• New inbound lead follow-up flows (new leads enter MCN, not AE)
• Website-triggered campaigns (MCN tracking is live; trigger events route to MCN)

Keep in Account Engagement until completion:

• Campaigns currently active with contacts mid-journey (let them finish)
• Engagement Studios with 30+ days remaining in active runs
• Any campaign using AE-specific features without a clear MCN equivalent yet

Do not run in either platform simultaneously:

• The same contact receiving campaign emails from both AE and MCN on the same topic
• Re-engagement campaigns targeting your full database (will cause duplicates)

[Screenshot: Campaign allocation diagram showing which campaigns run in which platform]

A quadrant diagram showing campaign allocation during the parallel period: New campaigns in top-left (MCN), Active long-running campaigns in top-right (AE), Inbound triggers in bottom-left (MCN), and Scheduled batch sends in bottom-right (AE until completion)

id: parallel-running-campaign-split

Managing Audience Overlap

The most operationally dangerous aspect of parallel running is sending the same contact emails from both platforms on the same or similar topic. This produces a poor experience (over-emailing), can trigger elevated unsubscribe rates, and confuses attribution.

Prevention strategy — contact-level routing:

Implement a routing logic in Salesforce CRM using a custom Contact field: "Marketing Platform" with values "Account Engagement," "Marketing Cloud Next," or "Both."

• New contacts created after the MCN go-live date are flagged as "Marketing Cloud Next"
• Contacts in active AE journeys are flagged as "Account Engagement" until their journey ends
• As AE journeys complete, contacts are reclassified to "Marketing Cloud Next"

Use this field as an exclusion condition in both platforms: AE campaigns exclude contacts flagged as MCN; MCN campaigns exclude contacts flagged as AE.

Contact-level overlap check:

Before launching any MCN campaign, run an audience overlap analysis:

1. Export your MCN segment as a list of contact emails
2. In Account Engagement, search for those email addresses to identify anyone currently active in an AE programme
3. Exclude those contacts from the MCN campaign launch until their AE journey completes

[Screenshot: Audience overlap check between AE and MCN active campaigns]

An audience overlap analysis showing 3,847 contacts in the planned MCN segment, with 312 contacts (8.1%) flagged as currently active in AE Engagement Studios — the 312 are highlighted for exclusion from the MCN launch

id: ae-mcn-audience-overlap-check

Consent Management Across Both Platforms

Both platforms need to respect the same consent state. A contact who unsubscribes from an AE email must also be suppressed in MCN, and vice versa.

The source of truth: Salesforce CRM Contact field HasOptedOutOfEmail (and any custom opt-in fields your organisation uses). Both AE and MCN should read from and write to this same CRM field.

In Account Engagement: Ensure unsubscribes update the CRM Contact record's opt-out field. This is standard AE behaviour if the Salesforce Connector is correctly configured.

In Marketing Cloud Next: Ensure the consent configuration reads from the same CRM Contact field. When a contact opts out via MCN, the change should write back to the CRM field.

Testing the cross-platform consent chain:

1. Use a test contact
2. Unsubscribe them in an Account Engagement email
3. Verify the CRM Contact HasOptedOutOfEmail = True (may take up to 20 minutes with AE sync)
4. Verify the contact is excluded from an MCN segment that requires opt-in
5. Repeat in the other direction: opt-out via an MCN email, verify exclusion in AE

If either direction fails, the consent chain is broken and requires configuration investigation before the parallel period continues.

Attribution During Parallel Running

Campaign attribution is fragmented during a parallel period — some touches are in AE, some in MCN, and they are in separate systems.

Accept this limitation rather than trying to solve it technically. The parallel period is time-bounded; fragmented attribution for 6–12 weeks is acceptable if the end state is clean attribution in MCN.

What to track during parallel running:

• AE campaign performance in AE reporting (as always)
• MCN campaign performance in MCN reporting
• Note the MCN go-live date in your Salesforce Campaign records so historical attribution analysis can account for the transition

Do not attempt:

• Retroactively importing AE campaign touches into MCN attribution
• Building a unified attribution view spanning both platforms (not worth the engineering effort for a temporary state)

When to Decommission Account Engagement

The decision to decommission AE should be based on objective criteria, not a calendar date.

Decommission readiness indicators:

• [ ] All active AE Engagement Studios have either completed or been intentionally deactivated
• [ ] No contacts are flagged as "Account Engagement" in the platform routing field
• [ ] All critical MCN equivalents for AE programmes are live and validated
• [ ] MCN consent suppression has been tested and confirmed functioning
• [ ] 90-day performance data for MCN campaigns is available and meets expectations
• [ ] Your team is fully trained on MCN and comfortable running all campaign types without AE as a fallback

[Screenshot: Account Engagement decommission readiness checklist]

A checklist with 8 items, showing 6 completed (green checkmarks) and 2 in progress: 'All AE Engagement Studios completed' (72% complete) and '90-day MCN performance data available' (showing 64 days elapsed)

id: decommission-readiness-checklist

Communication: Keeping Your Team Aligned

A parallel running period requires clear internal communication. The biggest risk is not technical — it is people launching campaigns in the wrong platform because the decision framework was not clearly communicated.

Create and distribute a one-page decision guide:

• "If this is a NEW campaign starting today → use Marketing Cloud Next"
• "If this campaign was already RUNNING before [go-live date] → let it finish in Account Engagement"
• "If you are UNSURE which platform to use → ask the migration lead before proceeding"

Brief your sales team separately: lead alerts, task creation, and CRM notifications will change during the transition. Alert them to expected changes and provide a point of contact for questions.

Summary

A well-managed parallel running period reduces migration risk by keeping Account Engagement as a functional fallback while Marketing Cloud Next is validated. The keys to doing it cleanly are: a clear campaign allocation framework, an audience overlap prevention mechanism, a tested consent chain across both platforms, and objective decommission criteria.

The goal is a clean handoff, not a rushed cutover. Take the time the parallel period needs to be done correctly.

Managing a parallel running period between Account Engagement and Marketing Cloud Next? Pardive provides migration programme management including parallel period planning and decommission readiness reviews. Book a free consultation.