Migrate from OrangeCRM to monday CRM

OrangeCRM Customers map to a monday.com board where each item represents an account. The Customer name becomes the Item Name, address fields map to location columns, and any industry or type properties become dropdown or text columns. We preserve custom Customer-level fields as custom columns created before import. Account items are created first so that subsequent Contact items can reference them via a Connect board or relation column.

OrangeCRM Contacts export cleanly with standard fields (name, email, phone, address). We map these 1:1 to monday.com Items in a Contacts board or Groups within the Companies board, using email as the dedupe key. Multi-value phone or email fields are split into separate text columns. Contact owner resolves by matching OrangeCRM owner email to the monday.com workspace member.

Fulfillment records track subscription or order fulfillment status tied to Customers. Since this is a proprietary OrangeCRM concept, we map Fulfillments to Items in a dedicated Fulfillments or Orders board, creating a relation column back to the parent Customer Item. We preserve fulfillment status, subscription tier, and any custom fields as typed columns. Customers with multiple active Fulfillments produce multiple Items linked to the same Customer.

OrangeCRM Help Desk Tickets map to Items in a Tickets board with status, priority, and assignee columns. Conversation threads in OrangeCRM export as text or JSON and are re-structured as a timeline column or series of subitems. We normalize ticket status values to match the monday.com board's status column options and preserve assignee assignments by matching OrangeCRM owner email to monday.com workspace members.

Email campaign records and subscriber lists in OrangeCRM map to a Segments board or are stored as tag/label columns on Contact items. We preserve subscriber opt-in dates as date columns, engagement metrics as number columns, and subscription status as dropdown or checkbox columns. Email addresses remain linked to the corresponding Contact Item.

Storefront orders and product records map to Items in an Orders board. We preserve order totals, line item details, and fulfillment status. Product IDs are mapped via a Products lookup board, and any proprietary OrangeCRM product data becomes custom columns on the Order Item. Closed or cancelled orders migrate with their original status preserved.

Some OrangeCRM deployments include a Banking module for payment or ledger tracking. We map these to an Invoices or Ledger board in monday.com with invoice amount, currency, payment status, and related Customer as columns. Multi-currency handling is flagged during scoping; currency codes become text columns and exchange rate history is preserved as a number column where applicable.

Event registrations and attendee records map to Items in an Events board with date, location, and session columns. Each registration creates a relation to the corresponding Contact Item in the Contacts board. Attendee status, session selections, and custom event fields become custom columns on the Event Item.

OrangeCRM supports custom fields per module. We extract the full custom field schema via admin panel export, then create matching custom columns in monday.com with equivalent types before any data import. Text fields map to text columns, dates to date columns, numbers to number columns, and picklists to dropdown columns. Validation rules from OrangeCRM are not enforceable in monday.com and are documented for the admin to recreate as needed.

File attachments on OrangeCRM records export as URL references or binary blobs depending on the admin panel export method. We preserve the attachment URL or download and re-upload to monday.com's file column, maintaining the link to the parent Item. Where attachment URLs become stale, we flag them in the migration report for manual re-upload by the customer.