Migrate from Vinsolutions to HubSpot

VinSolutions stores all person records as a unified contact object with a DMS customer ID. FlitStack maps each record to HubSpot Contact, preserving the DMS customer ID as a custom property (dms_customer_id__c). Contacts with a 'Sold' status route to HubSpot's customer lifecycle stage; all others route to 'lead' unless your migration plan specifies a different stage mapping.

VinSolutions prospects that have not yet been assigned to a sales rep or showroom visit are split to HubSpot Lead rather than Contact. The split is based on the source 'status' field: records with status = 'Internet Lead' or 'New Prospect' land as HubSpot Leads; records with status = 'Showroom Visit', 'Sold', or 'Service Customer' land as HubSpot Contacts.

VinSolutions companies represent dealership rooftops or commercial accounts. Mapped directly to HubSpot Company. The dealership name, address, and phone map to HubSpot standard fields; DMS store ID maps to a custom property (dms_store_id__c) for multi-rooftop groups that need to filter reporting by store.

VinSolutions deals represent vehicle transactions with associated vehicle details (VIN, make, model, year), deal amount, and F&I products. Mapped to HubSpot Deal. Deal stage names in VinSolutions (e.g., 'Hot', 'Negotiating', 'F&I', 'Closed') are mapped value-by-value to HubSpot deal stages defined in your target pipeline.

VinSolutions supports multiple sales pipelines per store (e.g., New Vehicle, Used Vehicle, Commercial). Each VinSolutions pipeline maps to a HubSpot deal pipeline. Stage names, probabilities, and forecast categories are mapped value-by-value. If VinSolutions uses one pipeline, a single HubSpot pipeline is created; if multiple pipelines exist, separate HubSpot pipelines are configured before data loads.

VinSolutions stores vehicle details (VIN, year, make, model, trim, mileage, color) on the deal record. These fields have no native HubSpot equivalent. FlitStack creates custom deal properties (vehicle_vin__c, vehicle_year__c, vehicle_make__c, vehicle_model__c, vehicle_trim__c, vehicle_mileage__c) and maps each value. If your HubSpot plan supports custom objects, a Vehicle custom object is created with a one-to-many relationship to Deals.

VinSolutions tracks trade-in vehicles per deal as a sub-object with its own VIN, mileage, and ACV. FlitStack maps trade-in data to custom deal properties (trade_in_vin__c, trade_in_mileage__c, trade_in_acv__c, trade_in_allowance__c). These are stored on the deal record since HubSpot does not natively support nested vehicle sub-objects on a deal.

VinSolutions desking tracks F&I product selections (GAP, service contract, tire protection, paint sealant) as deal-level flags or line items. FlitStack maps these to custom deal properties (fi_gap__c, fi_service_contract__c, fi_tire_protection__c, fi_paint_sealant__c) with Yes/No or amount values. The desking tool configuration itself does not export — only the product selections recorded per deal.

VinSolutions activity records (logged calls, emails, meetings, and notes tied to a prospect or deal) map to HubSpot engagements. Original timestamps, owners, and parent record associations are preserved. Notes with rich text are loaded as HubSpot notes; calls and meetings become HubSpot meetings with duration and outcome fields carried over.

VinSolutions users are matched to HubSpot users by email address. Unmatched users are flagged before migration — your team either creates HubSpot user accounts for them or assigns their records to a fallback owner. Inactive VinSolutions users are mapped as inactive HubSpot users unless you specify they should be excluded from the migration.

VinSolutions links every contact and deal to a DMS customer ID that ties the CRM record to the Dealer Management System. HubSpot has no native DMS ID field. FlitStack creates a custom contact property (dms_customer_id__c) and a custom deal property (dms_customer_id__c) and populates them from the VinSolutions export. This enables your post-migration HubSpot-DMS integration to re-associate records.

VinSolutions tracks lead sources (Internet, Phone, Showroom, Referral, Third-Party) as a contact property. These values are mapped value-by-value to HubSpot's 'Original source' or a custom 'lead_source' property. If VinSolutions uses third-party advertising sources (Cox Autodata, Dealer.com), those are preserved as custom source values in HubSpot.