Migrate from XSale to Freshsales

XSale Reps map to Freshsales User records. We resolve by email match. Active Reps become active Freshsales Users; inactive or archived Reps become inactive Users so historical assignments on Visit and Order records remain valid. The customer's admin provisions any missing Freshsales users before record import.

XSale Route records have no direct Freshsales equivalent. We create a Route custom object in Freshsales with fields for Route Name, Assigned Rep (lookup to User), Start Date, End Date, and Route Status. Each Visit in the Route sequence links to the Route via a lookup field on the Activity record. This requires the Growth plan or above. If the customer is on the Free plan, we reconstruct Routes as a filtered Activity view grouped by assigned Rep and date range.

XSale Visit records map to Freshsales Task or Event depending on whether the visit was scheduled (Event) or completed as a log entry (Task). Visit date, duration, location (address fields), outcome, and notes transfer to Freshsales Activity fields. If a custom Route object was created, the Visit links to the Route via a lookup field.

XSale Order and pre-order transaction records map to Freshsales Deals with line items. The Order total becomes Deal Amount. Order status maps to Freshsales Deal Stage (Open, Won, Lost). Product line items from the Order become OpportunityLineItem records attached to the Deal. If the customer has custom fields on the XSale Order object, we pre-create matching custom fields on the Freshsales Deal object before migration.

XSale accounts (stores, retail locations, or B2B customers) map to Freshsales Account records. Account name, address, and any custom fields transfer directly. We deduplicate by account name or store ID during import.

XSale contact records associated with stores or customer accounts map to Freshsales Contact records linked to the corresponding Account. Contact name, phone, email, and role transfer directly. Any custom fields on XSale contacts pre-create matching custom fields on the Freshsales Contact object.

XSale Visit objects frequently contain customer-added custom fields for visit outcome codes, compliance checkboxes, or photo capture. We pre-create matching custom fields on the Freshsales Task or Event object before migration. Freshsales supports up to 100 fields per custom object and 25 filterable fields. If the total field count exceeds this, we prioritize the most operationally critical fields and flag the remainder for a post-migration bulk update.

XSale Order objects often contain custom fields for payment terms, delivery instructions, or order source channels. We pre-create matching custom fields on the Freshsales Deal object before migration using the same field type mapping (text, number, date, dropdown, checkbox). Field-level security and validation rules are coordinated with the Freshsales admin before data load.

If XSale stores Products as separate entities from Orders, they map to Freshsales Product2 records with Standard Price Book entries. Product SKU maps from XSale product code. If products are embedded within Order line items only, we extract them as Product2 records during migration to support deal line items and future quoting.