Migrate from Vinsolutions to Microsoft Dynamics 365 Sales

VinSolutions stores all customer records in a single Contact object. Dynamics 365 splits customers into Lead and Contact — we route records based on the VinSolutions contact type: active service or sales customers land as Contact; prospects and unworked leads land as Lead. The split rule is configurable before migration runs.

VinSolutions prospect records that have not progressed to a customer record migrate directly to Dynamics 365 Lead. We map the original create date to a custom Created_In_Source__c field since Dynamics 365 CreatedOn is set at migration time. The prospect's lifecycle stage—open, qualified, or lost—translates to Lead.StateCode and Lead.StatusCode via value-by-value mapping. We verify that all VinSolutions status values have a corresponding Dynamics 365 option before migration commits; any missing options are added as custom pick-list values during schema setup.

VinSolutions dealership and company records map to Dynamics 365 Account. We map name to Account.Name, address fields to the composite address on Account, and phone to Account.Telephone1. If the dealership is also a customer (e.g., for inter-dealer transactions), we preserve the IsPrimaryDealer__c flag as a custom field.

VinSolutions vehicle sub-records (VIN, year, make, model, trim, mileage, color, ACV) have no native Dynamics 365 equivalent. We create a Vehicle custom table in Dataverse and link it to the Contact via a lookup field. The original vehicle record ID is preserved as Source_Vehicle_ID__c for delta-run de-duplication.

Trade-in vehicles linked to deals in VinSolutions Desking are stored as sub-records. We create a TradeInVehicle custom table with fields for VIN, mileage, ACV, payoff amount, and linked opportunity. Each trade-in is tied to the parent opportunity so the deal structure is intact after migration.

VinSolutions Desking outputs structured deal terms (monthly payment, term, APR, lender name, first payment date). We map the primary deal terms (amount, close date, stage) directly to the Opportunity record and store extended desking details in a linked DeskingData custom table. This preserves the full deal structure without bloating the Opportunity object.

VinSolutions Desking captures F&I product selections (GAP, tire-and-wheel, service contract, theft protection) with provider, term, and cost. These have no Dynamics 365 native entity. We create an FIProduct custom table linked to the Opportunity so finance product history is queryable in Dynamics 365 reporting.

VinSolutions lead source values (website, showroom visit, call, referral) map to Dynamics 365 Lead.LeadSource pick-list. Custom lead sources in VinSolutions require value-mapping configuration before migration — we surface these in the pre-migration field audit. Any VinSolutions lead source without a matching Dynamics 365 option requires a custom pick-list value to be created during the schema setup phase; the pre-migration audit flags these gaps for your Dynamics admin to resolve before migration runs.

VinSolutions call logs, emails, and notes attach to contact or vehicle records. We migrate calls as Task records with Type='Phone Call', emails as Email (activitypointer) records, and notes as Annotation records. Original timestamps and owning user are preserved; the Regarding lookup points to the migrated Contact or Lead.

VinSolutions deal records map to Dynamics 365 Opportunity. The deal name maps to Opportunity.Name, amount to Amount, stage to StageName, and close date to CloseDate. Each VinSolutions pipeline maps to a Sales Process in Dynamics 365 — we create the Sales Process before data lands so stage pick-list values are scoped correctly.

VinSolutions owner references resolve to Dynamics 365 SystemUser records by email address match. Records with no matching email are flagged in the pre-migration audit report — your team either invites the user to Dynamics 365 first or assigns them to a fallback owner. No record lands without an assigned OwnerId.

VinSolutions file attachments on records are downloaded and re-uploaded to the related Dynamics 365 record's SharePoint document location. File size limits apply (default 10MB per file in Dataverse). We preserve the original filename and upload date as metadata. If any attachment exceeds the Dataverse file size limit, we flag it for chunked upload or alternative storage strategy during migration. SharePoint integration must be enabled in your Dynamics 365 environment before the attachment migration phase runs.