Migrate from Opal CRM to monday CRM

Opal CRM Leads map to Monday.com CRM Contacts. Source attribution (form, upload, campaign) migrates as a custom column on the Contact board. We preserve any lead score or status fields as custom columns. Monday.com CRM Contacts are items on the Contacts board with linked Deals and Companies. If Opal CRM stores leads without a company association, we create placeholder Company records first so the Contact-Company relationship is satisfied during import.

Opal CRM team members (Admin, Manager, Sales Rep roles) map to Monday.com User accounts. Role permissions from Opal CRM do not export as structured data, so we capture the role assignment per user and document the mapping so administrators can reconfigure equivalent access levels in Monday.com's User management panel. Active users migrate first; inactive or suspended users are held in a reconciliation queue.

Tour Plans store field-sales itineraries with dates, locations, and expense line items. Monday.com has no native Tour or Visit object, so we create a dedicated Tour board and map itinerary data (dates, locations, assigned rep) to board columns. Individual expense entries that may have flattened during Opal CRM's manual export are reconstructed as child items or separate Expense group items within the Tour board. We flag any truncated expense values for manual review and deliver a written inventory of all Tour Plan records for the customer's admin to finalize board configuration.

Opal CRM Quotations map to Monday.com CRM Deals with custom columns holding line-item data. The quotation header fields (total amount, validity date, customer reference) migrate directly. Line items are stored as a linked subitems structure or as JSON-formatted text in a custom column depending on the target board configuration. Opal CRM's internal quotation workflow approval state has no Monday.com equivalent, so we capture the workflow status as a custom Status column and document it in handover notes for the admin to rebuild as a Monday.com automation if needed.

Opal CRM tracks lead progress through pipeline stages. Stage names and order are mapped to Monday.com Deal board Status column values. The probability associated with each stage is stored as a separate Probability column on the board. If Opal CRM uses custom stage names that do not match Monday.com's default deal stages, we rename the Status column values to match the source during migration.

Opal CRM interaction logs (calls, emails, meetings) stored against leads migrate as Updates or as Activity subitems on the Contact and Deal boards in Monday.com CRM. We preserve the activity timestamp, type (call/email/meeting), and any disposition or notes field. Monday.com's activity timeline is less structured than traditional CRM activity objects; we document the mapping strategy during scoping so the customer's team understands the difference in how activity history appears in the new system.

Opal CRM supports custom fields on Leads and possibly other objects, but the schema is not publicly documented. We identify custom fields during discovery by reviewing the customer's Opal CRM export file and map them to equivalent custom columns in Monday.com. Custom field types (text, number, date, dropdown) are mapped to Monday.com column types (Text, Numbers, Date, Dropdown). Any custom fields that cannot be represented in Monday.com's column system are flagged as manual-entry candidates in the handover notes.

Role definitions (Admin, Manager, Sales Rep) in Opal CRM do not export as structured data. We capture role assignments per user during discovery and document the mapping so administrators can reconfigure equivalent permissions in Monday.com's User management panel. Monday.com's permission model uses Workspace-level access and board-level edit/view permissions rather than role-based hierarchies, so we document the translation during scoping.