Migrate from Onpipeline to Pipedrive

Onpipeline Contacts migrate directly to Pipedrive People. The primary person fields (name, email, phone, address) map 1:1 to Pipedrive Person fields. Tags applied to Onpipeline Contacts migrate as Pipedrive person labels. Custom fields on Contact migrate to Pipedrive custom Person fields created in the destination account before import. The email field is used as the dedupe key to prevent duplicate People records during import.

Onpipeline Company records map to Pipedrive Organizations. The company name becomes the Organization name, and domain information becomes the Website field. Onpipeline's multi-Contact-per-Company relationship is preserved: all People linked to an Onpipeline Company are imported as People linked to the same Organization via the Person-to-Organization relationship in Pipedrive.

Onpipeline Deals migrate to Pipedrive Deals with value, stage assignment, and custom fields preserved. Each Deal maintains its linked Contact and optionally its linked Company through the three-part association: Pipedrive Deals can link to a Person (required) and an Organization (optional), which maps directly to Onpipeline's Contact + optional Company on a Deal. The Deal value (amount) maps to Pipedrive's weighted value field.

Onpipeline's custom stage names and per-stage probability percentages map to Pipedrive Pipeline stage names and probability values. We configure Pipedrive Pipelines and Stages before migration, renaming each stage to match the Onpipeline stage hierarchy. Stage order and probability percentages transfer exactly, with rounding to Pipedrive's integer probability format.

Onpipeline Products (name, SKU, price, stock quantity) migrate to Pipedrive Products. Stock quantity is stored as a custom field on Pipedrive Product since Pipedrive does not have native inventory tracking. SKU migrates as the Product code field. Products are imported before Deals so that Deal line items can reference the correct Product ID.

Onpipeline Quotes with line items migrate as Pipedrive Sales Documents if the customer has the Document add-on enabled. Quote headers (linked Contact, Deal, total value) map to Document fields, and line items transfer as Document line items. Pipedrive's Document add-on supports e-signature via DocuSign or HelloSign integrations. If the customer does not activate the Document add-on before migration, Quote records are stored as custom Deal fields and a written rebuild plan is delivered.

Onpipeline Events (calendar appointments with datetime, duration, assigned user, and description) migrate to Pipedrive Activities with type Meeting. The assigned user maps by email match to a Pipedrive User. Activity date and time preserve from Onpipeline. Events without a user assignment are logged under the Deal or Contact owner as the activity assignee.

Onpipeline Tasks migrate to Pipedrive Activities with type Task. Status (open, completed), due date, and priority transfer. Task descriptions become Pipedrive Activity notes. Assignments migrate by resolving the Onpipeline user to a Pipedrive User by email.

Onpipeline Notes attached to Deals or Contacts migrate as Pipedrive Notes. The note body text and creation timestamp preserve. Notes linked to both a Deal and a Contact are attached to the Deal in Pipedrive, with a reference to the linked Person in the note body. Notes with file attachments transfer the file reference as a content note link.

Onpipeline custom fields on Contacts, Companies, Deals, and Products migrate to Pipedrive custom fields on the equivalent objects. We extract the custom field schema (field name, type, and valid values) from Onpipeline during scoping and create matching Pipedrive custom fields before import. Text, number, date, and picklist field types map to Pipedrive field types of the same name. Multi-select picklists in Onpipeline map to Pipedrive multi-select fields.

Onpipeline Users referenced as Deal owners and activity assignees map to Pipedrive Users by email address. We run a pre-migration user reconciliation step to confirm that all Onpipeline users have corresponding Pipedrive accounts or are provisioned before record import. Any orphaned assignments (user in Onpipeline without a Pipedrive counterpart) are flagged in a reconciliation report for the customer's admin to resolve before the activity phase begins.