Migrate from Salesforce Marketing Cloud Account Engagement to Microsoft Dynamics 365 Sales

MCAE Prospects have no direct Dynamics 365 equivalent. We split Prospects by scoring tier at migration time: Prospects with a behavioural score above a customer-defined threshold and a linked Salesforce Account that maps to a Dynamics Account become Contacts attached to that Account. Prospects with scores below the threshold or no Account linkage become Leads. The split threshold is defined during scoping based on the customer's scoring category matrix. The original Pardot prospect score migrates as a custom field prospect_score__c on both Lead and Contact for audit and rebuild reference. Email address is the sole unique identifier in Pardot; we apply a three-pass matching strategy (exact email, normalised email, manual resolution queue) to detect duplicates before insert.

Pardot Custom Fields are first-class API objects with full CRUD support in the v5 API. We export field definitions (label, data type, associated Tags) and their values per Prospect. Each Custom Field maps to a typed field on the appropriate Dynamics entity (Lead or Contact) based on whether the Prospect splits to Lead or Contact. Picklist and multi-select fields require a value-set audit against Dynamics AllowedValues. Custom Fields that reference Pardot-only objects (Engagement Programs, Scoring Categories) are flagged as data fields rather than functional fields and migrated as text or picklist values.

MCAE has no native Account object — Prospects are linked to Salesforce Accounts via the Pardot-Salesforce Connector. We resolve the Salesforce Account ID stored on each Prospect and map it to a Dynamics Account. If the Salesforce Account name does not already exist as a Dynamics Account, we create it during the migration. Account Website, Industry, and Address fields migrate directly. Account records are inserted before Contact and Lead records so that AccountId lookups are satisfied at the time of record import.

MCAE Campaigns track marketing initiative performance and link to Salesforce Campaigns. We export Campaign metadata (Name, Type, Status, StartDate, EndDate, BudgetedCost) and Prospect-level activity data (opens, clicks, form submissions) as Campaign Member activity records in Dynamics 365. The Campaign Member Status field maps from MCAE Campaign member engagement status. Campaign hierarchies (parent-child campaign structures in Pardot) map to Dynamics Campaign hierarchy via ParentCampaignId lookup.

Pardot Users (Assigned Users / Owners) correspond to the Salesforce Users who own Prospect records. We map Pardot user_id to Dynamics User by email address lookup against the Microsoft 365 Azure Active Directory tenant. Owners without a matching Dynamics User go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Pardot users are mapped to inactive Dynamics users so that OwnerId references are satisfied without reactivating licences.

Tags segment Prospects and attach to Custom Fields. We export tag definitions and their assignments per Prospect. Tags migrate as a multi-select picklist on Lead or Contact, or as Dynamics Topics with TopicAssignment records, depending on the customer's use case. The tag strategy is chosen during scoping. Tags used for marketing segmentation map to Dynamics marketing lists and Campaign Member records.

Scoring Categories define named weight buckets (behavioural score vs. demographic grade). We export category definitions, weight rules, and the per-Prospect category scores. The scores migrate as typed fields on Lead or Contact. The weight logic is not functional at the destination — it is documented as a written specification for the customer's Dynamics admin to rebuild using Sales Copilot lead scoring or a Power Automate flow with a scoring calculation layer.

Static Lists and Dynamic Lists segment Prospects for targeted campaigns. We export list memberships as Prospect records with the list name stored on each record. Dynamic Lists with rule-based criteria do not migrate as active lists — the criteria are documented and the customer rebuilds them as Dynamics Marketing Lists or Power Automate-based segments. Static list memberships migrate as a custom field list_name__c or as Campaign Member records linked to a corresponding Dynamics Campaign.

Email Templates contain HTML content, dynamic content blocks, and merge fields. We export template HTML and metadata. The double-brace Pardot merge field syntax (%%first_name%%, %%email%%) is rewritten to Dynamics-compatible token syntax ({(lead.firstname)}, {(lead.emailaddress})). Templates with complex branching conditional logic are flagged for manual rebuild in Dynamics Email Templates or Power Automate approval flows rather than automated import, because Dynamics Email Templates handle conditional content differently from Pardot dynamic content blocks.

MCAE tracks Prospect engagement activity (email opens, link clicks, form submissions) against Campaigns. We export engagement history per Prospect-Campaign pair and create Campaign Activity records in Dynamics or Notes linked to the corresponding Contact or Lead. Engagement timestamps are preserved. Note that MCAE's Visitor Activity tracking (anonymous browsing behaviour) does not have a native Dynamics equivalent and is documented as a gap in the written migration report.