Migrate from Drivecentric to Pipedrive

DriveCentric contacts map directly to Pipedrive Persons. DriveCentric's company-on-contact model translates to Pipedrive's org_id lookup — the contact's primary company must first exist as an Organization record before the contact migrates. DriveCentric N:N contact-company associations are represented as Person-Organization relationships in Pipedrive. All contact fields (name, email, phone, address components) map directly to corresponding Pipedrive Person fields. Owner assignments transfer via email matching against Pipedrive users.

DriveCentric company records map 1:1 to Pipedrive Organizations. If DriveCentric supports parent-company hierarchies, these map to Pipedrive's parent_org_id field to preserve organizational structure. Multi-location dealerships map as separate Organization records linked by parent_org_id. All standard company fields (name, domain, industry, phone) transfer directly to matching Pipedrive Organization fields.

DriveCentric deals map to Pipedrive Deals. The deal's primary contact resolves to a Person via the person's ID, and the associated company resolves to an Organization. Stage, amount, and close date transfer directly. Stage probability is re-applied based on the target Pipedrive pipeline's configuration. The deal owner resolves via email match. Original DriveCentric create dates and stage-transition timestamps are preserved as custom datetime fields on the Pipedrive Deal.

DriveCentric pipeline stage names map value-by-value to Pipedrive Deal stages within the target pipeline. Probability and forecast category are re-applied per Pipedrive pipeline settings for each stage. Stage-entered timestamps from DriveCentric are preserved as custom datetime fields on the Deal for historical reporting continuity. All stage configurations must be recreated in Pipedrive before migration begins.

DriveCentric automotive properties — Vehicle Identification Number, trade-in value, last service date, vehicle condition scores — have no Pipedrive standard equivalent. FlitStack creates Pipedrive custom fields of the matching type (text, monetary, date) on the appropriate object before migration. The field key in Pipedrive is a hash generated at field creation; we handle mapping post-creation so values land in the correct custom field.

DriveCentric engagement records (calls, emails, meetings, notes) map to Pipedrive Activities. Original timestamps, owners (resolved by email match), and the activity type are preserved. The activity subject and body carry over from DriveCentric's engagement record. Call logs map with type='call', emails with type='email', and meetings preserve start/end times.

DriveCentric file attachments on contacts, companies, and deals are downloaded from DriveCentric storage and re-uploaded to Pipedrive as CRM Files, linked to the corresponding Person, Organization, or Deal record. Inline images embedded in notes are extracted and re-hosted as Pipedrive file attachments. All file metadata (filename, upload date) is preserved.

DriveCentric owner IDs are resolved by email match against Pipedrive users. If a DriveCentric user email does not match an existing Pipedrive user, the record is assigned to a designated fallback owner and flagged for admin review. DriveCentric users must be invited to Pipedrive before migration for full owner coverage. A pre-migration owner coverage report is generated to identify unmatched users.

DriveCentric internal record IDs are preserved as a custom Source_System_ID__c field on each Pipedrive object for traceability and delta-run de-duplication. Original DriveCentric create dates are stored as custom datetime fields on each object since Pipedrive sets CreatedDate at migration time. This preserves the full record history timeline in Pipedrive for reporting continuity.

DriveCentric automations, workflows, and sequences do not migrate. They are tightly coupled to DriveCentric's event model and have no 1:1 translation in Pipedrive. FlitStack exports DriveCentric workflow definitions as a structured rebuild reference document (JSON and PDF) for your Pipedrive admin to reconstruct in Pipedrive Automations and Sequences after migration.