Migrate from Results to Pipedrive

Results Companies map to Pipedrive Organizations. The company domain or website field from Results becomes the Organization's Website field and serves as the deduplication key during import. We resolve any duplicate Organizations by matching on domain before insert to prevent orphaned or split company records in Pipedrive.

Results Contacts map to Pipedrive Persons. Name, email, phone, and address fields migrate directly. Each Person is linked to its parent Organization via the org_id field, which we resolve at migration time by matching the Contact's company reference to the Organization created in the previous phase.

Results Deals map to Pipedrive Deals with stage, value, owner, and close date preserved. Stage probability percentages are calculated from Results deal stage percentages if available. Pipedrive requires a linked Organization (WhatId) on each Deal; we resolve this linkage from the Results deal-company relationship. Any Deals without a company link enter a reconciliation queue for the customer to resolve before final import.

Results pipelines map to Pipedrive Pipelines. We create the Pipeline structure in Pipedrive (pipelines and stages) before migration begins. Stage names and probabilities migrate from Results stage values. Pipedrive requires pipelines to exist before Deals are imported, so this is a pre-migration configuration step.

Results engagement records (calls, emails, meetings, tasks) map to Pipedrive Activity objects using type-specific endpoints. Activity type, subject, content, date, and duration fields migrate with original timestamps preserved to maintain the activity timeline ordering. We map call disposition and outcome values to custom Activity fields in Pipedrive.

Results custom fields migrate to Pipedrive custom fields. We pre-create the destination custom fields in Pipedrive during the schema phase with correctly typed field definitions (text, number, date, dropdown, checkbox, etc.) to satisfy Pipedrive API v2 strict validation. Field type mapping requires verification during the Results scoping call since Results field types may differ from Pipedrive equivalents.

Results owners map to Pipedrive users by email address match. We extract all distinct owner values from Results records, match against the Pipedrive destination user list, and flag any owners without a matching Pipedrive user for manual provisioning before migration resumes. Owner resolution must complete before Deal import because OwnerId is a required reference on Deals.

Results attachments migrate as Pipedrive ContentDocument records with ContentDocumentLink associations to the parent record (Person, Organization, or Deal). Pipedrive imposes file size limits and supports specific file types. We verify attachment sizes against Pipedrive's limits during the scoping export and flag any files requiring alternative handling (e.g., hosted links or cloud storage references).

Pipedrive enforces that each Deal has a WhatId pointing to an Organization. Results Deals can exist without a linked Company, which requires resolution before Pipedrive import. We offer three handling strategies: create a placeholder Organization for unlinked Deals, link them to a designated parent account, or let the customer decide per-record during a reconciliation review before final import.

Results Products map to Pipedrive Products with name, SKU, price, and description preserved. Standard Price Book entries are created in Pipedrive during import. Products must exist before Line Items are imported so that the product reference is satisfied at insert time.