Migrate from Ometria to Nutshell

Ometria Contact profiles map to Nutshell Person records. Standard fields (name, email, phone, address) migrate directly. Custom fields on Ometria contacts (up to 100 per account including archived) map to Nutshell custom fields, which are available on all Nutshell plans but have limits that vary by tier (Enterprise includes unlimited custom fields). We extract the full custom field schema from Ometria during discovery, classify each by data type (string, integer, date, boolean, list), and provision equivalent Nutshell custom fields before import. Ometria's dynamic contact properties such as VIP flag, lifecycle stage, or favorite brand migrate as text or enumerated custom fields in Nutshell.

Ometria stores (individual retail locations integrated as data sources) and company-level profiles map to Nutshell Account records. Store location metadata (address, region, store code) migrates as standard Account address fields or custom fields. If Ometria stores are used to tag individual contacts with a retail location affiliation, we create a lookup or custom field in Nutshell to preserve that association. Account is created before Person import so that the Account-Person relationship is satisfied at insert time.

Ometria dynamic segments are rule-based groups that update automatically; segment membership at migration time is captured as a static snapshot and can be recreated in Nutshell as a List. Segment definitions (the rules themselves) cannot migrate because Nutshell does not have a native dynamic segment engine. We export the segment name, member count, and rule definition logic, then deliver a written segment inventory documenting each Ometria segment and its equivalent Nutshell List or CRM filter. The customer's admin rebuilds the logic in Nutshell as static Lists or saved filters.

Ometria Lifecycle Programs are multi-step automation journeys triggered by events or timing rules. Nutshell's automation engine (part of the Engagement Suite) supports record-triggered and time-based automations, but the trigger model differs: Ometria triggers on behavioral events (order_placed, page_viewed) while Nutshell automations trigger on CRM record events (Person created, Deal stage changed). We export Lifecycle Program structure and step configurations as a written inventory. Each program's trigger, conditions, delays, and conditional branches are documented with a recommended Nutshell Automation equivalent. The customer's admin rebuilds journey logic in Nutshell; we do not migrate automation code.

Ometria broadcast campaigns are one-time email sends to a list or segment. We transfer broadcast campaign history (send date, recipient count, subject line) as metadata records. Campaign templates in HTML migrate as content that must be re-created in Nutshell's template builder. Sending logs and delivery metrics (opens, clicks, bounces) are exported as separate data files and can be stored as notes or attachments in Nutshell but do not appear as native analytics in the CRM reporting layer. Nutshell's Engagement Suite provides email campaign analytics natively.

Ometria events capture customer behavioral data with customizable schemas. Nutshell does not have a native behavioral event store. We map events to Nutshell Activity records where semantically appropriate: Order events can create Nutshell Activities with order reference in the description; email engagement events (opened, clicked) map to Activity records tied to the Person; page view events do not have a native Nutshell equivalent and are exported as a data file for BI tooling or discarded depending on customer preference. Event property data (revenue, product SKUs, discount codes) migrates as custom fields on the related Person or Deal.

Ometria order records contain 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 validate totals against Ometria's native reports during reconciliation. Each historical order maps to a Nutshell Deal with the order reference as Deal name, order total as Deal amount, and order date as the close date. Product line items from Ometria orders map to Deal Line Items in Nutshell if the Engagement Suite's quoting feature is active.

Ometria suppression lists hold contacts blocked from email for compliance or deliverability reasons. We export the full suppression list and apply it to Nutshell's email blocklist during migration. This step is compliance-critical: GDPR-suppressed contacts and bounce-suppressed addresses must be blocked in Nutshell before any outbound email send to prevent deliverability violations and legal exposure. Suppression list application is one of the first actions taken at the destination before any contact import.

Ometria master templates are reusable HTML blocks for campaigns. Nutshell's template builder uses a visual drag-and-drop editor rather than raw HTML import. We extract full HTML from Ometria master templates and deliver the source files to the customer's admin. The HTML must be rebuilt as Nutshell templates manually using the visual builder or with developer assistance to adapt the HTML structure. Dynamic content blocks and personalisation tokens (first_name, product_name, etc.) require separate reconfiguration in Nutshell's template variable system.

Ometria 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 (origin channel or form) by mapping to Nutshell's email opt-in field on Person records. Consent history beyond the current status migrates as a custom field or note attachment since Nutshell's standard model supports a single opt-in flag. Any contact on an Ometria suppression list is flagged as opted-out in Nutshell before the first send.