Migrate from XSale to Pipedrive

XSale Rep records map to Pipedrive User accounts. We match by Rep email address and resolve Pipedrive OwnerId on all downstream records. Any Rep without an email is held in a reconciliation queue for the customer's admin to provision a matching Pipedrive user before record import. Field team role assignment (Route Manager, Sales Rep, Delivery Rep) migrates to a Pipedrive custom user field.

XSale Routes require a scoping decision: if the customer treats each route as a recurring account (store or retail location), we map Route to Pipedrive Organization with address details. If the customer treats routes as sales campaigns or territories, we map Route to a Deal representing the route's total projected revenue with Activity records linked to individual Visits. The customer chooses the model during discovery.

XSale Visit records map to Pipedrive Activity records. Visit type determines the Pipedrive Activity type: in-person store visits map to Meeting, phone check-ins map to Call (TaskSubtype=Call), and pre-order captures map to Task. Visit timestamp becomes the Pipedrive ActivityDate. Any custom fields on Visit (store condition, competitor notes, stock level) migrate to custom Activity fields we pre-create in Pipedrive before migration.

XSale Order records map to Pipedrive Deals. Order total value maps to Deal value. Order status (pending, confirmed, delivered, invoiced) maps to a Deal custom field if no native Pipedrive stage matches. XSale order date becomes the Deal add_date in Pipedrive. We determine during scoping whether the customer wants one Deal per order or a rolling Deal per route-account.

XSale order line items map to Pipedrive Deal Products. We resolve the Product2 reference in Pipedrive's Product catalog; if a product does not exist in Pipedrive, we create it with the SKU from XSale. Quantity and unit price migrate to the OpportunityLineItem equivalent in Pipedrive.

XSale pre-order transactions (commitments placed during a visit before physical delivery) can be mapped as Deal custom fields capturing pre-order value, or as Note records attached to the Deal with the pre-order details. The customer chooses during scoping based on reporting needs.

XSale buyer records (the retail store or individual purchasing from the field rep) map to Pipedrive Person records. Email and phone migrate to standard Pipedrive contact fields. If the buyer is an organization, we also create a corresponding Organization record and link the Person via the organization_id field.

XSale store or retail location records that represent physical delivery destinations map to Pipedrive Organization with address fields populated from XSale's location data. The Organization becomes the Account that the Rep visits (linked via Visit Activity records).

XSale frequently carries customer-added custom fields on the Order object (delivery window, special handling, order source channel). We surface these during discovery, pre-create matching custom fields in Pipedrive (selecting the appropriate type from Pipedrive's 16 custom field types), and map them during migration. Text fields, date fields, and single-option fields translate directly; multi-option fields map to Pipedrive multiple options fields.

XSale Visit records commonly include custom fields for store condition, competitor products observed, or route-specific notes. We pre-create matching custom fields on Pipedrive Activity records before migration and map the values. Field type conversion follows the same mapping logic as Order custom fields.

XSale territory assignments map to Pipedrive Organization Tags (if multiple organizations share a territory) or to a custom Organization field capturing the territory name. The customer chooses the representation during scoping based on whether territory is used for reporting.