Migrate from Marketing Optimizer to Microsoft Dynamics 365 Sales

Marketing Optimizer Contact records with name, email, phone, and company linkage map directly to Microsoft Dynamics 365 Sales Contact. The primary email address becomes the email1 field, phone becomes telephone1, and firstname/lastname split maps to standard Contact name fields. We resolve the parent Account (from Marketing Optimizer Company) by domain-match or manual mapping before Contact insert to satisfy the AccountId lookup. Standard contact fields migrate without transformation.

Marketing Optimizer Leads carry a lead-selling-specific lifecycle stage tied to buyer/seller assignment workflows. Microsoft Dynamics 365 Sales does not have an equivalent lifecycle model; Leads use a standard Lead Status (New, Contacted, Qualified, Unqualified) and Lead Quality (Hot, Warm, Cold) instead. We preserve the original Marketing Optimizer lifecycle stage value in a custom text field mo_original_lifecycle_stage__c on the Lead or Contact record. The split rule maps leads with active buyer/seller assignments to Lead; leads converted to confirmed buyers map to Contact with an Account. We define the split rule during scoping based on the customer's specific stage matrix.

Marketing Optimizer Company records map to Microsoft Dynamics 365 Sales Account. Company name maps to Account Name, website domain becomes the Website field, and address fields map to standard Address composite fields in Dynamics 365. We use the Company record as the first entity migrated so that AccountId is available for Contact and Lead lookups during subsequent phases. Parent-account hierarchy does not exist in Marketing Optimizer, so migrated Accounts are top-level unless the customer manually configures hierarchy post-migration.

Marketing Optimizer Campaign records carrying name, type, and associated contacts map to Dynamics 365 Campaign. Campaign Name maps to Campaign Name, and the campaign type maps to Campaign Type (Webinar, Trade Show, Email, etc.) using a value mapping table defined during scoping. We re-link associated Contacts and Leads via CampaignMember records after the Contact and Lead phases complete. CampaignMember Status maps from Marketing Optimizer campaign membership status where available.

Marketing Optimizer Lead Assignment records link a Lead to a specific buyer or internal user. Since Microsoft Dynamics 365 Sales does not have a native Lead Assignment object, we migrate these as a custom lookup field (mo_assigned_buyer__c or mo_assigned_user__c) on the Contact or Lead record pointing to the assigned User or Account. The assignment timestamp migrates as mo_assignment_date__c. We resolve the assigned user by email match against the destination Dynamics 365 User table during migration.

Marketing Optimizer tracks pages visited and time on site per contact as web tracking data. Microsoft Dynamics 365 Sales does not have a native web tracking equivalent in the standard Contact model. We migrate this as a custom multi-select picklist field (mo_pages_visited__c) for top pages, or as a formatted text notes block with page URLs and visit timestamps for detailed history. The customer chooses the strategy during scoping based on how they intend to use the data in Dynamics 365 reporting.

Marketing Optimizer custom fields added by the customer require field-level mapping to Dynamics 365 schema. We document all custom field names, data types, and picklist values during scoping, then pre-create the corresponding custom fields in Dynamics 365 Dataverse before data migration begins. Field type mapping accounts for differences: Marketing Optimizer multi-checkbox fields map to Dynamics 365 multi-select picklist, date fields map to datetime fields, and numeric fields map with appropriate precision. Validation rules in Dynamics 365 are documented before migration to avoid import blocking.

Attachments associated with Marketing Optimizer Contact, Lead, or Company records are not accessible via the platform's documented API endpoints. We flag all attachment-dependent records during scoping and recommend the customer exports attachments manually via the Marketing Optimizer UI before the migration window opens. Migrated records retain a custom field mo_has_attachments__c set to true so the customer can cross-reference against the manual export. SharePoint or Dataverse file storage is provisioned post-migration for the customer to re-attach files. This step is mandatory; failure to export results in permanent attachment data loss.