Migrate from Omni.us to Mailchimp

Omni.us Target Accounts map to a Mailchimp Audience with Member records created for each contact reconstructed from Responses. Company name from the Target Account becomes the Organization field on each Member record. If a Target Account has no associated Responses, we create one Member record using the account's primary contact data if available. Multiple Target Accounts do not merge into a single Mailchimp Audience; we preserve the account-level separation by tagging Members with their source account identifier.

Omni.us Scripts map to Mailchimp Campaigns or stored Templates, but the semantics differ significantly. Omni.us Scripts are outbound sales sequences with placeholders, branching logic, and cadence steps; Mailchimp Campaigns are marketing email sends without native sequence logic. We export script text and placeholder structures as Mailchimp Templates, preserving the body content for reuse. The cadence and branching logic cannot migrate as code—we document the sequence steps in a handoff sheet so the customer's admin rebuilds them as Mailchimp Customer Journeys.

Omni.us Case Studies are content attachments linked to accounts or scripts. Mailchimp has no native Case Study object. We export the text content and metadata as Mailchimp Custom Properties on the relevant Member records, prefixed with omni_case_study_. For richer content, we export as a structured HTML block deliverable that the customer uploads to Mailchimp Content Studio or attaches to a Campaign note. Case Study attachments (PDFs, images) migrate as Mailchimp uploaded files.

Omni.us Responses do not store contact records directly—they link a prospect's reply to a Script and Target Account. We reconstruct the contact layer by extracting reply email addresses, names, and timestamps from Responses, deduplicating by email, and importing as Mailchimp Members. Response metadata (reply date, script associated, account associated) migrates as custom properties on each Member record. Any contact not associated with a Response after deduplication is flagged in the reconciliation report for customer review.

Omni.us Custom Workbook Fields defined at the schema, shared, or workbook level discover during pre-migration audit. We map each custom field type (text, number, date, duration, calculated) to the closest Mailchimp Merge Field type. Duration fields convert to text-formatted values (e.g., PT30M becomes 30 minutes) since Mailchimp Merge Fields do not support duration types. Multi-select workbook fields map to Mailchimp interest groups or multi-value text properties depending on the customer's segmentation plan.

Omni.us User records map to Mailchimp Members representing the internal team, not the sales contacts. We create Member records with a tag admin_user for internal-facing records and preserve the user's name and email. Omni.us role and permission structures do not have a Mailchimp equivalent—Mailchimp's admin roles (Account Owner, Admin, Manager, Author, Viewer) are platform-level and not migrated.

Automatic Pausing Rules govern when Omni.us outreach sequences pause based on prospect actions (reply, open, bounce, meeting booked). Mailchimp has no native sales engagement cadence equivalent to Automatic Pausing. We export the rule logic (trigger condition, pause action, resume condition) as a written specification document. The customer's admin rebuilds these as Mailchimp Customer Journey triggers: reply-triggered pauses map to Tag-added automations, bounce-triggered pauses map to unsubscribebounce suppression rules. This inventory is delivered as part of the handoff documentation, not migrated as live rules.

Omni.us does not expose a dedicated Activities object in its API. Historical engagement activity records (opens, clicks, meeting completions logged as Omni activities) cannot be queried or exported because the platform does not persist them as queryable objects. We note this as a data loss boundary in the migration scope and surface it during discovery so the customer understands what will not appear in Mailchimp engagement history.