Migrate from Optimove to Microsoft Dynamics 365 Sales

Optimove Customer records are the primary migration object and split across Dynamics 365's two-object model. The customer name and company-level data map to Account; individual contact details (email, phone, address) map to Contact with a required AccountId lookup. We use Optimove's CustomerID as an external identifier throughout import to maintain referential integrity across phases. If Optimove data does not distinguish between company and individual contact records, we create a single Account with the Contact data merged for simplicity, and the customer chooses the split strategy during scoping.

Optimove lifecycle stages (such as Prospect, Active, At-Risk, Champion) migrate as a custom picklist field on Contact named optimove_lifecycle_stage__c. Historical stage transition data from the Migration Explorer export migrates to a related custom object or to custom date fields recording stage transition timestamps. The stage names are preserved verbatim so that reporting continuity is maintained. The customer's admin maps the specific Optimove stage values to Dynamics 365 picklist values during discovery.

Optimove's custom attributes migrate to Dynamics 365 custom fields on Contact or Account depending on whether the attribute applies to the individual or the organization. We audit the current Optimove attribute count during discovery to confirm the migration stays within a manageable scope given Dynamics 365's unlimited custom field model. Attributes that exceed the 50-attribute ceiling in Optimove are flagged before migration so that overflow data can be redistributed or trimmed. Each custom field gets a corresponding Dataverse column created in the destination environment before import.

Optimove's proprietary predictive scores (OptiGenie AI next-best-action values, propensity scores, migration scores) are exported as raw numeric values from Data Share SQL views. These migrate to Contact custom fields such as optimove_predicted_value__c and optimove_churn_risk__c. The underlying model logic, confidence intervals, and OptiGenie recommendation rules cannot migrate because they are calculated within Optimove's modeling engine. We flag this limitation clearly in the migration scope and recommend that the customer builds equivalent scores in Dynamics 365 using Power BI or Azure Machine Learning post-migration if predictive features remain a requirement.

Optimove Target Groups are dynamic customer segments built from attribute rules. We export the customer membership lists (the actual CustomerIDs included in each Target Group at the time of export) and recreate them as static Dynamics 365 Marketing Lists or as dynamic Marketing Lists with an equivalent filter criteria rebuilt manually. Complex nested rule structures require translation into Dataverse query syntax and may require a rules-rebuild workshop with the customer's marketing operations team post-migration.

Optimove campaign metadata including campaign name, type, channels, and scheduling migrates to Dynamics 365 Campaign. We map the Optimove channel type (email, SMS, push, web) to the corresponding Dynamics 365 Campaign Type value. Audience size from Optimove's campaign definition migrates as a note or custom field. Campaign-level budget data migrates to the Campaign BudgetAmount field if populated in Optimove.

Historical campaign performance data including sends, opens, clicks, conversions, and control group metrics exports from Optimove's Data Share and maps to Dynamics 365 Campaign Member records and custom campaign response fields. Each campaign interaction (send, open, click, conversion) creates a Campaign Member entry with the appropriate Campaign Member Status value. Engagement timestamps preserve the original Optimove recorded time for timeline accuracy.

Optimove's Control Group feature is documented in Data Share and preserves customer membership assignments for accurate campaign ROI calculation. We export the control group membership list and create a custom field on Campaign Member (control_group__c as boolean) to mark which customers were in the control group for each campaign. This preserves the ability to calculate uplift post-migration by comparing control versus treatment group performance.

Optimove structures customer data by customer network and brand, each potentially having separate database schemas. We identify all separate networks during discovery and map each to an appropriate Dynamics 365 Business Unit (within a single tenant) or to separate child tenant environments depending on the destination licensing structure and data isolation requirements. Schema differences between networks within the same Optimove tenant may require separate mapping workstreams for each brand. We deliver a separate migration scope per network if the schema divergence is significant.