Migrate from Drivecentric to HubSpot

DriveCentric contacts map directly to HubSpot contacts. The HubSpot contact record is the primary destination for all person records. DriveCentric's primary company association maps to the HubSpot contact's Company Name property, which creates a linked Company record. Owner resolution runs by email match against HubSpot users.

DriveCentric tracks lead progression through custom stage fields (New Lead, Contacted, Active Buyer, Sold). We map each stage value to the nearest HubSpot lifecycle_stage: Active Buyer routes to 'SQL', Sold routes to 'Customer'. DriveCentric's original lead-stage history is preserved as a custom text property for reporting continuity.

DriveCentric company records map to HubSpot company records. Company name, domain, address, phone, and industry fields map directly. DriveCentric parent/child company hierarchies (if used) map to HubSpot's Associated Company field. Company records must migrate before contacts so the association resolves correctly.

DriveCentric deals map to HubSpot deals with dealname, amount, closedate, and owner mapping directly. Deal pipeline and stage map to HubSpot's Pipeline and Dealstage properties. DriveCentric's deal-stage history (stage-change timestamps) is preserved as a custom text property on the HubSpot deal.

Each DriveCentric deal pipeline maps to a corresponding HubSpot deal pipeline. Stage names are mapped value-by-value: DriveCentric's 'Finance' stage maps to HubSpot's 'Presentation' or your named equivalent. We deliver a pipeline-mapping table before migration so your HubSpot admin configures the destination pipeline first.

DriveCentric automotive custom fields — VIN, trade-in value, F&I product selection, vehicle stock number, lender name — have no native HubSpot equivalent. These migrate as HubSpot custom properties (created pre-migration on the Contact, Company, or Deal object as appropriate). Field type mapping: numeric fields become number properties, currency fields become number properties with currency notation noted for manual formatting.

DriveCentric logged calls migrate to HubSpot calls with original timestamps, duration, direction (inbound/outbound), result, and owner preserved. The HubSpot call record is associated to the contact it was logged against. Call recordings stored in DriveCentric are not migratable — we document this gap before migration.

DriveCentric logged emails migrate to HubSpot emails with subject, body, direction, and timestamp preserved. The email is associated to the contact record. Attachments stored in DriveCentric's email records are downloaded and re-uploaded to HubSpot Files, linked to the associated contact.

DriveCentric notes migrate to HubSpot notes with original text content, create date, and owner preserved. Rich-text formatting in DriveCentric notes is converted to plain text for HubSpot compatibility. Notes are associated to the relevant Contact, Company, or Deal record. Attachments referenced in DriveCentric notes are downloaded and re-uploaded to HubSpot Files.

DriveCentric file attachments on records are downloaded and uploaded to HubSpot Files. Files are associated back to the original record in HubSpot. HubSpot's file size limit (25MB per file) applies — files exceeding this limit are flagged for manual handling before migration.

DriveCentric owner records are resolved by email match against HubSpot users. Unmatched owners are flagged in a pre-migration report — your team either creates HubSpot user accounts for them or assigns their records to a fallback owner. Records with no assigned owner after resolution are held for manual assignment.

DriveCentric's pre-built DMS integrations (CDK Global, Reynolds & Reynol, DealerSocket) have no equivalent in HubSpot CRM. These integrations must be re-established post-migration using HubSpot's integration marketplace or custom API connectors. We document the full list of active DriveCentric integrations as part of the discovery phase.