Migrate from Marketing Optimizer to Pipedrive

Marketing Optimizer Contact records map 1:1 to Pipedrive Person. We map name, email, phone, company linkage, and address fields directly. The original Marketing Optimizer record ID is preserved in a custom field mo_original_id__c for audit and cross-referencing during reconciliation. Standard Pipedrive Person fields (name, email, phone, org_id) are used for direct mapping; any non-standard contact metadata lands in custom fields we create during schema setup.

Marketing Optimizer Company records map to Pipedrive Organization. The company domain or name becomes the Organization name, and address fields map to the standard Pipedrive address compound field. Organization is created before any Person import so that the org_id lookup is satisfied at Person insert time, preventing orphaned Person records.

Marketing Optimizer Lead records carry a lifecycle stage tied to the lead-selling workflow. Pipedrive does not have an equivalent lifecycle stage property on People. We migrate Leads as People and preserve the original lifecycle stage value in a custom field mo_lifecycle_stage__c. The customer decides whether to normalize these values into Pipedrive Lead Status for People that require a Lead record, or retain them as a custom field for segmentation and reporting.

Marketing Optimizer Deal records map to Pipedrive Deal. We map deal title, value, expected close date, and stage. The source pipeline and stage names map to Pipedrive Pipeline and Stage within that pipeline. Pipedrive's visual pipeline view replaces Marketing Optimizer's list-based deal tracking. We configure Pipedrive pipeline stages during schema setup before Deals are imported, using the stage names from Marketing Optimizer as the starting configuration.

Marketing Optimizer Campaign records (name, type, associated contacts) map to Pipedrive Campaign. Associated contacts are relinked during import via mo_original_id__c lookup resolution. Pipedrive Campaigns track marketing initiative performance and are accessible from the CRM layer without a separate add-on. Note that Pipedrive's native campaign reporting is more limited than Marketing Optimizer's built-in lead performance reporting; we document the gap for the customer during scoping.

Marketing Optimizer call records map to Pipedrive Activity with type = call. Call disposition, duration, and any notes migrate to custom Activity fields. WhoId on the Activity points to the migrated Person record resolved via mo_original_id__c lookup. Activity timestamps are preserved to maintain the engagement timeline in Pipedrive's People activity feed.

Marketing Optimizer email engagement records migrate to Pipedrive Activity with type = email. Email subject, body content, and direction (sent/received) map to corresponding Activity fields. The linked Person record is resolved via mo_original_id__c before insert. Pipedrive stores email content as Activity records rather than as a separate EmailMessage object like Salesforce, keeping the model simpler but with less email threading depth.

Marketing Optimizer meeting records map to Pipedrive Activity with type = meeting. Start and end timestamps, location, and meeting title migrate directly. Attendees are resolved via mo_original_id__c and linked to the Activity as Participants. If the meeting is associated with a Deal in Marketing Optimizer, the Activity is linked to the migrated Deal record as well.

Marketing Optimizer task engagements map to Pipedrive Activity with type = task. Task status (pending/completed), priority, due date, and assignment migrate directly. Task assignment resolves the Marketing Optimizer owner to the corresponding Pipedrive User via email match. Open tasks with past due dates are flagged during migration for the customer to review and reprioritize in Pipedrive.

Marketing Optimizer Lead Assignment records map a Lead to a specific buyer or internal user. Pipedrive does not have a native assignment-to-buyer record type. We migrate these as a custom field mo_buyer_assignment__c on the Person record, storing the buyer identifier and assignment date as a formatted string. If the customer needs this data queryable, we recommend splitting buyer and assignment date into separate custom fields during schema design.

Marketing Optimizer tracks pages visited and time on site per contact. Pipedrive does not have native web tracking; this data migrates as a custom field mo_web_pages_visited__c storing the page URLs and a mo_web_time_on_site__c custom field with duration. The customer chooses whether to populate these fields as free text or structured key-value pairs. If Pipedrive's Web Visitors add-on is active, the migrated data serves as historical baseline rather than live tracking.

Any custom fields defined by the customer in Marketing Optimizer require field-level mapping to Pipedrive custom fields. We document all custom field names, types, and current values during scoping, then create matching custom fields in the destination Pipedrive account before any data is imported. Field types are mapped: text to string, number to numeric, date to date, dropdown to set options from the Marketing Optimizer picklist values.