Migrate from Pega Sales Automation to Pipedrive

Pega Accounts map directly to Pipedrive Organizations. Account is the top-level entity with no parent dependencies in Pega, making it the import anchor. We map standard fields including AccountName, Industry, Website, Phone, Address, and any custom fields. The Organization id returned from the first import batch becomes the lookup reference for all dependent Contact and Activity records.

Pega Contacts map to Pipedrive Persons. The Contact-to-Account relationship (pyId or AccountID reference) maps to the Person's org_id field in Pipedrive. We preserve name fields, email, phone, title, and any custom fields. Persons without an email are allowed in Pipedrive but flagged in the reconciliation report for manual verification.

Pega Leads map to Pipedrive Leads, which are a separate object type in Pipedrive for unqualified prospects. We preserve disposition codes from Pega as custom Lead fields or map them to Pipedrive's built-in Lead status values. Pega Lead scores map to a numeric custom field in Pipedrive.

Pega Opportunities map to Pipedrive Deals. The Opportunity-to-Account relationship maps to Deal.org_id; Opportunity-to-Contact relationships map to Deal.person_id. Stage, amount, close date, probability, and owner transfer directly. Pega's Opportunity-Product junction (line items) map to Deal Products in Pipedrive with quantity and price preserved.

Pega Activities (calls, emails, tasks, meetings) map to Pipedrive Activities. Each Activity type (Call, Email, Meeting, Task) maps to the corresponding Pipedrive Activity type. Parent entity resolution uses the Account and Contact lookups already imported. Activity timestamps preserve the original Pega created_at and modified_at values for timeline fidelity.

Pega Products map to Pipedrive Products. ProductCode, name, description, and standard pricing transfer. Pipedrive requires Products to be created before they can be attached to Deals via the Product-specific API call; we sequence this accordingly.

Pega Campaigns map to Pipedrive Campaigns. Campaign status, type, and target audience custom fields transfer. Campaign membership records (which Contacts responded) map to Pipedrive Campaign Contacts with status preserved.

Pega Sales Teams define access control at the entity level. Pipedrive does not have a direct team-sharing model; instead, Pipedrive uses a User-per-seat model where Deals are owned by individual Users. We map Pega team membership to Pipedrive Teams and assign Deal ownership to the primary team member, with a custom field capturing additional team member assignments for audit.

Pega Territories segment Accounts and Users by geography or business unit with rules that trigger on record creation. Pipedrive has no native territory model. We map territory assignments to a custom multi-select picklist field on Organization or Deal, populated from the Pega territory rules evaluated at migration time.

Pega allows unlimited custom fields (properties) on any base entity. Custom fields require manual per-entity mapping because neither platform exposes a bulk discovery endpoint for all custom fields across the schema. We enumerate custom fields entity by entity via the Pega API, then hand-map each to the equivalent Pipedrive custom field (type-matched: text, number, date, enum, multi-select). Pipedrive's custom field limits vary by plan: Essential allows limited custom fields; Advanced and higher tiers allow more.

Pega Work Objects (Cases) are Pega BPM engine wrappers around entities with their own lifecycle states, assignments, and SLA timers. Pipedrive has no native Case object. If the customer's Pega implementation uses Cases to track non-standard entities (disputes, claims, service requests), we map Case records to Pipedrive Deals with a custom case_type__c field and Case status mapped to a Deal stage or custom status field. SLA timers and escalation assignments do not transfer.

Pega stores binary attachments in a Pega Cloud blob store that is not directly portable via API. We preserve attachment metadata (filename, content type, parent entity reference, creation date) as a structured record in Pipedrive. The binary blob itself is not re-imported. Customers with attachment requirements should plan to migrate files separately via a document management integration or cloud storage migration tool.