Migrate from Ometria to Pipedrive

Ometria Contact profiles map to Pipedrive People records. The contact's email address is the dedupe key. Standard fields (name, email, phone, address) migrate directly. Ometria's dynamic contact properties (VIP flag, lifecycle stage, favorite brand) become custom fields in Pipedrive. We flag which Ometria properties are deprecated (those referencing de-activated ecommerce sources) and exclude them from migration.

Ometria Company records map to Pipedrive Organizations. Ometria's company-level attributes (industry, annual revenue, employee count) become custom fields on the Organization. We resolve the link between Ometria Contact and Company via the contact's associated_company_id property and create the Organization record before the Person record so that the organization_id field is satisfied at Person insert.

Ometria Order records map to Pipedrive Deals. Each order generates a Deal with the order total as the Deal value, order date as the Activity date, and order status as a custom field. If a Contact has multiple orders, we create multiple Deals and link each to the same Person and Organization. Order line items, product SKUs, and discount codes become custom fields on the Deal. Note that Ometria's revenue attribution (which may differ 15-20% from Google Analytics) migrates as-is with a flag for reconciliation.

Ometria segments are dynamic rule-based groups that update automatically; Pipedrive has no equivalent native dynamic segment. We export segment membership as a list of contact email addresses and deliver this as a CSV for your Pipedrive admin to create as static lists, Person tags, or Lead Rotations. The segment logic (rules and conditions) is documented separately for rebuild in Pipedrive Workflows or a third-party segmentation tool.

Ometria Lifecycle Programs are multi-step automation journeys with triggers, delays, and conditional branches. Pipedrive Workflows are record-action automations scoped to CRM events (deal stage change, activity creation, field update). There is no direct equivalent to Ometria's journey builder. We export the full Lifecycle Program structure (trigger, steps, conditions, delays, actions) as a written inventory document. Your Pipedrive admin or a Pipedrive partner rebuilds the logic in Pipedrive Workflows or an external automation tool. Lifecycle Programs do not migrate as executable code.

Ometria Broadcast Campaigns are one-time email sends to a segment. Pipedrive Campaigns are mailing list groups for tracking email opens and clicks but do not handle sending themselves (Pipedrive relies on an integrated ESP). We export campaign metadata (name, send date, subject, segment, template used) and delivery metrics (sent, opened, clicked). The customer configures their email integration (Mailchimp, HubSpot Marketing, or similar) and rebuilds the campaign sends in that platform.

Ometria stores dynamic properties on each contact profile. We map each Ometria property to a Pipedrive custom field of the matching type: string properties map to text fields, dates map to date fields, numeric properties (order count, lifetime value) map to numeric fields, boolean properties (is_vip) map to boolean/toggle fields, and enumerated properties map to picklist fields. We validate the field type conversion before creating the Pipedrive fields and flag any properties with non-standard characters in the API name that require sanitization.

Ometria suppression lists hold contacts blocked from receiving email for compliance or deliverability reasons. These migrate to Pipedrive's Blocklist (global email blocklist) to ensure migrated contacts do not receive unintended email after cutover. Suppression records include email address, suppression reason (bounce, unsubscribe, complaint), and suppression date. We preserve the reason as a custom field on the blocklist entry and the date for compliance audit trail.

Ometria Store records represent retail locations integrated as data sources. Pipedrive has no native store or location object. We map store data to Organization custom fields (store code, store region) or a custom Organization field set. Store-level suppression rules migrate as additional blocklist entries tagged by store origin.

Ometria Subscribers are contacts with explicit opt-in status. Consent records are migration-critical for GDPR and CAN-SPAM compliance. We preserve subscription status (subscribed, unsubscribed, bounced), consent timestamp, and opt-in source (ecommerce form, in-store, loyalty program). These map to Pipedrive Person fields with HasNoEmailAddress, Campaign Member status, and a custom consent_source field for compliance records.

Ometria Events capture customer actions (order_placed, email_opened, page_viewed). Pipedrive Activities are CRM-level events tied to People and Deals. We map high-value Ometria events to Pipedrive Activities: order_placed events become Deal-linked Tasks, email_opened events become Person-linked Tasks with activity type = email. Low-frequency behavioral events (page_viewed, product_viewed) are summarized as custom fields on the Person rather than individual activity records to avoid flooding the Pipedrive timeline.

Ometria Master Templates store reusable HTML for campaigns. Pipedrive does not have a native email template builder (it integrates with external ESPs for email delivery). We export template HTML from Ometria and deliver it to the customer for re-insertion into their chosen email platform (Mailchimp, HubSpot, Klaviyo, or similar). The template must be copied as HTML code specifically into a master template slot per Ometria's account migration guide; we flag this for manual handling during the cutover window.