Migrate from Convert Wire to Pipedrive

Convert Wire contacts migrate to Pipedrive People. Pipedrive People require an optional OrganizationId linking to an Organizations record; contacts without a primary company in Convert Wire land as standalone People without an OrgId. We flag any contact records missing a required linked record during migration so org resolution can be confirmed.

Convert Wire companies migrate to Pipedrive Organizations. Parent-company hierarchies in Convert Wire map to Pipedrive's parent OrganizationId lookup. If Convert Wire stores multiple contacts per company, all contacts link to the same OrganizationId after migration. Orphaned contacts without a company map to an 'Unassigned Organization' placeholder.

Convert Wire deals migrate to Pipedrive Deals with their pipeline stage, close date, monetary value, and owner preserved. Each Pipedrive Deal is linked to an OrganizationId and one or more PersonIds. We validate that stage probability values are non-decreasing across the stage order before importing — a Pipedrive platform requirement.

Each Convert Wire pipeline becomes a Pipedrive Pipeline with stages configured to match the source stage names and order. Stage probability values are mapped value-by-value. Pipedrive requires stages to have non-decreasing probability — if the source data violates this, we adjust probabilities during migration and surface the change in the field-level diff before committing.

Convert Wire call activities migrate to Pipedrive Activities with type='call'. Call outcome, duration, and original timestamp are preserved in the corresponding Pipedrive Activity fields. PersonId and OrganizationId references link each call to the correct contact and organization records, maintaining complete call history context within Pipedrive for future reference and reporting purposes.

Convert Wire email activities migrate to Pipedrive Activities with type='email'. Subject line, body content, and timestamp transfer as-is. Pipedrive's email sync requires an active email integration — we note this as a post-migration setup step if your team uses Pipedrive's native email inbox.

Convert Wire meeting activities migrate to Pipedrive Activities with type='meeting'. Meeting title, start time, end time, location, and attendee details are all preserved in the corresponding Pipedrive Activity fields. The PersonId and OrganizationId links ensure meeting history attaches to the correct contact and organization records for comprehensive activity tracking within Pipedrive.

Convert Wire notes migrate as Pipedrive Notes attached to the corresponding Person, Organization, or Deal record. Rich-text formatting in Convert Wire notes is preserved as plain text in Pipedrive Notes. Notes without a linked entity are flagged for manual assignment post-migration.

Convert Wire custom fields on contacts, companies, and deals migrate as Pipedrive custom fields on their respective objects (Person, Organization, Deal). Pipedrive requires custom fields to be created in the Pipedrive UI or API before data imports — we create them during the Pipedrive setup phase using the Pipedrive API, capturing the generated field keys for mapping.

Convert Wire owner assignments migrate to Pipedrive Users. Matching is done by email address — if a Convert Wire owner email matches a Pipedrive user email, the Pipedrive UserId is assigned. Unmatched owners are flagged before migration for your team to either invite the user to Pipedrive or reassign records to a fallback owner.

Convert Wire leads migrate to Pipedrive Leads in the Lead Inbox. Pipedrive Leads share the same custom field structure as Deals and People — any Convert Wire custom fields on leads are available in Pipedrive's Lead Inbox automatically after the migration plan is executed.