Migrate from Marketing Optimizer to HighLevel

Marketing Optimizer Contact records map directly to GoHighLevel Contact. Standard fields (first name, last name, email, phone, address) map to their GoHighLevel equivalents. We use email as the dedupe key during import to prevent duplicate creation. Any Marketing Optimizer custom properties on the Contact record are captured during scoping and mapped to GoHighLevel custom Contact fields, which must be pre-created in GoHighLevel before import begins.

Marketing Optimizer Lead records carry a lifecycle stage tied to the lead-selling workflow (active, sold, buyer-assigned, expired). GoHighLevel does not have a native Lead object with a lifecycle stage property. We migrate Leads to GoHighLevel Contact records and preserve the original Marketing Optimizer lifecycle stage value in a custom Contact field (e.g., mo_original_lifecycle__c as a single-select picklist). Lead assignment records map as a linked custom field on the Contact rather than a separate object.

Marketing Optimizer Campaign records carry name, type, associated contacts, and campaign-level performance data. We map Campaigns to GoHighLevel Opportunities in a designated pipeline (e.g., Campaign Pipeline) so that associated contacts are linked via the Opportunity-Contact relationship. Campaign type and performance metrics migrate as custom Opportunity fields. If the customer has multiple campaign types that need separate tracking, we recommend a Campaign custom object in GoHighLevel rather than reusing the standard Opportunity pipeline.

Marketing Optimizer tracks pages visited and time-on-site per contact as engagement data. GoHighLevel does not have a native web tracking equivalent. We migrate this data as custom multi-select fields on the Contact record (one field for pages visited, one for visit counts or timestamps). The customer decides during scoping whether to normalize this into tags, a custom object for tracking sessions, or leave it as raw historical fields on the Contact.

Marketing Optimizer automated workflows define lead routing, scoring, and action triggers tied to the lead-selling lifecycle. GoHighLevel Workflows use a different trigger-action model and are not directly compatible. We do not migrate workflow logic as code. We document every active workflow with its trigger conditions, filter criteria, routing actions, and delay sequences as a written migration artifact. The customer's admin uses this document to rebuild the logic in GoHighLevel's Workflow builder.

Marketing Optimizer assignment records map a lead to a specific buyer or internal user. We migrate these as a custom Contact field (e.g., mo_assigned_buyer__c) carrying the buyer identifier or user reference from Marketing Optimizer. This is a flat string or ID value rather than a linked object since GoHighLevel does not have a native assignment record type. The customer may choose to normalize these into GoHighLevel tags or pipeline stages during post-migration cleanup.

Any custom fields created by the customer in Marketing Optimizer (beyond the standard contact and lead fields) require field-level mapping to GoHighLevel. We document all custom field names, data types, and picklist values during scoping, then pre-create equivalent custom fields in GoHighLevel before data import. GoHighLevel supports custom Contact fields and custom Opportunity fields. Custom object support is available on higher tiers; we confirm availability during discovery.

Files attached to Marketing Optimizer contact or lead records are not accessible via the documented API. This is a platform-level limitation of Marketing Optimizer, not a migration-specific issue. We flag all attachment-dependent records during scoping and recommend the customer exports them manually via direct login before the migration window closes. We cannot carry attachment data programmatically and failure to export manually results in permanent loss for any record with attached files.