Migrate from Optimiser CRM to monday CRM

Optimiser CRM Contacts map to Monday.com CRM People entities. Standard fields (name, email, phone, address) map to Monday.com's built-in People columns. Optimiser custom fields on Contacts require individual review during scoping; we create equivalent custom columns in Monday.com and map values field-by-field. Fields with zero data across all records are excluded to avoid creating dead columns. The email field on People serves as the dedupe key during import.

Optimiser CRM Company records map directly to Monday.com CRM Companies. The company name becomes the Company entity name, and any associated domain or website data maps to the Company details columns. Company records are imported before People records so that any Person-to-Company association is resolved at the moment of Person insert.

Optimiser CRM Deals map to Monday.com CRM Deals with their associated pipeline stage, value, expected close date, and owner. Pipeline stage names from Optimiser (which are configurable per instance) map to Monday.com's Status column values on the Deals board. We apply a stage-mapping table during migration rather than assuming identical stage names. Closed-Lost and Closed-Won states from Optimiser map to Monday.com's Done group with the appropriate status label.

Optimiser's configurable pipeline stages become Monday.com's Pipeline boards with Status columns representing each stage. We extract the full stage list from Optimiser, map each stage to a Monday.com Status column value, and configure the pipeline view in Monday.com before Deal import begins. Stages with zero records in Optimiser are flagged and can be excluded from the Monday.com pipeline configuration.

Optimiser Lead records (with status, source, and score fields) map to Monday.com CRM People entities in a separate Leads section or filtered view. Monday.com does not have a distinct Lead object separate from People; we use a custom Status column or a separate board to distinguish pre-qualified Leads from qualified People. The customer's preference is captured during scoping and applied as a naming convention and filter.

Optimiser Activity records (calls, emails, meetings, tasks, notes) logged against Contacts or Deals migrate to Monday.com's activity timeline on the corresponding People or Deal entity. We import activities in chronological order and associate them to the correct parent record by matching the Optimiser contact or deal reference to the Monday.com entity ID. Note content migrates as Updates or as a linked Document column depending on volume.

Optimiser custom fields are instance-specific with no standard reference schema. Before migration, we request a field inventory from the customer or perform a trial export to enumerate every active custom field. We map each custom field to the nearest Monday.com column type (Text, Number, Date, Dropdown, Checkbox, etc.) and create the corresponding column in the destination before data import. Multi-select values from Optimiser map to Monday.com's Tags or Dropdown columns.

Optimiser User records carry name, email, and role. We map Optimiser users to Monday.com team members by email address to preserve owner assignment on Deals and to assign activities to the correct person in Monday.com. Users without an existing Monday.com account go to a reconciliation queue for the customer's admin to provision before record import resumes.

Document attachments referenced by URL in Optimiser migrate to Monday.com URL columns on the parent entity. Files stored in Optimiser's file store are downloaded locally, then re-uploaded to Monday.com as File column attachments linked to the correct People or Deal entity. File migration is performed after the parent record exists in Monday.com to ensure the association is satisfied.

Tags applied to Contacts or Deals in Optimiser export as label values. We migrate tags as-is and create matching Tags column sets in Monday.com CRM on the People and Deal entities. The customer chooses whether to create separate tag columns per entity or a single cross-entity tag taxonomy during scoping.