Migrate from Vinsolutions to Nutshell

VinSolutions stores both active customers and prospects as separate objects. FlitStack maps both to Nutshell's unified Lead object. VinSolutions lead status (New, Contacted, Demo, etc.) translates to Nutshell's Lead status pick-list via value mapping. Prospects with a closed deal route to a Deal record post-migration.

VinSolutions customers who have purchased a vehicle are mapped to Nutshell People. The source DMS-matched flag is preserved as a custom Nutshell field for reference. Multiple VinSolutions prospects associated with one household collapse to a primary Person record in Nutshell.

VinSolutions vehicle data (VIN, stock number, make, model, year, trim, color, trade-in value) has no native Nutshell equivalent. FlitStack creates Nutshell custom fields — Vehicle_VIN__c, Vehicle_Stock__c, Vehicle_Details__c — on Person and Deal records so vehicle context travels with the customer record.

VinSolutions company records (the dealership entity itself and any commercial accounts) map directly to Nutshell Company. Franchise information, manufacturer affiliation, and dealership group hierarchy are preserved as custom fields since Nutshell has no native dealer-franchise concept or multi-rooftop grouping structure.

VinSolutions inbound leads from websites, third-party lead providers, or Cox Automotive inventory sources map 1:1 to Nutshell Lead. Lead source attribution is preserved in Nutshell's custom lead source field. Duplicate detection runs against email during import using Nutshell's built-in matching rules to prevent duplicate records.

VinSolutions lifecycle stages (New Lead, Contacted, Demo Drive, F&I, Sold, Lost) map value-by-value to Nutshell Lead status options (New, Working, Idle, Unqualified, Converted). Custom VinSolutions statuses require a mapping table built before migration. Some automotive-specific stages may collapse into fewer Nutshell statuses depending on your input.

VinSolutions deals and service contracts map to Nutshell Deals. Deal amount, close date, and owner all migrate directly. VinSolutions deal stage names (Prospecting, Finance, Closed Won) map to Nutshell pipeline stage values per pipeline. Each pipeline requires its own stage mapping table to ensure correct stage assignment in Nutshell.

VinSolutions sales pipeline maps to a Nutshell Pipeline. Each VinSolutions pipeline becomes one Nutshell pipeline. Nutshell supports multiple pipelines — the VinSolutions pipeline name becomes the Nutshell pipeline name, and stage values are recreated based on the mapping table. Pipelines must be pre-created in Nutshell before migration runs.

VinSolutions calls, emails, notes, and tasks migrate as Nutshell Activities with original timestamps, owners, and linked record IDs preserved. Call disposition notes and meeting outcomes migrate as activity description text. Activity-to-record linkages are maintained via Nutshell's activity linking mechanism during import.

VinSolutions file attachments on customers, vehicles, and deals are downloaded and re-uploaded to the corresponding Nutshell record as files. File metadata (original filename, upload date) is preserved. File size limits from Nutshell's storage apply — files exceeding Nutshell's size threshold may require alternative storage or compression.

VinSolutions custom fields on any object become Nutshell custom fields on the equivalent object. Field types are matched — pick-lists to Nutshell choice fields, text to text, numbers to number. N:N relationships in VinSolutions custom objects need junction records in Nutshell.

VinSolutions users and owners are matched to Nutshell users by email address. Unmatched owners are flagged before migration begins so your team can invite them or reassign their records. Records owned by unmatched users are assigned to a fallback Nutshell user specified by the customer before the migration run executes.