Migrate from Optimove to HubSpot

Optimove customer profiles map to HubSpot contacts. Each contact inherits the lifecycle_stage value as a custom pick-list property (Lifecycle_Stage__c) since HubSpot has no native stage-history equivalent. Email uniqueness is enforced — if the same email exists in multiple Optimove networks, FlitStack flags duplicates for manual resolution before import.

Optimove supports up to 50 attributes per customer (real-time via API plus batch data share). Each attribute becomes a HubSpot custom property — type-mapped (string to single-line text, numeric to number, date to date picker, pick-list to dropdown). If the account exceeds HubSpot's per-object property limit, FlitStack surfaces the surplus attributes and proposes consolidation before migration.

Optimove companies map 1:1 to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer as direct or value-mapped fields. Optimove's multi-network company structures are flattened — if the same domain appears across networks, the primary network's company record becomes the HubSpot company, and secondary network associations surface as custom fields or notes.

Optimove campaigns are targeting definitions — lists of customers excluded or included per campaign. These translate to HubSpot lists (static or active) for contact grouping. Campaign-level engagement metrics (opens, clicks, sends) migrate as custom deal properties or custom properties on the associated contact since HubSpot's campaign object tracks member status differently than Optimove's engagement metrics.

Churn probability, RFM scores, lifetime value predictions, and other OptiGenie model outputs migrate as HubSpot custom number properties (Churn_Probability__c, RFM_Score__c, LTV_Prediction__c). HubSpot's Breeze AI runs independently on HubSpot data post-migration — FlitStack preserves Optimove's existing scores as static reference values so teams can compare against HubSpot-native scoring over time.

Optimove's lifecycle stage labels (New, Active, At-Risk, Churned, Reactivated, etc.) migrate as HubSpot custom pick-list values. Stage-transition timestamps from Optimove's Migration Explorer report can be stored as a separate custom datetime property (Lifecycle_Stage_Updated__c) for reporting continuity. HubSpot's own lifecycle_stage property is not used in this migration — its values and behavior are set independently post-migration.

Optimove customers can exist in multiple independent networks. If a customer appears in more than one network, FlitStack creates a single HubSpot contact and stores each network's attribute values as separate custom property groups (e.g., NetworkA_CustomField__c, NetworkB_CustomField__c) or associates each network as a separate HubSpot company linked by association. Teams choose the strategy pre-migration.

Optimove engagement data (email opens, clicks, channel interactions) translates to HubSpot contact timeline entries where possible, or as custom properties on the contact record if event-level granularity is too voluminous for timeline import. FlitStack maps engagement by channel: email events become HubSpot email activities; SMS events migrate as custom activity properties; push and in-app events map to notes or custom engagement fields.

If Optimove stores engagement notes, call logs, or meeting records, these map to HubSpot contact timeline entries. Notes become HubSpot notes on the contact record; calls and meetings become HubSpot engagement activities. Original timestamps and owner assignments are preserved. If Optimove stores this data outside its data share, FlitStack extracts it via the Customers API and bulk-imports it to HubSpot's engagement timeline.

Optimove owner assignments are resolved by email match against HubSpot user accounts. If a HubSpot user with the matching email exists, the contact is assigned to them. If no match is found, FlitStack flags the record for the customer's team to either create a HubSpot user or assign a fallback owner before migration commits. No contact lands in HubSpot without a resolved owner.

File attachments linked to Optimove customer records are downloaded and re-uploaded to HubSpot Files, then associated to the corresponding contact record. File size limits apply (HubSpot's 25MB per file default). Inline images embedded in Optimove notes are extracted and rehosted as HubSpot file assets.