Migrate from Ometria to monday CRM

Ometria Contact profiles map to Monday.com CRM People records. The contact's email address becomes the primary identifier and dedupe key. Standard fields (name, email, phone, address) map directly. Custom customer attributes stored as dynamic properties on the Ometria profile migrate to Monday.com custom fields, using field-type mapping (text properties to text fields, numeric to number fields, dates to date columns, booleans to checkbox columns). Ometria's subscription status and consent timestamp map to Monday.com People email subscription properties.

Ometria stores company data as attributes on Contact records rather than as a separate object. If the source account includes explicit company records or uses the ecommerce integration to pass company context, we extract these and map them to Monday.com Organizations. The Organization is created before Contact migration so that the People-Organization lookup is satisfied at insert time. If no company data exists, we create placeholder Organizations from the contact's email domain as a dedupe and grouping strategy.

Ometria Segments are rule-based dynamic groups. We export segment definitions and the full membership list per segment. At Monday.com, we create Tags matching segment names and apply them to People records based on membership. Dynamic re-evaluation of segments (updating automatically as customer data changes) does not replicate; Tags are static snapshots at migration time. The customer can rebuild dynamic segment logic in Monday.com using filtered Views or automation triggers.

Order records from Ometria include purchase history, revenue attribution, and product associations. We map order summary data (total spend, order count, last order date, average order value) to custom fields on the People record. For detailed order line items, we create a separate Orders Board in Monday.com with Items representing each order, linked back to the People record via a Connect Boards column or a text field holding the customer email. Revenue figures in Ometria may differ from external analytics by 15-20% due to Ometria's attribution model; we flag this discrepancy before cutover.

Ometria stores customer properties such as VIP flag, lifecycle stage, favorite brand, and loyalty tier. We map each property to a Monday.com custom field of the matching type. Boolean properties (VIP flag) become checkbox columns; numeric properties (lifetime value) become number columns; text properties become text columns; date properties become date columns. Properties that reference other objects (e.g., preferred store) are mapped as text fields with the reference value stored directly.

Ometria suppression lists hold contacts blocked from email for compliance or deliverability reasons. We export the full suppression list and apply the suppressed status to the corresponding People records in Monday.com as a People property (e.g., Email Status = Undeliverable or Suppressed). This preserves GDPR compliance by ensuring migrated records maintain their suppression status at the destination. We validate that suppressed contacts are excluded from any People import batch sent to Monday.com.

Ometria Subscribers are contacts with explicit opt-in status. We preserve subscription status, consent timestamp, and opt-in source as People properties in Monday.com. Opt-in source (e.g., website form, in-store signup) is stored as a text field since Monday.com does not have a native opt-in source column. Consent records are migration-critical for compliance and are mapped to the People record's subscription status field.

Ometria Events capture customer actions (order_placed, email_opened, page_viewed). We map high-value behavioral events (purchase events, subscription changes, loyalty milestones) to custom fields or Activity log entries on the People record. Routine events (page views, session starts) are not individually migrated due to volume; we preserve summary metrics (total events, last event timestamp) as custom fields on the People record. Event schema is account-specific in Ometria, and we flag any non-standard event properties that require custom field creation in Monday.com.

Ometria Store records represent retail locations integrated as data sources. If the migration includes store-level attribution, we map stores to Monday.com Organizations (named by store) or to a text field on People records storing the primary store reference. Store-level suppression rules also transfer as part of the suppression list migration.