Migrate from openCRX to monday CRM

openCRX Contact records (the individual subclass of Account) map to items in a Monday.com People board. We map full name, email address, phone number, postal address, and any active DataBinding custom fields to Monday.com custom columns. Ownership is resolved by matching the openCRX creator/owner reference to the customer's Monday.com workspace member list. Contacts are migrated before Deals so that deal items can link to their primary contact person via a relation column.

openCRX LegalEntity records (the company subclass of Account) map to items in a Monday.com Organizations board. Company name, industry, revenue, number of employees, and address fields map to Monday.com text and number columns. URL fields become link columns. The Organization board links to the People board through a relation column so that contact-to-company relationships are preserved.

openCRX Opportunity records (part of the contract hierarchy) map to items in a Monday.com Deals or pipeline board. Deal name, amount, currency, close date, stage, and probability map to Monday.com columns. openCRX's segment-specific stage names are translated to the customer's Monday.com pipeline stage labels. Owner resolves by email match to Monday.com workspace members.

openCRX Quote records inherit from the contract hierarchy and do not have a direct Monday.com CRM equivalent. We convert each Quote into a Deal item with the status set to 'Quote' and the original quote PDF attached via the Monday.com file column. Quote line items become sub-items or group rows under the Deal item. Customers who require a structured Quote object should plan to use Monday.com's Integrations with a quoting tool post-migration.

openCRX Sales Order records follow the same constraint as Quotes — no native Monday.com CRM equivalent. We create a Deal item with status reflecting the order stage, attach the order document as a file, and preserve line items as sub-items. Pricing rules applied at order creation in openCRX are stored as static values in the migration to avoid logic loss.

openCRX Invoice records (terminal contract objects) migrate as Deal items with an Invoice status label. The invoice PDF is attached to the item. Header fields (invoice number, date, amount, currency, payment status) become custom columns. openCRX's payment terms and billing address map to text columns. Any linked Accounts are linked via the Organizations relation column.

openCRX Activity records (including Activity Trackers) map to Monday.com item updates. Each activity type (call, email, meeting, task) is written as a timestamped update with the activity type, duration, subject, description, and outcome. openCRX's rich time-tracking attributes and activity notes become update body text. Monday.com's Activity Log is preserved per item. This is a flattening migration — openCRX's ability to link an Activity to multiple object types (Contact, Account, Opportunity) is simplified to the primary item being migrated.

openCRX Workflow Processes are segment-scoped and tightly bound to the running instance. They are not standalone records that can be exported and re-imported. We document the active workflow definitions during discovery — trigger conditions, steps, and assigned roles — in a written Workflow Inventory delivered to the customer. The customer rebuilds automations in Monday.com using its native automation builder or an integration tool such as Zapier or Make.

openCRX Product records map to items in a Monday.com Products board. Product name, SKU (hs_sku equivalent), description, unit price, and currency map to Monday.com columns. Multi-currency pricing from openCRX is stored as multiple number rows per currency. Bundle and design-to-order product structures are flattened to a single product item with a notes column describing the bundle composition.

openCRX custom fields defined via DataBinding PropertySet are identified during scoping and mapped to Monday.com custom columns. Monday.com supports text, number, date, dropdown, multi-select, checkbox, URL, link, formula, dependency, and file column types. Complex multi-value or structured user-defined fields that have no direct Monday.com equivalent are stored as text or note columns. The customer reviews and recreates any column configuration not achievable through standard type mapping.