Migrate from XSale to Zoho CRM

XSale Reps map to Zoho CRM Users. We resolve by email match against the destination Zoho User table. Any XSale Rep without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before Contact and Deal import begins. Zoho User license type (Standard, Professional, etc.) is determined by the customer's Zoho plan and assigned during provisioning. XSale Rep roles (Admin, Manager, Field Rep) map to Zoho Roles and Profiles.

XSale Routes do not have a direct Zoho CRM equivalent. We create a custom Zoho module named Route__c with fields for Route Name, Assigned User (lookup to User), Start Date, End Date, Territory, and visit sequence order. If the customer prefers not to use a custom module, we map Routes to Zoho Campaigns as a standard object alternative, with Campaign Members representing store stops. The customer selects the strategy during scoping based on reporting needs.

XSale Visit records map to Zoho Task (for visit tasks with completion status) and Event (for scheduled visits with start and end times) records. Each Visit's linked Store and Rep resolve to the Zoho Account and User lookups respectively. Visit status (Completed, Skipped, Pending) maps to Task Status or Event Status. Visit geolocation coordinates migrate as custom latitude and longitude fields if the customer requires location reporting.

XSale Store records (the physical retail or wholesale location visited) map to Zoho CRM Accounts. Store Name becomes Account Name, Store Address maps to the Billing Address fields, and Store Type (retail, wholesale, distributor) maps to an Account custom field. Store is the parent entity for Contacts at that location, so Account is created before any Contact import so the AccountId lookup is satisfied at insert time.

XSale Contact records at each Store map to Zoho CRM Contacts. Each Contact is linked to its parent Account via the AccountId lookup. Contact name, phone, email, title, and role at store migrate directly. XSale's contact type (Store Manager, Buyer, Merchandiser) maps to a custom picklist field on the Zoho Contact for segmentation.

XSale Orders map to Zoho CRM Deals (called Opportunities in standard CRM terminology, but Zoho uses Deal). Order amount maps to Deal Amount, Order date maps to Close Date, Order status maps to Deal Stage, and the linked Store-Account maps to the AccountId lookup. Order lines (individual products ordered) map to Deal Line Items if the customer uses Zoho's Products and Price Books module, or to custom multi-line text fields on the Deal if the quoting module is not active on the destination plan.

XSale pre-order transactions (orders placed before the route visit, common in wholesale and DSD scenarios) are handled as Deal Line Items attached to the corresponding Order-Deal. Product, quantity, unit price, and discount migrate as line item fields. If the customer has complex pre-order pricing rules (volume tiers, customer-specific pricing), we migrate these as custom fields on the Deal rather than attempting to model them as Zoho Price Books, which adds significant setup complexity.

XSale Products (SKU, name, description, unit price) map to Zoho CRM Product2 records. ProductCode maps from XSale SKU, and Standard Price Book entries are created during import. Products are imported before Deals so that line item resolution succeeds at migration time.

XSale visit activity logs (comments, check-in timestamps, stock-out flags, competitor notes) migrate as Zoho Task Description fields or as linked Note records on the parent Deal. We preserve the full text content, timestamp, and linked Rep-User. If the customer has extensive free-form visit notes, we migrate them as Notes attached to the Account (store) so they are accessible from the account view without drilling into individual visits.

XSale rep performance data (visits completed, orders placed, revenue generated per route) does not map to a standard Zoho CRM object. We create custom fields on the User object for key performance indicators (KPits_completed__c, orders_placed__c, revenue_generated__c) and populate them from XSale historical data. For advanced reporting on rep performance, we recommend Zoho Analytics as a companion product, where the imported data is combined with live Zoho CRM data for cross-object reporting.

XSale route assignments (which rep is assigned to which route on which date) are reconstructed in Zoho as either custom Route__c module assignments or as Campaign Members on the Route-Campaign. The mapping type depends on the Route strategy chosen during scoping. Each assignment record links the Route to the Rep-User and carries the effective date range.

XSale customers frequently add custom fields to the Order object for delivery instructions, POD (proof of delivery) status, payment terms, or customer-specific discount flags. We identify every custom Order field during discovery, create matching custom fields on the Zoho Deal object before migration, and map values during the Order-to-Deal transform. Fields that have no Zoho equivalent are flagged during scoping so the customer can decide whether to drop them, combine them into a text area, or accept a custom field build.