Migrate from XSale to HubSpot

XSale products with no variants map directly to HubSpot Products. The product name, description, and base price translate to HubSpot's name, description, and price fields. Products with variants require splitting — see the variant mapping note. Direct mappings preserve data integrity without transformation logic, making validation straightforward during migration testing.

XSale stores variants as option combinations (e.g., size=XL, color=Red) under a parent product. HubSpot has no native variant concept. Each variant row in XSale becomes a separate HubSpot Product record with a custom Parent_Product_ID__c field linking it to the HubSpot product representing the parent. Option values are stored in custom properties.

XSale custom attributes (e.g., material, care instructions, certifications) map to HubSpot product properties. Each unique attribute name in XSale generates a corresponding custom property in HubSpot. Attribute types are preserved: text attributes become string properties, numeric attributes become number properties, and option-list attributes become pick-list properties in HubSpot.

XSale's multi-level category hierarchy (parent → child → grandchild) cannot be fully replicated in HubSpot, which has no native product category hierarchy. We map the top-level category to HubSpot's Product Type property. For deeper levels, we store the full category path as a pipe-delimited string in a custom Category_Path__c property on the product record.

XSale stores customer records with name, email, phone, company name, and address. These map directly to HubSpot Contact properties: firstname, lastname, email, phone, and company. If XSale stores company as a separate object with a reference from the contact, the company migrates to a HubSpot Company record and the contact is linked via the company_domain_name or primary company association in HubSpot.

XSale stores company-level records with name, website, industry, and address. These map to HubSpot Company properties: name, website, industry, and address fields. If XSale stores only company name without a full company object, the company name is stored as the Contact's associated company in HubSpot and a Company record is created automatically.

XSale's product SKU or part number maps directly to HubSpot's HS SKU field on the Product object. This field is native to HubSpot Products and requires no custom field creation. Uniqueness validation is applied against the HubSpot catalog after migration to prevent duplicate SKU collisions.

XSale stores product images and media file URLs. HubSpot Products do not natively store images — images are typically hosted in HubSpot Files and referenced via URLs. We extract XSale media URLs and store them in a custom property (Product_Image_URLs__c) as a pipe-delimited list. If the migration includes re-uploading files to HubSpot Files, those new URLs replace the XSale URLs in the property.

XSale product pricing (list price, cost price, MSRP) maps to HubSpot's standard price fields. If XSale stores multiple price types (cost, MSRP, dealer price), the additional values are stored as custom properties in HubSpot (e.g., Cost__c, MSRP__c). Currency handling: if XSale uses a non-USD currency, the HubSpot price is stored in the original currency and a currency_code property is added.

XSale stores supplier and manufacturer information on products. HubSpot has no native supplier field on Products. We create custom properties (Supplier__c, Manufacturer__c) on the HubSpot Product object to carry this data. These properties are indexed and can be used in HubSpot's filtering and reporting.

XSale tracks stock quantities per product or variant. This maps to HubSpot's standard Quantity field on the Product object. Note: HubSpot's native inventory tracking is designed for e-commerce integrations. For CRM-style inventory visibility, custom rollup fields or a separate integration with an ERP may be needed post-migration.

We preserve the original XSale product ID on every migrated record as a custom property (Source_System_ID__c) on the Product, Contact, and Company objects. This ID is used for delta-run de-duplication (so records modified in XSale during cutover are correctly updated rather than re-created), for audit traceability, and for any future sync back to XSale if needed.

XSale may store which products a customer has purchased or is associated with. HubSpot has no direct product-to-contact association object at the CRM level. We handle this by creating a custom property on the Contact record (Associated_Products__c) storing the list of related HubSpot product IDs, or by creating a Deal record that links the contact to the product for cases where the association represents a purchase history.