Migrate from Vinsolutions to Pipedrive

VinSolutions Person records map directly to Pipedrive Persons on a 1:1 basis. Standard contact fields including name, email address, phone number, and physical address carry over without transformation. The primary DMS-linked company association from VinSolutions — the dealership or business a contact is tied to — becomes the Organization lookup field on the Pipedrive Person record. This Organization lookup must resolve to a previously migrated Organization, so Organizations migrate before Persons in the sequence.

VinSolutions company records representing the dealership entity or customer business organization map to Pipedrive Organizations. Core business fields including company name, website URL, industry classification, number of employees, and full address translate directly. When a DMS-linked dealer group hierarchy exists in VinSolutions, the parent-child relationship between franchise locations maps to the Organization's parent_organization_id field in Pipedrive, provided the parent organization migrates first to establish the ID reference.

VinSolutions deal records map to Pipedrive Deals. Deal name, monetary value representing sale price or gross profit, lifecycle stage, expected close date, and assigned owner all carry over. DMS vehicle data attached to the deal — including vehicle identification number, stock number, trade-in valuation, and F&I product selections — migrates as Pipedrive custom fields since Pipedrive has no native vehicle object. Stage mapping requires value-by-value configuration because VinSolutions stage names differ from Pipedrive stage names.

VinSolutions leads that serve as pre-contact routing records map to Pipedrive Leads. Lead status classification, source attribution, and assigned owner carry over as direct field mappings. Pipedrive Leads inherit all custom fields configured on the Deal object, so DMS-linked lead scoring values from VinSolutions become a custom numeric field on Pipedrive Leads without requiring a separate field creation step for the Lead object.

VinSolutions activity records for calls, emails, and meetings map directly to Pipedrive Activities. Activity type classification, subject line, scheduled date and time, owning user, and linked contact or deal reference all resolve without transformation. Showroom visit activities from VinSolutions that lack a specific Pipedrive equivalent map to Pipedrive Tasks with a custom type label field to preserve the activity category distinction.

VinSolutions notes attached to contacts, companies, or deals migrate as Pipedrive Notes linked to the corresponding Person, Organization, or Deal record. Note body content, original creation timestamp, and owning user all carry over. Rich-text formatting is preserved where the source format is compatible with Pipedrive's note rendering, ensuring that formatted content like bullet points and bold text maintains its structure after migration.

File attachments associated with VinSolutions records are downloaded from the source system and re-uploaded to Pipedrive as Files, with each file linked to its corresponding Person, Organization, or Deal record. Pipedrive enforces a default file size limit of 25MB per file, so any attachments exceeding this threshold require either compression or a reference link strategy before the migration run executes.

VinSolutions custom contact properties map to Pipedrive custom fields on the Person object. Each custom property requires a separate field creation step in Pipedrive using the API with Pipedrive's hash-key field naming convention before the migration run. The field type in Pipedrive matches the VinSolutions source type — text fields remain text, numeric fields remain number, picklist fields require value-by-value mapping if source values differ from Pipedrive's standard picklist options.

VinSolutions deal custom properties — including DMS-linked fields like VIN, trade-in value, F&I product flags, and showroom process identifiers — map to Pipedrive Deal custom fields. Each property requires a separate API-based field creation step with hash-key naming. F&I-specific picklist values require explicit value-by-value mapping since no automotive equivalent exists in Pipedrive's standard field type definitions, and every picklist option must exist in Pipedrive before records migrate.

VinSolutions CRM processes and automated workflows — such as showroom visit triggers, DMS-matched task firing, stage-advance automations, and performance-based alerts — have no Pipedrive equivalent because they are configuration objects with logic trees rather than data records. FlitStack AI exports every process definition as a documented rebuild reference, but the Pipedrive admin must recreate these using Pipedrive's Automation builder. Pipedrive automations are tier-gated: Lite has zero, Growth allows 30 active, Premium permits 60, Power supports 90, and Ultimate offers unlimited automations.

VinSolutions DMS vehicle records — including VIN, MSRP, book values, inventory status, and vehicle condition notes — link deals to the complete vehicle lifecycle. Pipedrive has no DMS or vehicle object and no native concept of vehicle inventory. These records require either a Pipedrive Product record with custom fields for vehicle attributes, or a reference document maintained in a linked external system. We surface this structural gap in the migration plan before data lands so the team can decide on a handling strategy.

VinSolutions Performance Manager consultation notes represent informal coaching records that exist outside the standard CRM data model — they are advisory annotations stored separately from deals and contacts rather than structured CRM fields. We treat these as Notes attached to the relevant Deal or Person record in Pipedrive for continuity of reference, with a note indicating they represent coaching content rather than transactional CRM data. This preserves access to the information without requiring a custom field for unstructured advisory text.

VinSolutions user records resolve to Pipedrive users through email address matching — the primary key for user identity in both platforms. All CRM records are re-assigned to the matched Pipedrive user during migration, preserving the original owner context in Pipedrive's owner_id field. Any VinSolutions owner without a corresponding Pipedrive user is flagged explicitly before the final migration run executes, requiring team assignment or user creation in Pipedrive first.