Migrate from Pipeliner CRM to Pipedrive

Pipeliner Accounts map directly to Pipedrive Organizations. We use the account name as the dedupe key and preserve all standard fields (address, phone, website, industry, type). Organization is created before any Person import so that the linked_to_person and org_id references resolve at insert time. Custom fields on Pipeliner Accounts migrate to Pipedrive custom fields on Organization, which can be added directly from the import mapping page per Pipedrive's UI.

Pipeliner Contacts map to Pipedrive Persons. We preserve the Contact-to-Account linkage by resolving the parent Organization ID during import. Email address is the primary dedupe key; any Persons already existing in Pipedrive are flagged for manual merge or skip based on the customer's dedupe preference. Custom fields on Contacts migrate to Person custom fields.

Pipeliner Leads map to Pipedrive Leads. We preserve lead status, source, rating, and any custom fields. Pipedrive treats Leads as a separate pipeline object distinct from Persons, allowing the customer to maintain a pre-qualification pipeline before converting to a Person and Deal. Lead owner maps to Pipedrive user by email match.

Pipeliner Opportunities map to Pipedrive Deals. The Pipeliner pipeline and stage assignment normalizes to the primary admin-defined pipeline schema, collapsing any per-user stage overrides into the canonical Pipedrive pipeline stage. Deal value, probability, expected close date, and custom fields migrate directly. The Opportunity-to-Account link becomes the Deal's linked Organization; Opportunity-to-Contact links become Deal Participants.

Pipeliner pipelines with per-user stage definitions require normalization before mapping. We extract the primary admin-defined pipeline schema and use it as the target Pipedrive pipeline configuration. Each Pipeliner stage maps to a Pipedrive stage with corresponding probability and position. Per-user overrides are collapsed; the migrated Deal reflects the admin-defined canonical stage rather than the per-viewer variant.

Pipeliner Quotes map to Pipedrive Deals with Products attached. The Quote header fields (title, total, expiration) become Deal fields; the Quote line items map to Products attached to the Deal. Product catalog entries from Pipeliner's Product Grid pre-populate the Pipedrive Products catalog. We do not migrate Pipeliner Quote PDFs as Pipedrive does not have a native quote document object; the customer exports these separately.

Pipeliner Projects are date-based task groups linked to Accounts, Contacts, or Opportunities. Pipedrive does not have a native project object. We migrate Projects as a series of linked Activity records (tasks with due dates, descriptions, and status) attached to the parent Deal or Organization, or as a named custom field group if the customer requires explicit project-level grouping in Pipedrive. This is decided during scoping.

Pipeliner Tasks map to Pipedrive Activities. We preserve subject, body, status, priority, due date, and assigned owner. Owner resolution uses email match against Pipedrive users. Tasks linked to specific Opportunities become Activities attached to the corresponding Deal; Tasks without a Deal parent attach to the linked Person or Organization.

Pipeliner Appointments map to Pipedrive Activities with type set to calendar event. Start time, end time, location, and attendees migrate. Attendee resolution matches by email against Pipedrive Persons and Users. We do not migrate appointment bodies beyond the standard fields.

Pipeliner Products in the Product catalog map to Pipedrive Products. Product name, code (SKU), unit price, and description migrate. Products are created before Deal migration so that Products can be attached to Deals via the Deal-Product association during the Deals phase.

Pipeliner fully custom entities require explicit scoping per migration. We map each custom entity to either Pipedrive custom fields on the nearest standard object (Organization, Person, Deal) or a named custom field group with lookup references if the entity has relationships to standard objects. Custom entity schema, field types, and lookup relationships are documented during discovery and mapped individually per migration scope.

Pipeliner Owners map to Pipedrive Users by email match. Any Owner without a matching Pipedrive user goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Pipeliner owners map to inactive Pipedrive users so that historical assignment is preserved.