Migrate from Vinsolutions to Twenty CRM

VinSolutions contacts map directly to Twenty People. Every contact's first name, last name, email, phone, and job title transfer as Twenty field equivalents. Contacts without a primary company receive a placeholder Company in Twenty or are linked to your specified fallback account. Owner assignment resolves by email match against Twenty workspace members.

VinSolutions dealership-company records map to Twenty Companies. Company name, address, phone, website, and industry fields transfer directly. Parent-child dealership hierarchies (if your group operates multiple rooftops under one VinSolutions instance) map to Twenty's Company relation field — the parent company must migrate first to avoid orphaning child records.

VinSolutions internet leads are contacts with a lead_source field and a process_status metadata block. We migrate them as Twenty People records and preserve the lead_source value in a custom field (VinLeadSource__c). The process_status block migrates as a custom text field (VinProcessStatus__c) for manual review and workflow-triggering on the Twenty side.

VinSolutions vehicle-linked opportunities map to Twenty Opportunities. Each opportunity has a vehicle object attached (VIN, year, make, model, stock number) — we store these as a JSON block in Twenty's Opportunity custom field (VehicleDetails__c) since Twenty has no native vehicle object. Deal stage (Prospecting, Deal Desk, F&I, Sold) maps to a Twenty Opportunity Stage pick-list, which your admin defines to match your sales process.

VinSolutions logged calls, emails, meetings, and notes attach to both contact and opportunity records. We map calls and emails to Twenty Tasks (type field set to Call or Email), meetings to Twenty Tasks with type=Meeting and start/end time fields populated. Notes migrate as Twenty Notes attached to the relevant People or Opportunity record. Original timestamps and owner IDs are preserved.

VinSolutions process rules (lead assignment triggers, stage-change alerts, email-on-event, team notifications) do not migrate — they have no equivalent in Twenty's trigger-action model and the logic is platform-specific. We export the full process definition as a structured JSON playbook that your Twenty admin uses to rebuild equivalent rules in Twenty's workflow builder.

VinSolutions vehicle inventory records (VIN, mileage, pricing, options) have no direct Twenty equivalent. We map these to a Twenty Custom Object named Vehicle (or Inventory), creating it in Twenty's Settings → Data Model before migration runs. Each vehicle record links to its corresponding Opportunity via a custom relation field on the Opportunity.

VinSolutions users and owners resolve by email match against Twenty workspace members. Your admin must invite all active VinSolutions users to Twenty before migration so their email addresses exist in Twenty's member list. Unmatched owners are flagged pre-migration and assigned to a fallback Twenty user or a generic 'Unassigned' placeholder.

VinSolutions file attachments (deal documents, trade-in photos, F&I forms) are stored against opportunity or contact records. We migrate file names, download URLs, and attachment dates as a custom text field (AttachmentLinks__c) on the relevant Twenty record. For files hosted in VinSolutions' proprietary storage, we include a note that links must be re-uploaded to your preferred file storage post-migration.

VinSolutions tracks lead attribution across multiple dimensions: internet source (website form, third-party lead provider), campaign tag, and BDC assignment. We preserve all attribution fields as custom text or pick-list fields on both the Twenty People and Opportunity records, so your attribution reporting has continuity in the new CRM.

VinSolutions stores DMS deal matching status (whether a deal has been confirmed in the dealer management system). This flag and the DMS reference number migrate as a custom text field (DMSReference__c) on Twenty Opportunities. DMS sync status is informational in Twenty — your team manually reconciles F&I outcomes post-migration.

VinSolutions desking tool captures payment structure, trade-in value, APR, term, and deal notes. These values are stored in a structured block in VinSolutions. We split them into individual custom fields on the Twenty Opportunity record: DeskingPayment__c, DeskingTradeIn__c, DeskingAPR__c, DeskingTerm__c, DeskingNotes__c — so your team can report on deal structure metrics directly in Twenty.