Migrate from Optimove to Pipedrive

Optimove's Customer record maps to both a Pipedrive Person and an Organization. We use the Customer's primary contact fields to create the Person record, and the Customer's associated company or network name to create or match the Organization. The CustomerID becomes a custom field optimove_customer_id__c on both Person and Organization for cross-reference. Multi-brand Optimove deployments may require mapping each Customer network to a separate Pipedrive Organization hierarchy or separate workspaces.

Optimove's custom attributes (up to 50 total across all input methods) migrate to Pipedrive custom fields on Person and Organization. We audit the existing attribute count during discovery and flag any overflow risk from the 50-attribute ceiling. Optimove attributes added via the real-time API can only be updated via UpdateCustomerAttributes in Optimove; we map these to Pipedrive custom fields with equivalent data types. Attributes exceeding Pipedrive's supported types (long text, multi-select, date fields) are stored as text fields with format documentation for the customer admin.

Optimove Lifecycle Stages (such as Prospect, Active, At-Risk, Evangelist, and custom stage values) migrate to a Pipedrive custom field optimove_lifecycle_stage__c on the Person object. Lifecycle stage transition history from Optimove's Migration Explorer is not migratable as behavioral data; we export the current stage assignment per Customer. The customer admin should plan for lifecycle stage monitoring using Pipedrive's automation rules or custom dashboards post-migration.

Optimove Target Groups are dynamic customer segments built from attribute rules. We export the customer membership lists (the actual customer IDs in each segment) and recreate them as Pipedrive Filters. Complex nested rules (AND/OR conditions with multiple attribute thresholds) may not translate directly to Pipedrive's filter builder; we document the original rule logic and flag any manual segmentation requirements for the customer's admin. The customer should validate filter coverage against the original target group membership counts.

Optimove's proprietary predictive scores, OptiGenie AI next-best-action recommendations, and confidence intervals are calculated by Optimove's internal modeling engine and have no standard equivalent in Pipedrive. We export the raw numerical scores where accessible via Data Share as a reference file, but the scores cannot be operationalized in Pipedrive without recalibration. Customers relying heavily on predictive scoring should plan for a scoring model rebuild using Pipedrive's custom fields, third-party scoring tools, or a data warehouse integration.

Optimove campaign metadata (name, type, channels, schedules, audience sizes) migrates to Pipedrive Deal records and Activity records. Each Optimove campaign maps to a Pipedrive Deal representing the campaign initiative, with campaign metadata stored as custom fields on the Deal. Campaign-level engagement metrics (total sends, opens, clicks) store as custom numeric fields on the Deal. The customer admin should plan to rebuild campaign journey orchestration logic in Pipedrive using automation rules and email sequences.

Optimove campaign engagement data (sends, opens, clicks, conversions) links to individual Customers via CustomerID. We migrate engagement history as Pipedrive Activity records (calls, emails, tasks) linked to the corresponding Person record. The engagement metric values (e.g., open count, click count) store as custom fields on the Activity or as a linked custom object if the customer requires detailed engagement history. Control group membership assignments migrate to a custom field on the Person record.

Optimove Control Groups store customer membership assignments for campaign holdout testing. We migrate the control group membership to a custom field optimove_control_group__c on the Person record, preserving the original control group name and assignment status. This allows the customer to calculate campaign ROI post-migration by comparing converted customers against the control group baseline.

Optimove's multi-brand architecture structures customer data by network and brand, each potentially having separate database schemas. We identify all separate networks during discovery and map each to an appropriate Pipedrive destination: either separate Organizations (if operating under one Pipedrive account), separate Pipedrive Workspaces (if using Pipedrive's workspace feature), or entirely separate Pipedrive accounts per brand. Schema differences between networks within the same Optimove tenant require separate mapping workstreams and may increase migration timeline and cost.

Optimove user accounts and roles can be listed via the platform admin interface. We export user name, email, and role assignments and provision matching Pipedrive User records. Optimove role permissions and access levels (marketing ops, campaign manager, analyst, viewer) require manual recreation in Pipedrive because Optimove's permission model is proprietary. Pipedrive's permission roles (admin, manager, member) differ from Optimove's access model and should be reviewed by the customer's admin before migration.