Migrate from Omni.us to Zoho CRM

Omni Target Accounts map directly to Zoho CRM Accounts. We preserve company name, domain, and any workbook-level custom fields as Zoho custom fields on Account. Address data (street, city, state, country) migrates to Account Address fields if present in Omni; otherwise the fields are left blank and flagged for the customer's admin to enrich post-migration. Accounts are the first records imported because Contacts, Opportunities, and Notes all require an AccountId lookup.

Omni does not store contacts as standalone records — the contact layer must be reconstructed from Response objects by tracing the email address, name, and phone associated with each response back to the parent Script and Target Account. We deduplicate by email to create one Zoho Contact per unique prospect, then link the Contact to the corresponding Account. Response metadata (reply date, channel, disposition) migrates as custom fields on the Contact record. Prospects with no response history but present in a Target Account receive a Contact record with no engagement history.

Omni Scripts have no native Zoho equivalent. We create a custom Zoho CRM module called Omni Scripts with custom fields for script text (Notes type), placeholder fields (text), branching logic (multi-select picklist or text), and sequence order (number). The script content is preserved verbatim as a rich text field so that sales ops can reference it during the Zoho onboarding process. This is a reference migration, not a live integration — scripts are not executed inside Zoho.

Omni Case Studies are content attachments linked to accounts or scripts. We export the text content and metadata and store them as file attachments on the corresponding Zoho Account record. If the Case Study is script-linked rather than account-linked, we attach it to the Account associated with the primary Target Account for that script. Zoho's 5 MB per-file limit applies; Case Studies exceeding this are stored as Zoho Notes with a link to the external document store.

Omni Automatic Pausing Rules govern when outreach sequences pause based on prospect actions (reply, open, bounce, opt-out). We convert these into Zoho Workflow Rules scoped to the Contact and Account modules. The trigger condition (reply, open) maps to a Zoho Workflow trigger on field update or specific field criteria. The action (pause sequence) maps to a Zoho Workflow task assignment or Blueprint stage change. We document the full rule logic in the automation inventory so the customer's admin can validate and extend in Zoho Workflow Builder.

Omni's three-layer modeling (schema, shared, workbook) means custom fields can exist at different abstraction levels. We perform a pre-migration field audit against the Omni model IDE to enumerate all active custom fields and their types, then create matching Zoho CRM custom fields on the appropriate module. Duration fields, calculated fields, and nested custom properties receive special handling: Duration maps to Zoho Number fields with a unit designation in the field name; calculated fields are not migrated as live formulas but as static values with a note that the admin should rebuild the calculation in Zoho Formula fields post-migration.

Omni user records map to Zoho CRM Users by email address. We import the Omni user list and create Zoho Users with matching email and name. Role and permission structures are not natively present in Omni so we create baseline User records without granular access control preserved. The customer's Zoho admin assigns roles (Standard, Professional, etc.) and profiles post-migration. Any Omni user not yet provisioned in Zoho is held in a user reconciliation queue.

Omni Response records carry engagement metadata (reply timestamp, channel, body excerpt) that maps to both a Zoho Task record (for the activity timeline) and a Note record (for the reply content). The Task gets TaskSubtype = Email, Activity Date set to the response timestamp, and a link to the Contact and Account. The Note stores the full reply body as rich text. This split preserves the activity timeline view in Zoho while retaining the full response content for rep reference.

The link between a Response and its parent Script has no native Zoho equivalent. We preserve this relationship by attaching a Note to the migrated Contact that lists the scripts that generated the outreach. The Note includes script name, send date, and script version so that sales reps can reference the outreach context without a live sequence tool inside Zoho. This is a reference reconstruction, not a live sync.

Omni Target Accounts may carry tags or custom properties that serve as segmentation markers. We migrate these as Zoho CRM multi-select picklist fields on the Account module. The customer chooses during scoping whether to use native Zoho Tags (applied via the Tag function) or a dedicated picklist field for structured segmentation. Unstructured free-text tags that do not map to a defined picklist value are added as Zoho Tags on the Account record.