Migrate from OrangeCRM to Twenty CRM

OrangeCRM Customers map to Twenty Companies. The Customer record is the primary account-level object and must be imported before any Contact or Opportunity records because Company serves as the parent lookup. We extract the Customer export, map company_name to name, domain or website fields accordingly, and preserve any custom fields as key-value properties in the Company's customProperties JSON column.

OrangeCRM Contacts map directly to Twenty People records. We map first_name, last_name, email, phone, and address fields 1:1. Multi-value phone and email records are split into separate phoneNumbers and emails arrays in Twenty's format. The Customer-to-Company lookup is resolved at migration time to set the linkedCompanyId on each Person record.

OrangeCRM Fulfillment records track subscription or order fulfillment tied to a Customer. Twenty has no native Fulfillment object, so we provision a custom Fulfillment object via Twenty's API, define fields matching the OrangeCRM schema (fulfillment_status, fulfillment_date, product_id, quantity, customer_reference), and create lookup relationships to the parent Company. Business logic embedded in fulfillment status transitions must be reimplemented as manual processes or documented for the customer's admin.

OrangeCRM Help Desk tickets map to a custom Ticket object we provision in Twenty. We map ticket_id, status, priority, assignee (resolved to a Twenty User), created_date, and conversation history. Conversation threads migrate as Note records or as a comments array on the custom Ticket object depending on Twenty's API support at migration time. Pipeline configurations for ticket stages do not export and must be rebuilt in Twenty's settings.

OrangeCRM email campaign records and subscriber lists map to Twenty Lists (as membership records) and opt-in date and engagement metrics stored as custom properties on Person records. We extract subscriber lists from OrangeCRM's email marketing module, create corresponding List records in Twenty, and link each subscriber's opt-in date and campaign engagement metrics to their Person record.

OrangeCRM Storefront orders and product records map to a custom Order object in Twenty. We preserve order_total, line_items (as JSON array), fulfillment_status, and any proprietary product IDs. Product records from the Storefront module map to a custom Product object in Twenty if the customer requires product catalog management in the destination.

Some OrangeCRM deployments include a Banking module for payment or ledger tracking. This maps to a custom Payment object in Twenty with fields for amount, currency, transaction_date, payment_type, and linked Company. We flag any multi-currency handling requirements and ensure currency codes are preserved in the destination schema.

OrangeCRM Event registrations and attendee records map to a custom Event object in Twenty with attendee status, session selections, and event_date preserved. Attendee Person records receive custom properties for event registration details. The original event field schema is preserved as custom fields on the Event object.

OrangeCRM user accounts and record owners map to Twenty User records. We perform an owner lookup during migration by matching email addresses. Any OrangeCRM Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before the record import resumes.

OrangeCRM custom fields per module are extracted from the module export with their full schema (field name, type, options). We provision matching custom fields in Twenty's object settings before importing data, mapping field types to Twenty's supported types (text, number, date, boolean, select, multi-select). Custom field values are included in the respective object import payloads.

OrangeCRM file attachments export as URL references or binary blobs depending on the export method. Per Twenty's documentation, file attachments are not included in CSV imports and must be re-uploaded manually or migrated via API. We flag every attachment URL, download the file, and re-upload to the linked Twenty record. Orphaned attachments without a valid parent record are documented in the final migration report.

OrangeCRM BI reports and dashboards are configuration data, not transactional records. We export report definitions as JSON metadata but note that the actual analytics data must be rebuilt or reconnected in Twenty. Report scheduling and alerting logic does not export and must be reconfigured in Twenty's settings post-migration.