Migrate from Kordeva to Pipedrive

Kordeva Contact records (name, email, phone, address, custom fields) map directly to Pipedrive Person. The Kordeva Custom Fields API provides extended contact attributes that we enumerate during discovery and carry as Pipedrive custom fields on the Person object. We resolve any missing Person email as a dedupe risk and flag duplicates before insert. The Person-Organization link is established by resolving the Kordeva company reference during Company/Organization import.

Kordeva Company records map to Pipedrive Organization. Standard fields (name, domain, address) transfer directly. Any Kordeva company-level custom fields become Pipedrive Organization custom fields. The Organization is imported before Person to satisfy the org_id lookup on Person. If a Contact has no company assignment in Kordeva, the Person is created without an org_id and can be linked later from Pipedrive.

Kordeva Deal records map to Pipedrive Deal with pipeline stage names preserved. The Kordeva dealstage value is mapped to a Pipedrive Pipeline and Stage. We configure the Pipedrive pipeline structure before migration: stage names, stage order, and stage probability percentages transfer from Kordeva. Deal owner resolves by email against Pipedrive User records.

Each Kordeva Deal pipeline becomes a Pipedrive Pipeline. Stage names and probabilities migrate as Stage entries within that Pipeline. The customer reviews and approves the pipeline layout before data insert because stage names and order reflect business-specific pipeline logic that varies by team.

Kordeva activity records logged against contacts and deals transfer to Pipedrive Tasks (calls, emails, tasks) and Events (meetings). Each activity carries the original timestamp for activity timeline ordering. We resolve the parent record (Person, Organization, or Deal) by matching Kordeva's contact_id and deal_id to the migrated Pipedrive IDs. Activity owner resolves by email. If Kordeva API access is unavailable and we fall back to CSV, activity history may be incomplete and is flagged in the scoping report.

Kordeva custom field definitions are enumerated via the Custom Fields API during discovery. Each custom field is created in Pipedrive on the target object (Person, Organization, or Deal) with the matching field type. Pipedrive supports 16 custom field types. We map Kordeva field types to Pipedrive equivalents (text to string, dropdown to picklist, multi-select to multi-select picklist). Field labels and API names are preserved to maintain data meaning after migration.

Kordeva Accounts and Invoicing records (invoice amounts, line items, payment status) have no native Pipedrive equivalent because Pipedrive has no accounting module. We map invoice data to Pipedrive Deals with a custom field strategy: invoice number becomes a deal title prefix, invoice amount becomes the deal value, payment status becomes a picklist custom field, and line item descriptions become a text custom field. The customer chooses whether to consolidate multiple invoice line items per account into a single Deal or create separate Deals. Accounts-Invoicing mapping is a configuration step that requires customer review of the data schema before insert.

Kordeva Owner records resolve by email against Pipedrive User accounts. Any Kordeva Owner without a matching Pipedrive User is held in a reconciliation queue. The customer's Pipedrive admin provisions missing Users before record import resumes. Owner assignments on Deals and Activities depend on this resolution.

Kordeva product records (if present in the source environment) map to Pipedrive Products. Product name, code, and price migrate as Pipedrive Product fields. Products must be created before Deals that reference them so that the product_id lookup is satisfied at Deal insert time.

Kordeva Notes linked to Contacts or Deals migrate as Pipedrive Notes attached to the corresponding Person or Deal. Note content, author, and timestamp transfer. We resolve the parent record by matching the Kordeva resource ID to the migrated Pipedrive record ID.