Migrate from Ometria to Zoho CRM

Ometria Contacts are the unified customer profile consolidating ecommerce, POS, loyalty, and campaign data. We map Ometria Contacts with a lifecycle stage indicating active purchase intent to Zoho CRM Contact attached to an Account. Ometria Contacts representing early-stage prospects without an established account relationship map to Zoho CRM Lead. The split rule is defined during scoping based on the customer's lifecycle stage matrix and any purchase history indicators. Original Ometria lifecycle stage is preserved in a custom field ometria_lifecycle_stage__c for audit and reporting continuity.

Ometria Segments are rule-based dynamic groups that update automatically as customer data changes. Zoho CRM does not have an equivalent dynamic segment object; instead, we migrate segment memberships as Tags applied to Lead and Contact records, and where segment logic represents a stable customer attribute (VIP, loyalty tier, purchase category), we translate it to a Zoho multi-select picklist custom field. Segment definitions and rule logic are documented in a written handoff for the customer's admin to rebuild as Zoho Workflow filters or Blueprint stages.

Ometria Lifecycle Programs are multi-step automation journeys triggered by events or timing rules. These do not migrate automatically to Zoho because Zoho Workflow Rules use a different trigger and condition model. We export the full program structure including step order, trigger conditions, delay configurations, and conditional branches, and deliver a written inventory mapping each Ometria Lifecycle Program to an equivalent Zoho Workflow Rule configuration. The customer's Zoho admin rebuilds the automations post-migration.

Ometria stores customer attributes as dynamic properties on the profile (VIP flag, lifecycle stage, favorite brand, loyalty tier). We map these to Zoho CRM custom fields with appropriate field types: picklists for categorical attributes, checkboxes for boolean flags, date fields for consent timestamps, and text fields for arbitrary string values. Custom property type mapping (string, integer, boolean, date) is resolved during the schema design phase before any records are inserted.

Ometria Events capture customer actions such as order_placed, email_opened, page_viewed, and custom event types. Zoho CRM does not have a native behavioral event schema, so we translate Ometria event history into Zoho Tasks (for milestone events like order_placed) and Notes (for behavioral events like page_viewed and email_opened) linked to the parent Contact or Account record. Event property data migrates as note body text or custom Task fields. Event schema mapping is defined per event type during scoping.

Ometria Order records include purchase history, revenue attribution, and product line items. Zoho CRM does not have a native Order object at the standard tier; we map orders to Zoho Quotes (which capture product, quantity, and price) and attach order metadata as Notes on the associated Contact or Account. Revenue attribution data from Ometria migrates to custom fields on the Quote. Note that Ometria revenue figures may differ from external analytics by 15-20% due to Ometria's attribution model; we validate totals against Ometria's native reports rather than Google Analytics.

Ometria Broadcast Campaigns are one-time email sends to a list or segment. We migrate campaign templates (subject, body, and HTML) as Zoho Email Templates and deliver a written inventory of broadcast campaign history including send date, recipient count, and delivery metrics. Sending logs and individual delivery metrics migrate as separate export files. Zoho CRM Campaigns provide list management and response tracking but do not execute sends; the customer uses Zoho Campaigns or a third-party email platform for ongoing broadcast execution.

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 Zoho CRM Block List on the relevant Leads and Contacts, and set the HasOptedOutOfEmail field to true for GDPR and CAN-SPAM compliance continuity. Suppression reason codes are preserved in a custom field suppression_reason__c for audit purposes.

Ometria Stores represent individual retail locations integrated as data sources. We map store profiles to Zoho CRM Accounts with a custom field store_type__c set to 'Retail Location'. Location metadata (address, region, territory) migrates to standard Account address fields. Store-level customer associations migrate as custom multi-select fields on the Contact linking to the relevant store Accounts.

Ometria Subscribers are contacts with explicit opt-in status. Consent records are migration-critical for compliance. We preserve subscription status, consent timestamp, and opt-in source in custom fields on the migrated Zoho CRM Contact or Lead: consent_status__c, consent_date__c, and consent_source__c. HasOptedOutOfEmail maps from the Ometria unsubscribe status.

Ometria Coupon pools and promotion properties passed in events must be mapped as custom fields or Notes at the destination. We create coupon-related custom fields on the Contact or Account object (last_promo_code__c, promo_redemption_count__c) and attach coupon pool details as Notes with promotional metadata. Ometria's coupon sync configuration requires replication via destination platform settings post-migration.

Ometria Owner records (users assigned to contacts and campaigns) map to Zoho CRM User records resolved by email match. Any Ometria Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners are mapped to inactive Zoho Users to preserve assignment history.