Migrate your Ometria data

Contacts are the central profile object in Ometria, consolidating data from ecommerce, POS, loyalty, and campaign sources into a single customer view. We migrate all standard contact fields and custom properties, preserving identity resolution links and consent records.

Segments are rule-based dynamic groups that update automatically as customer data changes. We export segment definitions and membership lists via CSV or XLSX. Note that segment logic referencing deprecated fields may require manual recreation at the destination.

Lifecycle Programs are multi-step automation journeys triggered by events or timing rules. We export program structure and step configurations but automation triggers, delays, and conditional branches often require field-level mapping to match destination syntax.

Broadcast campaigns are one-time email sends to a list or segment. We transfer broadcast templates and campaign history. Sending logs and delivery metrics migrate as separate export files; individual engagement events may not transfer 1:1.

Events capture customer actions such as order_placed, email_opened, or page_viewed. Event schema is customizable per account. We map event names and property structures, flagging any events with non-standard payloads for manual review.

Customer attributes are stored fields on a profile such as VIP flag, lifecycle stage, or favorite brand. Custom properties require field-type mapping since destination systems use different property type conventions (boolean, string, array, date).

Master templates store reusable HTML for campaigns. The account migration guide requires copying HTML code as a master template specifically; we extract and re-insert HTML directly and verify rendering post-import. Dynamic content blocks may require reconfiguration at the destination.

Suppression lists hold contacts blocked from receiving email for compliance or deliverability reasons. We export the full suppression list and apply it as a block set at the destination to ensure GDPR and deliverability continuity.

Coupon pools and promotion properties passed in events must be mapped as custom fields or properties at the destination. Ometria stores coupon sync configuration that requires replication via destination platform coupon management.

Order records include purchase history, revenue attribution, and attribution model data. Revenue figures in Ometria may differ from Google Analytics by 15-20% due to different attribution logic; we flag this discrepancy and migrate both raw order data and attributed revenue separately.

Stores represent individual retail locations integrated as data sources. We migrate store profiles, location metadata, and any store-level customer associations. Store-level suppression rules also transfer.

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, mapping to destination subscription fields.

Visit data captures customer onsite behavior including page views and session duration. Ometria counts visits differently than Google Analytics due to different attribution models. We migrate visit event logs where volume permits; high-traffic accounts may require sampling or summary-level migration.

Ometria supports customized data exports to AWS S3, Databricks, Google Cloud, Azure, and SFTP endpoints. We configure export connectors or use Databricks connections for bulk migration of custom datasets that do not map to standard objects.