Migrate from Ometria to Twenty CRM

Ometria Contacts map to Twenty CRM Person records. We map standard fields (email, firstName, lastName, phone, address properties) directly. Ometria custom dynamic properties migrate as Twenty custom fields, which we pre-create in the target workspace via the API before import. Consent records (opt-in status, consent timestamp, opt-in source) map to Twenty's optional workspace-level consent tracking or custom fields. Email address serves as the dedupe key during import.

Ometria Company records (from ecommerce or POS integrations) map to Twenty CRM Company records. Store locations that are modeled as Ometria Stores may map to additional Company records or to custom address fields depending on the customer's data model. The store name becomes the Company name; location metadata becomes address and custom fields.

Ometria Segments are dynamic rule-based groups. We export the segment definition (rule logic, conditions, membership count) and the membership list as CSV. The membership list migrates as a tag or custom multi-select field on Person records. Segment logic itself (if-then rule conditions) cannot be replayed in Twenty CRM and is documented for manual rebuild as filter views in Twenty's UI.

Lifecycle Programs are multi-step automation journeys with event triggers, delays, and conditional branches. Twenty CRM has no native automation engine equivalent. We export the full program structure (step sequence, trigger events, delay durations, conditional logic, and action types) as a written inventory document. The customer's admin rebuilds each program in a third-party automation tool (Brevo, Klaviyo, or an in-house system) or documents it for future implementation in Twenty.

Broadcast campaigns (one-time email sends to a list or segment) include template content, send configuration, and campaign history. We transfer broadcast template HTML as reference documentation. Sending logs and delivery metrics export as separate CSV files. The email execution layer (sending infrastructure, throttling, SPF/DKIM) does not migrate and requires a new sending domain configuration in the customer's chosen email platform.

Ometria suppression lists hold contacts blocked from email for compliance or deliverability reasons. We export the full suppression list and apply the email addresses as a block set in the destination email platform (Brevo, Klaviyo, or SendGrid) configured during migration. In Twenty CRM, suppressed contacts are flagged via a custom field or Person record tag to ensure they are not re-engaged without re-verification.

Ometria Events capture customer actions with customizable property schemas. We map event names and timestamps to Twenty CRM Activity records attached to the corresponding Person and Company. Event properties with structured values (revenue, product SKU, discount code) migrate as Activity custom fields or as notes on the Activity record. High-volume event types (page_viewed) are scoped to the last 12-24 months to manage API load and destination storage.

Ometria stores customer attributes as dynamic properties unique to each account (loyalty points, VIP flag, lifecycle stage, favorite brand). We audit the full property schema, map property data types (string, number, boolean, date, array) to Twenty's field type equivalents, pre-create all custom fields in the Twenty workspace, and import values as structured field data. Properties with array values (e.g., product preferences) map to Twenty multi-select custom fields.

Subscribers are contacts with explicit opt-in status. Consent records are migration-critical for GDPR and CAN-SPAM compliance. We preserve subscription status, consent timestamp, and opt-in source, mapping each to dedicated fields in Twenty. If the customer's destination email platform differs from Twenty's sending layer, consent records are also configured in that platform to ensure deliverability compliance is maintained post-migration.

Order records from Ometria (revenue attribution, product SKUs, discount codes) are mapped as custom fields on the associated Person or Company record, or as Opportunity records if the customer uses Ometria's order data for sales pipeline tracking. Revenue figures from Ometria may differ from Google Analytics by 15-20% due to different visit-counting and attribution logic; we flag this discrepancy and validate totals against Ometria's native reports during reconciliation.

Ometria Stores represent individual retail locations integrated as data sources. We migrate store profiles (name, location metadata, address) as Company records in Twenty CRM with a custom store-type field to distinguish them from customer companies. Store-level suppression rules and store-attribute associations migrate as additional fields on each Person record.

Ometria requires HTML templates to be copied specifically into a master template slot during account migration. We extract full HTML from the source account as a reference archive. Templates are not imported into Twenty CRM directly since Twenty does not include a native email template editor. We deliver the template archive to the customer's marketing team for re-insertion into their chosen email platform (Brevo, Klaviyo, or equivalent).