Migrate from XSale to Salesforce Sales Cloud

XSale Rep records map to Salesforce User. Each Rep's email address, name, and roleassignment become the Salesforce User's Email, Name, Title, and Role fields. Active Reps become Active Salesforce Users; inactive or archived Reps become Inactive Users to preserve OwnerId references on migrated records. If the destination org has fewer User licenses than Reps, we flag the discrepancy during scoping and the customer provisions additional licenses or deactivates legacy Rep records before migration begins.

XSale Route records do not have a direct Salesforce equivalent. We assess during scoping whether Routes map to Salesforce Territory (available in Enterprise and above with Territory Management enabled), a custom Route__c object, or Salesforce Topics on the related Account records. Route sequencing and stop order migrate as custom numeric fields on the chosen destination object. Route-to-Rep assignment migrates as OwnerId on the Route record itself, resolved via the Rep-to-User mapping.

XSale stores and customer accounts referenced in Visit and Order records map to Salesforce Account. The XSale store name becomes Account Name, and store address fields map to BillingAddress and ShippingAddress. If XSale stores have a store ID or external reference code, we store it as Account External_ID__c for deduplication during import.

XSale Visit records map to Salesforce Task (for check-in records and task-type visits) and Event (for scheduled stop visits with start and end times). Each Task receives the Account's ID as WhatId, and the assigned Rep's User ID as OwnerId. GPS coordinates from XSale Visit (latitude, longitude) migrate to custom Task fields for geo-audit purposes. Visit duration and status (completed, skipped, no-show) migrate as custom fields. Visit notes migrate as Task Description.

XSale Order records require a scoping decision: if the customer tracks order value and expected close date, Orders map to Salesforce Opportunity with a custom order_type__c picklist set to 'Pre-Order'. If XSale Orders have complex line items, return codes, or fulfillment status that Opportunity cannot accommodate, we create a custom Order__c object with Line Items via OpportunityLineItem or a related Custom Object. The mapping decision is made during schema design with the customer's RevOps lead.

XSale Order line items map to Salesforce OpportunityLineItem. We resolve Pricebook2, Product2 (using XSale product SKU as ProductCode), Quantity, and UnitPrice at migration time. If XSale products do not yet exist in Salesforce Product2, we create them during the Product migration phase before inserting line items.

XSale product catalog items map to Salesforce Product2 records. ProductCode maps from XSale SKU, Name maps from product title, Description maps from the XSale product description field. Standard Price Book entries are created for each Product2 using XSale pricing.

XSale may store store managers or buyer contacts associated with Visit and Order records. These map to Salesforce Contact attached to the mapped Account. Contact phone, email, and title migrate from XSale contact fields. If XSale does not have a distinct Contact object and stores contact name as free text on Visit records, we create Contact records from that free text during the Visit mapping phase.

XSale Visit activity logs (extended notes, order taken during visit, follow-up required flag) migrate to Salesforce Task records with custom fields for order_taken__c, follow_up_required__c, and visit_notes__c. The Task is linked to the Account via WhatId and to the Rep's User record as OwnerId.

XSale's built-in Rep performance metrics (stops completed, orders taken, revenue per route) do not have a Salesforce standard object equivalent. We create a custom Rep_Performance__c object with fields for reps_performed__c, stops_completed__c, orders_count__c, and revenue_per_route__c, linked to the User record via a lookup relationship. This preserves the historical performance data in Salesforce for reporting alongside pipeline metrics.

XSale Route-to-Rep assignments and Route-to-Account stop assignments require mapping to Salesforce's organizational structure. In Salesforce Enterprise with Territory Management enabled, Routes map to Territory records. Without Territory Management, we use Salesforce Topics (Account Topics) to associate Accounts with Route identifiers, or a custom Route_Assignment__c junction object. The choice is documented during schema design.

Any customer-added custom fields on the XSale Visit object migrate to custom fields on the Salesforce Task record. We identify these fields during the discovery audit, pre-create the corresponding custom fields in Salesforce (with appropriate field types: text, number, date, picklist), and map the values during the Visit migration phase. Custom field metadata (field label, API name, data type) is captured in the migration scope document before any data moves.

Any customer-added custom fields on the XSale Order object migrate to the destination Order object (Opportunity or custom Order__c depending on the scoping decision). We pre-create all custom fields in Salesforce, validate field types against XSale data during the transformation audit, and flag any XSale picklist values that do not match Salesforce picklist constraints so the customer can whitelist them before migration.

If XSale captures prospect store information separate from existing accounts (e.g., new store openings targeted during route planning), those records migrate to Salesforce Lead with Address, Company (store name), and any custom scoring fields. Lead Status is set to a default value (e.g., Open - Not Contacted) for manual assignment post-migration.