Migrate from Optimove to HighLevel

Optimove Customer records map to GoHighLevel Contact as the primary object. We export via the Optimove Customers API and Data Share SQL views, resolving the CustomerID as a unique dedupe key. Standard attributes (name, email, phone) map directly. Optimove's custom attributes are audited against GoHighLevel's custom field limits per object. Lifecycle stage assignments are preserved in a custom text field optimove_lifecycle_stage__c for reporting continuity.

Optimove Lifecycle Stages (e.g., Prospect, Customer, Champion) are not a native GoHighLevel object. We map each distinct stage to a custom field optimove_lifecycle_stage__c on the Contact record as a text value, and we preserve stage transition history from Migration Explorer exports as a JSON blob in a long-text field lifecycle_history__c. This allows the customer's admin to build reporting on original lifecycle state without rebuilding the behavioral model.

Optimove's custom attributes (up to 50 total across all input methods) map to GoHighLevel custom fields on Contact. We audit the source attribute count during discovery and flag any overflow risk. Attributes originally added via the Optimove real-time API must be created in GoHighLevel before the migration, as API-added attributes in Optimove can only be updated via UpdateCustomerAttributes and affect how we sequence the attribute creation step.

Optimove Target Groups are dynamic customer segments built from attribute rules. We export the customer membership lists (which customers belong to which segments) and recreate membership in GoHighLevel as custom multi-select fields (if the segment list is short) or as Tags on Contact records (if the segment count is large). Complex nested rules require manual translation during a post-migration journey mapping workshop.

Optimove does not expose a standalone Companies object in its API, but companies associated with customers can be extracted from Data Share SQL views. We map the company name and domain to GoHighLevel's Company object where the customer uses a company-centric data model. If the customer primarily uses individual contacts without company linking, we skip the Company object import to avoid orphaned records.

Optimove Campaigns are multi-channel orchestration records (email, SMS, push, web). GoHighLevel does not have a direct Campaign object equivalent to HubSpot or Salesforce. We map active Optimove campaigns to GoHighLevel Opportunities in a dedicated Pipeline (e.g., Marketing Pipeline) where the Opportunity name reflects the campaign title and stage tracks campaign status. Campaign metadata (type, channels, schedule) migrates as Opportunity fields.

Optimove campaign performance data (sends, opens, clicks, conversions, control group metrics) exported from Data Share maps to custom fields on the corresponding GoHighLevel Opportunity. Engagement metrics are linked to CustomerIDs for downstream attribution. We preserve the raw numerical scores where accessible; control group membership assignments migrate as a custom field for post-migration ROI analysis.

Optimove Control Groups are documented in Data Share and exportable. We preserve control group membership assignments as a custom field control_group__c on the Contact record. This allows the customer's analytics team to calculate campaign ROI post-migration using the original control group split.

Optimove engagement history (email sends, opens, clicks, SMS, push notifications, WhatsApp messages) exported via Data Share maps to GoHighLevel Activity records attached to the corresponding Contact. GoHighLevel's Activity model supports notes and tasks but not the granular engagement event schema that Optimove tracks. We flatten Optimove's multi-channel engagement events into a standardized activity timeline in GoHighLevel.

Optimove structures customer data by customer network and brand, with each potentially having independent database schemas. We identify all separate networks during discovery and map each to a GoHighLevel Sub-account. Each sub-account has its own Contact, Company, Pipeline, and Workflow workspace, maintaining data separation equivalent to Optimove's multi-brand architecture. This adds scoping complexity but is fully resolvable with a network inventory during discovery.

Optimove user accounts and roles can be listed via the platform admin interface. Role permissions and access levels require manual recreation in GoHighLevel because Optimove's permission model is proprietary. We export the user list and role assignments, then map to GoHighLevel User roles during migration. Any Optimove user without a corresponding GoHighLevel user is held in a reconciliation queue for the customer's admin to provision.