Migrate from Ometria to Mailchimp

Ometria Contact profiles map to Mailchimp Audience members by email address. We preserve standard fields (first name, last name, email) and custom contact properties as Mailchimp merge fields (FNAME, LNAME, plus custom merge tags). Consent timestamp and opt-in source migrate to Mailchimp's subscription tracking fields. Ometria's dynamic contact properties (lifecycle stage, VIP flag, favorite brand) become static merge fields at migration time; ongoing updates require re-sync via Mailchimp API or manual updates.

Ometria rule-based Segments map to Mailchimp Groups (for categorical membership such as loyalty tier or location) or Tags (for behavioral or event-based classification such as abandoned_cart or recent_purchaser). We export segment definitions as logic documentation and apply membership lists as Tag imports at migration time. Note that Ometria's dynamic segments that update automatically on data change require Mailchimp Customer Journey triggers or manual re-tagging to recreate; static segment snapshots migrate as one-time tag applications.

Ometria Lifecycle Programs (multi-step automation journeys with event triggers, delays, and conditional branches) do not migrate automatically. Mailchimp Customer Journeys support trigger-based flows but have different conditional logic and action types. We export the full program structure including step order, trigger conditions, delay durations, and branch rules as a written inventory document. The customer's admin rebuilds each program in Mailchimp's automation builder using the documented logic. Program abandonment triggers and predictive scoring steps have no direct Mailchimp equivalent.

Ometria broadcast campaign templates and campaign history (campaign name, send date, subject line, audience size) migrate as documentation. Campaign HTML content extracts from Ometria and recreates in Mailchimp's campaign editor. Sending logs, delivery metrics, and open/click data export as separate CSV files for the customer's historical reference but do not populate Mailchimp's native reporting; those metrics live in Ometria and are not transferable.

Ometria suppression lists (contacts blocked from email for compliance or deliverability reasons) migrate as Mailchimp suppressed contacts via CSV import. We export the full suppression list including email address and suppression reason, then import as a Mailchimp suppression file. This ensures GDPR and CAN-SPAM compliance by preventing bounced, unsubscribed, or blocked addresses from receiving email in the new Mailchimp account. Suppression data must be imported before any audience send to avoid compliance violations.

Ometria custom contact properties (VIP flag, favorite brand, loyalty status, lifecycle stage) map to Mailchimp merge fields. We assess each property's data type during scoping: string and numeric properties become text or number merge fields; boolean flags become text merge fields with yes/no values; date properties become date merge fields. Mailchimp's merge field type support is limited compared to Ometria's flexible property schema, so complex nested or array-type properties map as text fields with serialized values. Tags serve as an alternative for categorical custom attributes where merge field limits are a concern.

Ometria Master Template HTML extracts from the source account and inserts into Mailchimp's template editor. Per Ometria's account migration guide, HTML must be copied specifically into a master template slot at the destination; we extract full HTML, recreate as Mailchimp Saved Templates, and run visual QA across desktop and mobile previews. Dynamic content blocks and personalisation tokens from Ometria require reconfiguration in Mailchimp using Mailchimp's own personalization syntax. Regular template slots in Ometria do not transfer via account migration and must be manually recreated.

Ometria order records (purchase history, revenue attribution, order total, items) can map to Mailchimp's Ecommerce integration if the destination Mailchimp account has an active store connection (Shopify, WooCommerce, Magento). For orders without an active store integration, we map order summary data to custom merge fields on the contact record (last_order_date, total_lifetime_value, order_count). Note that Ometria's revenue attribution figures may differ from Google Analytics by 15-20% due to different visit-counting logic; we flag this discrepancy in the reconciliation report and do not use Ometria financial totals as the authoritative source for revenue reporting at the destination.

Ometria event schema (order_placed, email_opened, page_viewed, and custom account-specific events) cannot migrate as structured behavioral data because Mailchimp does not maintain a per-contact event history store. We map the most recent or most significant event states to Tags (abandoned_cart = true, has_purchased = true) or merge fields for use in segmentation and automation triggers. The full event timeline and event property details are not transferable. Events with non-standard schemas require field-type mapping and may need customer admin sign-off on the simplification approach.