Migrate from Omni.us to Freshsales

Omni Target Accounts map directly to Freshsales Account records. Company name, domain, and any associated metadata map to Freshsales standard Account fields. The Target Account domain is used as the dedupe key during import to prevent duplicate Accounts. Target Account status (active/paused) migrates as a custom picklist field account_status__c on Account.

Omni Responses do not contain standalone contact records. We reconstruct the contact layer by extracting name and email from each Response, linking it back to the associated Script and Target Account. If a Response references an email address not yet seen, we create a Contact record; if the email already exists from a prior Response, we update it with the latest response metadata. This means contacts without associated Responses in the migration window will not appear in Freshsales unless they are added manually or matched from another source. We run a reconciliation pass post-migration to identify contacts present in Omni user records but missing from the Response-linked set.

Omni Scripts map to either Freshsales Notes (if the customer wants script content in the Contact/Account activity timeline) or a Custom Object named Script (if they want script records as standalone objects with their own list view and relationships). We discuss the preferred strategy during scoping. Script text, placeholders, and branching logic migrate as rich text fields. Scripts are written after Accounts and Contacts are in place so that any relationship fields can be resolved at insert time.

Omni Case Studies are content attachments linked to accounts or scripts. Freshsales has no native Case Study object. We map Case Study text content and metadata to either Freshsales Notes (linked to the associated Account) or a Custom Object named Case_Study with fields for title, content_body, and related_account_id. The customer selects the strategy during scoping. Case Studies with file attachments migrate those files as Freshsales file records linked to the parent object.

Omni Automatic Pausing rules govern sequence pause triggers based on prospect actions. Freshsales Workflow Automator handles similar logic with triggers on record creation, field change, or time-based conditions. We do not migrate Automatic Pausing rules as code. Instead, we audit every pausing rule in Omni, document its trigger condition, associated script, and pause duration, and deliver a written Workflow inventory with step-by-step instructions for rebuilding each rule in Freshsales Workflow Automator. The customer admin or a Freshsales partner implements the rebuilds post-migration.

Omni custom workbook fields exist at schema, shared, and workbook abstraction levels. We perform a pre-migration field audit via the Omni schema model to enumerate all active custom fields and their data types. Duration fields, calculated fields, and nested custom properties require type mapping to Freshsales field equivalents. Custom fields with the same name and type as Freshsales standard fields can import directly; non-matching fields require custom field creation in Freshsales before migration begins. We create the destination custom fields during the schema provisioning phase.

Omni user records map to Freshsales User records by email match. Role and permission structures in Omni are not granular, so we create baseline User records without preserving fine-grained access control settings. Any user in Omni without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before Contact and Account migration resumes.

Omni does not expose a dedicated Activities object in its API. Historical engagement activity records cannot be migrated because the platform does not persist them as queryable objects. We flag this gap in the migration report and recommend that the customer's Freshsales admin enable Freshsales built-in activity tracking from the cutover date forward. Any Response metadata (reply timestamp, channel) that exists in Omni Response records migrates as custom fields on the reconstructed Contact.