Migrate from Drivecentric to Freshsales

Drivecentric leads map directly to Freshsales Lead. The primary person-level record in Drivecentric (whether classified as Lead or Contact) lands as a Freshsales Lead. Drivecentric's AI-assigned task counts and duplicate-merge history are not carried forward — those are Drivecentric-specific behaviors.

When Drivecentric shows a Deal attached to a Lead, the Lead converts in Freshsales to a Contact record linked to an Account. Freshsales' Lead Conversion creates both records and optionally an Opportunity. Field mapping for the conversion must be configured in Freshsales Admin settings before migration to avoid data loss on the Contact and Account sides.

Drivecentric company records map 1:1 to Freshsales Account. The dealership name, address, phone, and website fields transfer directly. Multi-rooftop dealer groups may have a parent-company record in Drivecentric that maps to a parent Account in Freshsales using the Parent Account field.

Drivecentric Deals map to Freshsales Opportunity (sometimes labelled Deal in the Freshsales UI). The deal name, amount, stage, close date, and owner transfer directly. Pipeline stages in Drivecentric map to Freshsales deal stage values via value mapping. F&I product attachments on the Deal require mapping to Freshsales Products on the Opportunity.

Drivecentric deal pipelines map to Freshsales Deal Pipelines. Each Drivecentric pipeline becomes a separate Freshsales pipeline. Stage names, probabilities, and forecast categories map value-by-value. If Drivecentric uses one pipeline for new vehicles and another for used vehicles, both transfer as separate Freshsales pipelines.

Drivecentric call and email logs map to Freshsales Task records with Type = Call or Email. Drivecentric meetings map to Freshsales Event with start/end times and location preserved. Original timestamps and assigned owner are carried forward. Notes attach to the parent record (Lead, Contact, or Opportunity) using Freshsales' association model.

Drivecentric notes transfer into Freshsales as Note objects that are linked to the corresponding Lead, Contact, or Opportunity record via Freshsales' association model. Where Drivecentric exports support rich-text formatting, that formatting—including bold, hyperlinks, and bullet lists—is retained in Freshsales notes. The original Drivecentric record ID is stored in a custom field on each note to preserve lineage and enable audit trails after migration.

F&I products and service contracts attached to Drivecentric Deals map to Freshsales Products. The product name, price, and description transfer. If Drivecentric stores line items with quantity and discount per deal, those map to Freshsales Opportunity Line Items on the Opportunity record.

Drivecentric custom fields — such as vehicle VIN, year/make/model, trade-in value, credit application status — have no direct Freshsales equivalent and must be created as custom fields in Freshsales before migration. The custom field name and pick-list values are preserved. Freshsales custom fields use snake_case naming in the API.

Drivecentric owner IDs resolve to Freshsales users by email match. FlitStack flags any Drivecentric owner whose email has no corresponding Freshsales user account before migration. Those records are assigned to a fallback owner or held pending user provisioning in Freshsales.

Drivecentric automations — including AI task generation rules, lead-response sequences, and follow-up workflows — do not transfer. They must be rebuilt using Freshsales' Workflow automation builder or Sales Sequences. FlitStack exports the Drivecentric automation definitions as a reference document for your Freshsales admin.