Migrate from Ometria to Freshsales

Ometria Contact profiles map to Freshsales Contact or Lead depending on lifecycle stage. Subscribers and early-stage contacts with no sales interaction map to Freshsales Lead. Customers, evangelists, and sales-engaged profiles map to Freshsales Contact tied to an Account. We preserve the original Ometria lifecycle stage in a custom field ometria_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity. Email address serves as the dedupe key across both objects.

Ometria custom properties such as loyalty_tier, favorite_brand, lifetime_value, and acquisition_source map to Freshsales custom fields of equivalent type. Multi-value properties (brand preferences, product interests) map to Freshsales multi-select picklists. We flag any Ometria property with a data type that has no Freshsales equivalent (for example, an array of JSON objects becomes a long-text field or a custom object relationship) and document the transformation in the field-mapping deliverable.

Ometria segments are dynamic rule-based groups. We export both the segment definition (the rule logic) and the snapshot membership list. Membership lists migrate as Freshsales Static Lists for immediate use. The segment definition itself is documented in writing as a recommended Freshsales Dynamic List or as a set of Workflow filter criteria that the customer's admin rebuilds in Freshsales. Segment logic referencing deprecated Ometria fields is flagged for manual cleanup.

Ometria suppression lists hold contacts blocked from receiving email for compliance or deliverability reasons. We export the full suppression list and apply it as a Freshsales Block List so that blocked contacts do not receive any Freshsales emails or sequences. Consent records (opt-in timestamp, opt-in source) are migration-critical for GDPR compliance and map to the Freshsales HasOptedOutOfEmail field and related consent custom fields.

Ometria order records include purchase history, revenue attribution, and order-level attributes. Since Freshsales does not have a native order object, we create a custom Order object with fields for order_id, order_date, total_amount, currency, items_json, and attribution_source. We also create a lookup relationship from Order to the parent Contact and Account so that order history appears in the Contact timeline via a related list. Revenue figures in Ometria may differ from Google Analytics by 15-20% due to different attribution logic; we flag this discrepancy and validate totals against Ometria's native reports rather than external analytics.

Ometria events (order_placed, email_opened, page_viewed, loyalty_redeemed) capture customer behavior across channels. Standard engagement events map to Freshsales Task records with a custom event_type__c field to distinguish between behavior types. High-volume behavioral events (page_viewed, product_viewed) are consolidated into a custom Event History object to avoid creating thousands of individual Task records that would inflate the activity timeline without sales value. Event schema is account-specific in Ometria, so we document the full event taxonomy during scoping and map each event type individually.

Ometria Lifecycle Programs are multi-step automation journeys with triggers, delays, and conditional branches. These do not migrate as automation code because Freshsales Workflows use a different trigger and action model. We export the full program structure including step sequence, trigger conditions, delay durations, conditional branches, and channel actions. The customer's Freshsales admin receives a written program inventory with recommended Freshsales Workflow equivalents for each program. Lifecycle program status (enrolled, exited, completed) migrates as a custom field on Contact for reporting continuity.

Ometria broadcast campaign templates and sending history migrate as Freshsales Email Templates with HTML preserved. Campaign sending logs and delivery metrics (opens, clicks, bounces) migrate as a custom Campaign Metrics object linked to the Contact. Broadcast cadence and timing rules are documented in writing for the customer's admin to reconstruct using Freshsales Workflows and Sales Sequences. Ometria's AI-driven audience selection (Architect product) has no Freshsales equivalent; we recommend rebuilding audience selection as Freshsales Dynamic Lists or Freddy AI-based scoring rules.

Ometria stores represent individual retail locations integrated as data sources. Store profiles with location metadata migrate as Freshsales Account records with address and custom store fields, or as a dedicated Store custom object if the customer requires store-level attribution separate from the sales Account. Store-level suppression rules migrate as Account-level Block settings.

Ometria coupon pools and promotion properties passed in events map to custom fields on the Order custom object. Coupon sync configuration (active coupons, redemption rules) requires replication at the destination via Freshsales custom fields or a third-party promotions integration. We flag coupon configuration for manual rebuild in the migration handoff documentation.