Loading
Ongoing maintenance for Salesforce HelpRead More

Key Considerations for Migrating Email Delivery Data from MC Engagement to Marketing Cloud Next

Publish Date: Oct 29, 2026
Description

Important: Consent Model Differences to Understand Before Migration

MCE and MCN manage email opt-in and opt-out at different levels.

MCE Consent Model: Individual (Subscriber) Level

  • Each Subscriber with the same email address has an independent consent state.
  • Example: If exampleIdA opts out, exampleIdB with the same address can still receive email.

MCN Consent Model: Contact Point (Email Address) Level

  • MCN treats the same email address as a single Contact Point.
  • Example: If example@gmail.com opts out, email delivery to that address stops.

Note. Because of this difference, an address opted in within MCE may be treated as opted out in MCN. Review and reconcile Subscribers who share the same email address before migrating.

 

Required Migration Tasks

Step 1: Share Domain Configuration

Step 2: Ingest Consent Data 

  • Identify where your consent data lives.
    • Managed in Publication Lists. Consent Mapping supports bidirectional sync.
    • Managed in All Subscribers. If you use All Subscribers, Consent Mapping bidirectional sync is not supported and a separate initial ingestion is required.
  • Determine high-priority subscriptions to ingest first.
  • See "Consent Ingestion Methods (3 Options)" below for ingestion details.

Step3: Warm Up & Test (Pre-Launch Validation)

  • Domains can be copied to MCN, but IP addresses cannot be shared.
  • Build an IP warming plan and work backward from your go-live date.
  • Start with highly engaged Subscribers and expand gradually.
  • Monitor bounce rates and spam complaint rates continuously.

 

Consent Ingestion Methods (3 Options)

Use one of these methods to ingest existing MCE email consent data into MCN.

Option 1: Sync MCE Publication Lists (if consent is managed in Publication Lists)

  • Automatic, bidirectional, near-real-time sync. See Sync MCE Publication Lists.
  • Mapping a Publication List creates a Communication Subscription in MCN.
  • After mapping, opt-ins and opt-outs sync in near real time.
  • Note. Not available if consent is managed in All Subscribers. Use Option 2 or 3 instead.

Option 2: Manual CSV Upload in MC Next (50,000 records or fewer)

  • Simple method to get started.
  • Supports up to 50,000 records per upload.
  • Best for small datasets or one-time lists.

Option 3 : Large-Scale Ingestion (more than 50,000 records)

For ingestion exceeding 50,000 records, refer to this article:

Marketing Cloud Next - Consent Management: Consent at Scale and Data Ingestion

 

Email Domain and IP Considerations

Domains Can Be Shared (Copied), but IPs Cannot

Detailed steps are available: Share Email Sending Domains with MCN.

ItemHow It Works with MCE → MCN
Email sending domainCan be shared via the "Connect Data" page in MCN Setup.
IP addressCannot be shared (MCN uses separate IPs from MCE).

Notes on Domain Sharing 

  • If the MCE domain is configured via delegation, it takes effect immediately. Self-hosted domains copy in Draft status and require DNS record configuration.
  • When you send from MCN, your domain may be treated as a new sender. Verify DMARC, SPF, and DKIM before launch. Monitor deliverability. See Marketing Cloud Next - Domain Warming 30 Day Plan.

 

Knowledge Article Number

005461440

 
Loading
Salesforce Help | Article