Migrate from XSale to Microsoft Dynamics 365 Sales

XSale Reps are the primary actors in the field execution model. We distinguish between internal Reps (sales team members) who should map to Dynamics 365 User records, and external Reps (store contacts, buyer contacts) who map to Contact records. We use the XSale Rep type or role field to determine the split. Internal Reps are resolved by email match against the destination User table; external Reps are inserted as Contacts against the appropriate Account.

XSale Routes are anchored to store or customer locations that serve as Accounts in Dynamics 365. We extract the store or customer reference from each Route and create Account records in Dynamics 365 using the store name as Account Name and any stored address fields. The Account is created before the Route migration so that the AccountId lookup is satisfied on Route insert.

Routes are XSale's core organizational unit and have no direct Dynamics 365 equivalent. We provision a custom Route__c entity in the destination org with fields for route_name, rep_id (lookup to User), start_date, end_date, and status. The route sequence (order of stops) is preserved as a custom sequence_number field. Route__c is created as the first custom entity in the migration so that Visit records can reference it via a WhatId or custom lookup.

XSale Visits record each stop along a route. We map Visits to Task records with TaskSubtype = Task (for store checks and pre-order confirmations) or Event records (for scheduled meetings with buyers). The WhatId on the Task or Event points to the Route__c custom entity. Visit timestamp maps to ActivityDate on Task or StartDateTime on Event. Any visit outcome or notes field maps to Description or custom Task fields.

XSale Orders map to Dynamics 365 Opportunities. The order amount becomes the Opportunity Amount field, the order date becomes the Close Date, and the status (pending, confirmed, delivered) maps to a corresponding Opportunity Stage. Line items within an XSale Order (SKUs, quantities, prices) map to OpportunityLineItem records. We resolve the Pricebook2 and Product2 references during migration.

Pre-order transactions in XSale capture buyer commitments before physical delivery. We assess the volume and structure during discovery. Low-volume pre-orders (under 5,000 records) map to a custom PreOrder__c entity linked to the Account and Route. High-volume pre-orders that represent a formal quoting process map to Salesforce Quote records, which are standard from Microsoft Dynamics 365 Sales Professional onward. The customer chooses the strategy during scoping.

SKUs and products referenced in XSale Orders are extracted and provisioned as Product2 records in Dynamics 365. Standard Price Book entries are created during the product phase. ProductCode maps from the XSale SKU field. If XSale stores product images or descriptions, these migrate as ContentDocument records linked to Product2.

XSale Rep ownership on Routes, Visits, and Orders maps to Dynamics 365 User records. We resolve by email match. Any XSale Rep without a matching User in the destination org goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId on Opportunity must be resolved before Opportunity insert.