Migrate from Marketing Optimizer to Zoho CRM

Marketing Optimizer standard contact records with name, email, phone, and company linkage map 1:1 to Zoho CRM Contacts. We use email address as the dedupe key during import. Standard fields (First_Name, Last_Name, Email, Phone, Mailing_Street, Mailing_City, Mailing_State, Mailing_Zip, Mailing_Country) map directly to their Zoho equivalents.

Marketing Optimizer Lead records carry a lifecycle stage tied to the lead-selling workflow (buyer status, routing stage, assignment status). Zoho CRM does not model lead-selling lifecycle stages natively, so we preserve the original Marketing Optimizer stage as a custom Lead field mo_original_lifecycle_stage__c and the assignment status as mo_assignment_status__c. The customer decides during scoping whether to normalize these values to standard Zoho Lead Status or retain them as custom metadata for reporting.

Marketing Optimizer Assignment records link a lead to a specific buyer or internal user. These do not have a native Zoho CRM equivalent, so we migrate them as a multi-select or lookup custom field on the Zoho Contact record named mo_assigned_buyer__c (or the equivalent field name agreed during scoping). If multiple assignments per contact exist, we store them as a comma-separated text field or create a related Custom Module depending on the customer's data model complexity.

Marketing Optimizer Campaign records carry name, type, and associated contact IDs. These map to Zoho CRM Campaigns. We re-link associated contacts during import by resolving the Marketing Optimizer contact IDs to their new Zoho CRM Contact IDs through the email-based dedupe mapping. Campaign Type maps to Zoho Campaign Type picklist.

Any custom fields defined by the customer on Marketing Optimizer Contacts, Leads, or Campaigns require field-level mapping to Zoho CRM. We document all custom field names, data types, and picklist values during scoping, then pre-create equivalent custom fields in Zoho before data import. Custom fields that cannot map to a Zoho native type (e.g., multi-value arrays) are stored as Text fields with a note in the mapping document. This is the most scope-variable object mapping and must be confirmed before migration begins.

Marketing Optimizer tracks pages visited and time on site per contact. Zoho CRM does not have native web tracking, so this data migrates as a custom multi-value text field mo_web_pages_visited__c storing URL and timestamp pairs, or as a numeric engagement score mo_engagement_score__c if the source platform provides a computed score. The customer chooses the representation during scoping.

Files attached to Marketing Optimizer contact or lead records are not accessible via the documented API. We flag all attachments during scoping with the record ID, file name, and attachment URL (if exposed). The customer must export these manually before the migration window closes. We provide a written inventory of every flagged attachment with recommended export steps. Failure to complete manual export before cutover results in permanent data loss for attachment-dependent records.

Marketing Optimizer automated workflows define lead routing, scoring, and action triggers. The platform does not expose workflow definitions in a transferable format, so we do not migrate them as code. We document every active workflow as a written artifact: trigger conditions, action sequences, delay rules, and routing logic. The customer rebuilds these in Zoho Workflow Rules or Blueprint post-migration using this inventory.

Marketing Optimizer Owner records map to Zoho CRM Users. We resolve owners by email match against the destination Zoho org's user table. Any Marketing Optimizer Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner records are resolved before any record import to satisfy Zoho's OwnerId lookup requirements.

Marketing Optimizer Contact records carry a company linkage. These map to Zoho CRM Accounts with the company name as the Account Name field. The mapping is 1:1 at the Account level, and each Account is created before related Contacts to satisfy the Account Lookup relationship at insert time.