Migrate from Omni.us to Nutshell

Omni Target Accounts map directly to Nutshell Company records. Company name, domain, and any standard address fields transfer. The Target Account's domain field becomes the Company Website in Nutshell. Target Accounts serve as the dedupe key for subsequent Contact imports, so Companies are migrated first to satisfy the Account lookup required on Contact records.

Omni Responses have no standalone contact field—they link a prospect's reply to a Script and a Target Account. We extract contact details (name, email, phone) from the Response payload and resolve the target account reference to the Nutshell Company already migrated. Responses without extractable contact details go to a reconciliation queue for manual review. This reconstruction step is the highest-risk phase because Response payloads vary by configuration.

Omni Scripts carry outreach text, placeholders, and branching logic. Nutshell has no native Scripts object. We export script content as plain-text Note records attached to the originating Nutshell User or as Document records, preserving the full script body. Placeholder tokens and branching logic are not automatically recreated; we document the structure in a separate script inventory so the customer's admin can rebuild sequences in Nutshell Tasks or a connected sales engagement tool.

Omni Case Studies attach to accounts or scripts as content references. Nutshell does not have a native Case Study object. We export the case study text and metadata and attach it as a Note or Document record to the related Nutshell Company. If the case study contains file attachments, we migrate them as ContentDocument records linked to the Company.

Omni's three-layer model (schema, shared, workbook) means custom fields can exist at different abstraction levels. We perform a pre-migration schema audit via the Omni model IDE to enumerate all active custom fields, their types (text, numeric, duration, calculated), and their workbook scope. Each custom field maps to a Nutshell custom field of matching type on the corresponding object. Duration fields and calculated fields may require transformation or become read-only calculated fields in Nutshell.

Omni Automatic Pausing rules govern sequence pauses based on prospect actions. Nutshell's automation rules serve a similar purpose but use a different configuration model. We do not migrate these as executable workflow code. Instead, we document each Active Pausing rule with its trigger condition, pause duration, and associated script, and deliver a written guide for rebuilding in Nutshell's automation rules or tasks.

Omni user records map to Nutshell User accounts by email match. Role and permission structures are not natively present in Omni so we create baseline User records without granular access control preservation. The customer's Nutshell admin configures team roles and permissions post-migration.

Omni does not expose a dedicated Activities object in its API. We cannot migrate historical engagement activity records because the platform does not persist them as queryable objects. Any engagement timestamps present in Response records are preserved as metadata on the reconstructed Contact.