Migrate your OrangeCRM data

Customer is the primary account-level object in OrangeCRM. We map it to Accounts or Companies in destination CRMs, preserving custom fields by parsing the module's export format and applying value transformations where field types differ.

Contacts export cleanly from OrangeCRM's Customer module with standard fields (name, email, phone, address). We map these 1:1 to destination Contacts and handle multi-value phone/email fields by splitting into destination-valid arrays.

Fulfillment records track subscription or order fulfillment status tied to Customers. Since this is a proprietary OrangeCRM concept with no direct equivalent in most destination CRMs, we map Fulfillment status and dates as custom properties on the linked Customer or Order record.

OrangeCRM's Help Desk module stores tickets with status, priority, assignee, and conversation history. We map tickets to the destination's ticket object, converting conversation threads into comment threads and preserving custom ticket field values.

Email campaign records and subscriber lists in OrangeCRM map to Lists or Segments in destination CRMs. We preserve subscriber opt-in dates and campaign engagement metrics as custom contact properties rather than full campaign objects.

BI reports and dashboards in OrangeCRM are configuration data, not transactional records. We export the report definitions as JSON metadata but note that the actual analytics data must be rebuilt or re-aggregated in the destination BI tool.

Storefront orders and product records map to Orders and Products in destination systems. We preserve order totals, line items, and fulfillment status, converting any proprietary OrangeCRM product IDs to destination product references.

Some OrangeCRM deployments include a Banking module for payment or ledger tracking. This maps to the destination's accounting or invoice objects. We flag any currency or multi-currency handling requirements during the scoping call.

Event registrations and attendee records map to Events and Contacts in the destination. We preserve attendee status, session selections, and any custom event fields as custom Contact or Event properties.

OrangeCRM supports custom fields per module. We extract the full custom field schema via their export, then generate destination custom fields with matching types and map values accordingly during import.

File attachments on records export as URL references or binary blobs depending on OrangeCRM's export method. We preserve the attachment URL or download and re-upload to the destination, maintaining the linked record relationship.

OrangeCRM user accounts and record owners map to Users in the destination CRM. We perform an owner lookup during import and flag any orphaned assignments where the owning user does not exist in the destination system.