Migrate from OrangeCRM to Salesforce Sales Cloud

OrangeCRM's Customer module is an account-level record that often embeds primary contact data within the same record. We parse the Customer export to identify records that contain both company and individual contact data, then split them: company data (name, address, industry) maps to Salesforce Account, and contact data (name, email, phone, title) maps to Salesforce Contact with the AccountId lookup resolved at migration time. Custom fields on the Customer module migrate as typed custom fields on both Account and Contact. The OrangeCRM customer_id becomes the Account External_ID__c for deduplication.

Contacts exported separately from the Customer module or identified as secondary contact records in OrangeCRM map 1:1 to Salesforce Contact. Standard fields (FirstName, LastName, Email, Phone, MailingAddress) migrate directly. Multi-value phone and email fields are split by delimiter into separate phone type labels. The Contact's AccountId is resolved by matching the parent OrangeCRM Customer External_ID to the newly created Salesforce Account External_ID__c.

Fulfillment records track subscription or order fulfillment status tied to OrangeCRM Customers. Salesforce has no native fulfillment object, so we map Fulfillment to Opportunity with a custom fulfillment_status__c picklist (values: Pending, Processing, Shipped, Delivered, Cancelled) and a related custom object Fulfillment_Line_Item__c for line-level detail (product, quantity, price). The OrangeCRM Customer External_ID is resolved to the Salesforce AccountId on the Opportunity. Any renewal or subscription terms are preserved as custom Opportunity fields.

OrangeCRM Help Desk tickets map to Salesforce Case. Ticket status (Open, In Progress, Resolved, Closed) maps to Case Status values that we configure in the destination org. Priority maps to Case Priority. Assignee maps to Case OwnerId via the User lookup by email. Conversation threads in OrangeCRM's ticket history are preserved as EmailMessage records linked to the Case via the WhatId field, keeping the full support context intact.

OrangeCRM Email Marketing records include campaign definitions and subscriber lists. Campaign-level metadata (name, subject, send date, open rate, click rate) maps to Salesforce Campaign with custom fields for engagement metrics. Subscriber records map to CampaignMember with Status (Sent, Open, Clicked, Bounced) and a custom original_opt_in_date__c. The customer chooses between a Salesforce Campaign model or List+ListMember model during scoping based on whether Service Cloud is included.

OrangeCRM BI reports and dashboards are configuration data rather than transactional records. We export report definitions as JSON metadata but note that the underlying data does not migrate as analytics history. We deliver a written inventory of every BI report with its name, filters, and field selections. Salesforce report rebuilding uses the exported field names as a reference; actual report creation in the destination org is performed by the customer's admin or a BI partner.

OrangeCRM Storefront orders map to Salesforce Order records. Product records map to Product2. Order totals, line items, and fulfillment status migrate to Order and OrderItem. If the customer does not have Order Management enabled in Salesforce, we map Storefront orders to Opportunity with custom order fields and a related custom product line object, matching the customer's existing Salesforce configuration.

OrangeCRM Banking module records (if activated in the deployment) map to a custom Banking_Transaction__c object with fields for transaction_id, amount, currency, transaction_date, description, and customer reference. We flag any multi-currency handling requirements during scoping. If the destination org has Finance Cloud or a billing integration (Zuora, Stripe, Chargebee), we map to the relevant invoice or ledger object instead.

OrangeCRM Event Management records contain event definitions, attendee registrations, and session selections. Event metadata (name, date, location, capacity) maps to Salesforce Event or Campaign. Attendee registrations map to custom Event_Registration__c records linked to the Event and the Contact (resolved via email match). Session selections and attendee status are preserved as custom fields on Event_Registration__c.

OrangeCRM supports custom fields per module. We extract the complete custom field schema via the export, map field types to Salesforce equivalents (Text, Number, Date, Picklist, Checkbox, Lookup), pre-create the destination custom fields via the Salesforce metadata API, and then map values during the data load phase. Custom field naming in Salesforce uses the OrangeCRM field label with an __c suffix and a scrubbed API name (spaces and special characters removed).

File attachments on OrangeCRM records export as URL references or binary blobs depending on the export method available. We preserve attachment URLs as Salesforce ContentDocument records linked via ContentDocumentLink to the parent record (Account, Contact, Opportunity, Case). If the attachment is a downloadable blob, we download, re-upload to Salesforce as a ContentVersion, and link to the parent record at migration time.

OrangeCRM user accounts and record owners map to Salesforce User records. We resolve owners by email match against the Salesforce destination org's User table. Any OrangeCRM owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import proceeds. Inactive OrangeCRM users are mapped to inactive Salesforce Users with the original owner preserved in a custom last_orangecrm_owner__c field for audit.