Migrate from Marketing Optimizer to Salesforce Sales Cloud

Marketing Optimizer standard Contact records with name, email, phone, and company linkage map 1:1 to Salesforce Contact. The src_email field becomes Contact.Email, src_phone becomes Contact.Phone, and src_company maps to the Account lookup after the Account object is provisioned. We resolve the Account lookup at import time by matching the company name from Marketing Optimizer against the Account.Name dedupe key.

Marketing Optimizer Lead records carry a lifecycle stage tied to the lead-selling workflow (buyer status, seller status, assignment state). These do not map 1:1 to Salesforce Lead because Salesforce Lead is designed for unqualified prospects rather than buyer/seller attribution records. We migrate Marketing Optimizer Leads to Salesforce Contact with a custom field mo_original_lifecycle_stage__c preserving the original stage value, and a custom field mo_assignment_status__c preserving the buyer or internal user assignment. This approach retains the full attribution history that drives reporting in lead-selling operations.

The Marketing Optimizer lifecycle stage value (buyer, seller, assigned, unassigned, or other lead-selling-specific values) migrates to a custom Text field on the Salesforce Contact. We document all distinct lifecycle stage values during scoping and map each to a corresponding picklist value in the custom field. The customer's admin decides whether to use this field for segmentation, reporting, or Flow triggers post-migration.

Marketing Optimizer assignment records link a Lead to a specific buyer or internal user. We migrate these as a custom Contact field (mo_assigned_buyer__c) storing the buyer identifier from Marketing Optimizer. If the buyer is a known Account in Salesforce, we resolve the AccountId lookup; otherwise the field stores the raw identifier for the customer's admin to reconcile.

Marketing Optimizer Campaign records carry name, type, and associated contacts. We map these to Salesforce Campaign and re-link associated contacts through CampaignMember records during import. Campaign Type maps to Salesforce Campaign Type picklist; any custom campaign types in Marketing Optimizer become custom picklist values in Salesforce before import.

Campaign-member relationships (which contacts are associated with which campaigns) migrate as Salesforce CampaignMember records. We resolve the ContactId and CampaignId references at migration time using the email dedupe key for contacts and the Campaign Name for campaigns. Status values from Marketing Optimizer map to Salesforce CampaignMember Status.

Marketing Optimizer tracks pages visited and time on site per contact. This data migrates as a custom multiline text field (mo_web_activity__c) on the Contact record containing page URL, timestamp, and duration in a structured format. Salesforce does not have a native web tracking equivalent; the customer's admin can use this field for manual reference or import it into a Salesforce Data Cloud model for analysis.

Any custom fields added by the customer in Marketing Optimizer require explicit field-level mapping to the Salesforce schema. We document all custom field names, types, and values during scoping, create the corresponding custom fields in Salesforce (with appropriate types: Text, Number, Picklist, Date, Checkbox), and map the values during import. Custom field naming follows Salesforce __c suffix convention and preserves the original Marketing Optimizer field label for traceability.

Marketing Optimizer Owners referenced on Contact, Lead, and Campaign records map to Salesforce User records by email match. Any Marketing Optimizer Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners are mapped to inactive Users if historical assignment matters; otherwise they are flagged for the admin to decide.

Marketing Optimizer call engagements map to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and any notes transfer to custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Marketing Optimizer timestamp. The WhoId points to the migrated Contact.

Marketing Optimizer email engagements migrate to Salesforce EmailMessage records linked to an Activity Task record. Email body content, subject, from address, and to address migrate to EmailMessage fields. The Task record appears in the Contact activity timeline with WhoId pointing to the migrated Contact and WhatId pointing to the related Campaign or Opportunity if applicable.

Marketing Optimizer meeting engagements map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee mapping creates EventRelation records pointing to the migrated Contacts and Users. Activity timeline ordering is preserved by setting the Event start time to the original Marketing Optimizer timestamp.

Marketing Optimizer notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact. Note title and body preserve; any attachments to notes require separate manual export (see gotcha on attachments). The Note creation date maps to ActivityDate for timeline ordering.

Automated workflows in Marketing Optimizer define lead routing, scoring, and action triggers. Workflow definitions are not accessible in a transferable format via the documented API. We document every active workflow with its trigger conditions, action sequences, and delay rules as a written migration artifact. The customer's admin or a Salesforce partner uses this artifact to rebuild equivalent logic in Salesforce Flow post-migration. We do not migrate workflow logic as executable code.

Files attached to Contact or Lead records are not accessible via the Marketing Optimizer API. We flag all records with attachments during scoping and recommend the customer exports them manually as a separate step before the migration window opens. Failure to perform this manual export results in permanent data loss for attachment-dependent records. We include an attachment-flagged record list in the migration artifact package.