Migrate from Delta Sales CRM to Pipedrive

Delta Contacts map directly to Pipedrive Person records. The standard contact fields (name, phone, email, address) map to Pipedrive's name, phone, email, and address fields. We preserve the link to the originating Delta Company record as a custom field delta_company_id__c for reference. Delta's contact-specific custom fields migrate to Pipedrive Person custom fields of equivalent type (text, number, date, or picklist). All Person records import before Deals to satisfy the PersonId lookup requirement.

Delta Companies map to Pipedrive Organizations. The company name, website, industry, phone, and address fields map directly. Pipedrive Organizations are created before Persons so that the organization_id reference on Person is resolved at insert time. We use company name as the dedupe key to prevent duplicate Organizations during import. Company-specific custom fields migrate to Pipedrive Organization custom fields.

Delta Leads map to Pipedrive Lead records. We preserve lead status, source attribution, and owner assignment from Delta. If Delta Leads have been partially converted to Deals without a full conversion workflow, we preserve the partial state as custom fields and create matching Pipedrive Leads. Pipedrive Lead Status values are configured during Pipedrive setup to match Delta's lead lifecycle stages.

Delta Deals map to Pipedrive Deals with direct field mapping for deal title, value, stage, expected close date, and probability. The Delta pipeline and stage assignment maps to a Pipedrive pipeline and stage configuration that we build in Pipedrive before migration. Deal owner resolves by matching Delta owner email to a Pipedrive User. Lost-won reasons from Delta custom fields become custom deal fields in Pipedrive.

Delta pipelines and their stage definitions export as configuration metadata. We create Pipedrive pipelines with matching stage names, stage order, and probability percentages. Stage probabilities round to Pipedrive's integer-percentage format. If Delta has multiple pipelines, each becomes a separate Pipedrive pipeline. Stage colors and stage win/loss flags are configured in Pipedrive to match Delta's visual pipeline presentation as closely as possible.

Delta Products map to Pipedrive Products. Product name, SKU, price, unit, and description migrate directly. We create the Product records in Pipedrive before importing any Deals that reference them, so the product_id reference resolves at import time. Products without deals attach as orphan catalog items with no migration risk.

Pipedrive does not have a native invoice object in its standard CRM tier. We map Delta invoice headers (invoice number, date, total amount, status) as custom fields on the associated Pipedrive Deal. Line items are appended as a custom text field in structured format (product name, quantity, unit price per line). If the customer requires full invoice reconstruction, this is documented in the migration scope and may require a Pipedrive invoice app from the marketplace.

Delta Payment records (amount, date, method, associated invoice) migrate as structured custom fields on the linked Pipedrive Deal. Payment method maps to a picklist custom field; payment date and amount map to date and currency fields. If multiple payments exist per invoice, we concatenate them into a multi-entry custom text field with a documented format.

Delta Activities map to Pipedrive Activities by type: calls map to Activity type = Call, meetings to Activity type = Meeting, tasks to Activity type = Task, and follow-ups to Activity type = Task. We chunk activity exports by rep and date range (90-day windows) to avoid export timeouts on large activity histories. Each Activity links to the correct Person and Deal by resolving the parent record IDs at migration time. Activity dates and assignees preserve from Delta's original values.

Delta custom fields across all objects migrate to Pipedrive custom fields of equivalent type. We pre-create Pipedrive custom fields before importing any data so the fields exist during import. Picklist custom fields require value-list alignment between Delta and Pipedrive. Multi-select picklists in Delta map to Pipedrive multi-select custom fields. All custom field definitions are documented in the scoping phase with their source field type, target Pipedrive field type, and any transformation logic required.

Delta Beat Plans have no direct Pipedrive equivalent. We export the beat plan structure (route name, assigned rep, customer list, sequence order, visit frequency) as a structured CSV and create a Pipedrive custom object (BeatPlan__c) with fields for route_name, assigned_user, customer_person_id, visit_sequence, and frequency. We deliver this as a separate import package with a documented custom object schema so the admin can configure it in Pipedrive after migration. This is explicitly scoped as a reference reconstruction, not an automated migration of Delta's routing logic.

Delta file attachments migrate as binary blobs with their associated record ID preserved. We export attachments in their original format (images, PDFs, documents) and store them in a flat directory structure keyed by record ID. The migration package includes a manifest mapping each attachment to its parent Delta record. Because Pipedrive's bulk import does not support file attachment ingestion, we deliver attachments as a downloadable package with a per-record reference guide for the customer's admin to upload manually to Pipedrive after migration.