Migrate from Omni.us to monday CRM

Omni Target Accounts map directly to Monday.com CRM Company records. Company name, domain, and custom properties migrate to the corresponding Company fields. The Company record is the first object we write because every Contact in Monday.com CRM must have a Company association, and this satisfies the parent-record lookup before Contact import begins.

Omni Scripts map to Monday.com board Items on a dedicated Scripts board. The script text, placeholders, and branching logic preserve in rich-text columns on the Item. Placeholder field names migrate as a separate text column so that reps can see which fields are available for personalization. The board can be organized by Script type or campaign using Monday.com Groups.

Omni Responses carry no standalone contact record—contact information exists only within the Response payload linked to a Script and Target Account. We reconstruct the Contact layer by extracting name and email from each Response, deduplicating by email across all Responses, and creating one Contact record per unique email. The Contact is linked to the Company derived from the associated Target Account. Responses with no name or email surface as orphaned records and are flagged in the reconciliation report for manual review.

Omni Case Studies are content attachments linked to accounts or scripts. We export the text content and any file attachments and link them to the corresponding Monday.com CRM Company record or Scripts board Item via the Monday.com Files integration. Monday.com does not have a native Case Study object, so the content migrates as a file attachment with a description column capturing the text.

Omni Automatic Pausing rules govern when outreach sequences pause based on prospect actions. We translate these into Monday.com Automation Recipes scoped to the Scripts board. The trigger (prospect reply, email open, link click if tracked) maps to a Monday automation trigger, and the action (pause sequence) maps to the corresponding automation action. The customer rebuilds these in Monday.com's no-code automation builder from our written recipe inventory.

Omni Custom Workbook Fields exist at schema, shared, or workbook levels and include types such as text, number, date, duration, and calculated fields. We discover all active custom fields via the Omni model IDE during scoping, then map each to a typed Monday.com board column. Duration fields from Omni convert to number columns with an appended unit descriptor. Calculated fields that depend on other Omni fields may require a Monday.com formula column or a manual calculation note for the customer.

Omni user records map to Monday.com User accounts. We resolve by email match against the Monday.com destination workspace. Omni does not store granular role or permission structures, so we create baseline Monday.com User records without specific permission-set assignments. The customer's Monday.com admin assigns seat types and board permissions post-migration.

Omni does not expose a dedicated Activities object in its API. Historical engagement records (calls, emails, meetings, tasks) cannot be exported because the platform does not persist them as queryable objects. We flag this gap in the pre-migration data audit and document it in the handoff report. Future activities will be logged natively in Monday.com CRM from the migration cutover date onward.