Migrate from Optimove to Zoho CRM

Optimove's Customer is the central object with unified behavioral profiles. We split this at migration time: B2B Customer records (those with company association) map to Zoho Account plus Contact; pure B2C Customer records map to Zoho Contact only. We use the Optimove CustomerID as a custom external ID field on Zoho Contact for deduplication and later cross-referencing. The split rule is defined during discovery based on whether the Customer has an associated company field or is individual-only.

Optimove's custom attributes (subject to the 50-attribute total limit) map to Zoho CRM custom fields on the Contact and Account modules. We audit the current attribute count during discovery to confirm it falls within Zoho's 300-field-per-module capacity, which it almost always will. Attributes added via Optimove's real-time API are imported via Zoho's API using UpdateRecord after the initial bulk load. Zoho field types are selected by data type matching: string attributes to text fields, numeric attributes to numeric fields, date attributes to date fields, and categorical attributes to picklist fields.

Optimove Lifecycle Stage assignments migrate to a Zoho CRM custom picklist field on Contact. Stage names are preserved verbatim, and the customer's Lifecycle Stage transition history migrates as a secondary custom field (Last_Lifecycle_Transition_Date__c) or as related activity records. Zoho does not have a native Lifecycle Stage equivalent; we configure the picklist values during schema setup so that the customer's existing stage names appear in Zoho without requiring re-entry.

Optimove's proprietary OptiGenie AI predictive scores and next-best-action recommendations are exported as raw numeric values from Optimove's Data Share and migrate to custom numeric fields in Zoho CRM. These values are not recalculated in Zoho; Zia's AI features provide new scoring after go-live. We clearly flag during discovery that predictive model confidence intervals, recalibration mechanisms, and the underlying model logic are Optimove-specific and cannot be migrated. Customers relying heavily on predictive decisioning should plan for a model rebuild period using Zoho's Zia or a third-party scoring tool.

Optimove Target Groups (dynamic customer segments built from attribute rules) are exported as membership lists linked to CustomerIDs. We migrate the membership lists to Zoho CRM Views (saved filters) with the underlying criteria documented as Zoho filter rules. Complex nested attribute rules are translated into Zoho's Advanced Filters, which support multi-condition grouping. Segment names migrate as View names for immediate usability. Zoho does not have an equivalent to Optimove's real-time segment recalculation; Views refresh on demand.

Optimove campaign metadata (name, type, channels, schedules, audience sizes) migrates to Zoho CRM Campaigns. Campaign status and type fields are mapped from Optimove's campaign state. We preserve historical campaign performance data (sends, opens, clicks, conversions) as related Campaign metrics or as a custom object for reporting continuity. Optimove's visual journey canvas and orchestration rules have no portable export format and are documented separately for manual recreation in Zoho.

Optimove email engagement history migrates to Zoho CRM Email Records linked to the parent Contact. Email subject, body, timestamp, and send status transfer directly. Engagement metrics (open, click, bounce) migrate as custom fields on the Email record. Zoho's Email module supports linking to Contacts and Accounts; we resolve the parent Contact reference via the Optimove CustomerID during import.

Optimove call and meeting engagement records migrate to Zoho CRM Activities. Call duration, disposition, and meeting start/end times migrate as activity fields. Location and attendee data for meetings migrate as Event fields. Activity timestamps are preserved from the original Optimove engagement date to maintain the activity timeline ordering that sales reps rely on.

Optimove Control Group membership assignments migrate as a custom field on the Zoho CRM Campaign module (Control_Group__c with a checkbox or multi-select picklist). Control group percentages and performance delta data migrate to Campaign custom fields for post-migration ROI calculation. Zoho does not have a native control group feature, so we implement it as a configuration using Zoho's custom field capabilities.

Optimove structures customer data by brand or customer network, potentially with separate schemas per network. We create a custom Brand__c module in Zoho CRM to represent each network, and tag Customer records with the appropriate brand reference. If Optimove networks have independent attribute schemas, we normalize them during the extract phase and map to the unified Zoho field structure. Brand-level campaign and engagement data routes to the corresponding Campaign records tagged with the brand reference.

Optimove user accounts and roles are listed via the platform admin interface and migrate to Zoho CRM Users. Role permissions and access levels require manual recreation because Optimove's permission model is proprietary. We export the role assignment matrix and deliver it as a Zoho permission role mapping document for the customer's admin to implement post-migration. Active users are imported first; inactive users are held in a reconciliation queue for provisioning.