Migrate from OrangeCRM to Microsoft Dynamics 365 Sales

OrangeCRM Customer records map directly to Microsoft Dynamics 365 Sales Account. OrangeCRM's Customer ID becomes the Account's external identifier for dedupe during import. Custom fields on the Customer module (e.g., customer tier, industry classification) migrate to custom Account fields created in Dataverse before import. We validate the export completeness during discovery because OrangeCRM lacks a programmatic export endpoint and relies on admin-panel extracts.

OrangeCRM Contacts map 1:1 to Microsoft Dynamics 365 Sales Contact. Standard fields (name, email, phone, address) transfer directly. Multi-value email and phone fields in OrangeCRM are split into separate Contact phone and email rows. The Contact's parent AccountId is resolved from the mapped Customer record before Contact insert so that the Account-Contact relationship is established at load time.

OrangeCRM Fulfillment records track subscription or order fulfillment tied to a Customer. This is a proprietary OrangeCRM concept with no direct Microsoft Dynamics 365 Sales standard equivalent since Sales lacks native order management. We map Fulfillments to Dynamics Order records linked to the Account, and fulfillment status fields become custom Order fields. For continuity businesses with recurring Fulfillment records, we map each Fulfillment date-range as a separate Order with a custom recurrence reference field.

OrangeCRM Help Desk tickets map to Microsoft Dynamics 365 Sales Case (or Customer Service module Case if the license includes Service Cloud). Ticket status, priority, and assignee migrate directly. OrangeCRM conversation threads migrate to Case's internal Notes or to an Activity log. If the destination org lacks Service Cloud, we flag Case as unavailable and recommend the customer add the license or use a custom entity as a Case substitute.

OrangeCRM email campaign subscriber lists and opt-in dates migrate to Microsoft Dynamics 365 Sales as static marketing lists attached to Contacts. Subscriber opt-in dates and last engagement dates become custom Contact fields (email_optin_date__c, last_email_engagement__c). Campaign-level metrics (open rates, click rates) are preserved as custom fields on the Contact or as Campaign member custom data if the destination includes Dynamics Marketing.

OrangeCRM storefront orders and products map to Dynamics Order and Order Product records. Order totals, line items, and fulfillment status transfer directly. Product records from OrangeCRM's Storefront map to Product2 in Dynamics. Currency handling is validated at import time because OrangeCRM's Banking module may track multi-currency, which requires a corresponding Dynamics currency configuration.

OrangeCRM Banking module records (payment or ledger tracking) have no direct standard Microsoft Dynamics 365 Sales equivalent because banking belongs in an ERP layer. We map Banking records to a custom Invoice entity or, if the customer licenses Business Central, flag them as requiring a separate ERP migration. Currency fields from Banking records are mapped to a custom currency_code__c field. This module is rare in standard OrangeCRM deployments; we confirm presence during discovery.

OrangeCRM event registrations and attendee records map to Dynamics Event (calendar event) linked to Contacts via EventRelation. Attendee status, session selections, and custom event fields migrate as custom Event fields or as custom Contact fields scoped to event context. We use Event's StartDateTime, EndDateTime, and Location to preserve the original event structure.

OrangeCRM user accounts map to Microsoft Dynamics 365 Sales User records by email match. Any OrangeCRM Owner without a matching Dynamics User is placed in a reconciliation queue for the customer's admin to provision before record import continues. Owner assignments on Fulfillment, Ticket, and Contact records resolve against the mapped User table at import time.

OrangeCRM custom fields per module are extracted from the admin-panel export as a full schema definition. We pre-create corresponding Dataverse custom fields (with correct type mapping: text to String, date to DateTime, number to Integer or Decimal) before any data import. OrangeCRM multi-select fields map to Dynamics MultiSelectOptionSet. Custom field API names are preserved with a migration-origin suffix to distinguish them from future additions.