Migrate from Vinsolutions to Salesforce Sales Cloud

VinSolutions Customer maps to Salesforce Contact. Every Contact requires an AccountId — customers without a primary dealer association link to a default 'Unassigned Account' record. Original create date and last-modified date preserved as custom datetime fields since Salesforce's CreatedDate reflects migration time.

VinSolutions Customers flagged as 'Prospect' route to Salesforce Lead. Customers with 'Active' or 'Sold' status route to Contact. The split prevents duplicate records and ensures the sales pipeline sees unworked prospects in the correct Salesforce object. Additionally, the status field is preserved as a custom pick-list on Lead for reporting continuity.

VinSolutions Vehicle records have no Salesforce standard equivalent. FlitStack creates a Vehicle__c custom object with fields for VIN, Year, Make, Model, Trim, Mileage, StockNumber, and a lookup to the primary Account. Trade-in Vehicles get a separate Trade_In_Vehicle__c custom object linked to the Desking record.

VinSolutions Desking records store F&I structuring data — term, rate, APR, payment, down payment, trade-in allowance, and backend product selections. These map to a Desking_Record__c custom object with a lookup to the Account and a lookup to the Vehicle__c record. F&I product selections stored as a multi-select pick-list or separate line-item custom object depending on product count.

VinSolutions Deals (sold transactions) map to Salesforce Opportunities. The Deal stage (Pending, Funded, Closed) maps to Salesforce Opportunity StageName. CloseDate pulls from the Deal sale date. Amount reflects the total front-end deal structure. Backend F&I products are referenced via the Desking_Record__c lookup.

VinSolutions lead sources (Website, Phone, Showroom, Third-Party) map to Salesforce Lead LeadSource pick-list values. If VinSolutions uses custom source labels, FlitStack creates a custom pick-list on Lead and maps values one-by-one to preserve reporting continuity. This ensures that marketing attribution reports remain accurate after the migration.

VinSolutions Service records map to Salesforce Cases. Each Case is linked to the Account (customer) and the Vehicle__c record. Case Type maps to a custom pick-list mirroring VinSolutions service categories. Open service appointments migrate as open Cases; completed services as closed Cases with the original service date preserved.

VinSolutions call logs, emails, and notes map to Salesforce Tasks. Original timestamps and owners are preserved. Task WhatId links back to the Account or Contact. Meetings map to Salesforce Events with start/end times and the assigned consultant as owner. as the record owner for future reference.

VinSolutions DMS sync logs track real-time data exchange between the CRM and the Dealer Management System. This is a technical audit trail, not a business record. It does not have a Salesforce equivalent. FlitStack preserves the last sync timestamp as a custom field on Account for reconciliation purposes.

VinSolutions custom objects (available on higher tiers) map 1:1 to Salesforce custom objects with the __c suffix. Custom object relationships that use VinSolutions' N:N association model need Salesforce junction objects — FlitStack surfaces these in the migration plan for your admin to configure.

VinSolutions file attachments on Customer, Vehicle, or Deal records re-upload to Salesforce Files. File size limits apply (Salesforce default 25MB per file; Extended Storage available for higher limits). Inline images in notes are downloaded and re-hosted as Salesforce Files linked to the parent record.