Migrate from Perfectview to Pipedrive

PerfectView's Relation object combines Company and Contact data into a single entity. We split each Relation into one Organization record (using the company name, address, and domain fields) and one or more Person records (using the individual name, email, phone, and role fields). The primary contact within a Relation becomes the primary Person linked to the Organization; additional contacts within the same Relation become secondary Person records. We validate the split against live data before bulk migration to prevent orphaned records or duplicates at the Relation boundary.

PerfectView Activities (calls, emails, meetings, tasks) map directly to Pipedrive Activities with the same activity type labels. The activity timestamp, duration, subject, and body transfer directly. We link each Activity to the resolved Person record (WhoId) and the related Organization record (OrgId) using the Relation context preserved during the split. Activity owner maps from PerfectView's assigned user to Pipedrive's user_id.

PerfectView Lead records map to Pipedrive Lead. Lead status, lead source, and custom fields transfer directly. We link the Lead to an Organization record if a matching company name or domain exists in the migrated data. Leads without a matching organization attach to the primary contact Person instead. The customer's PerfectView lifecycle stage values map to Pipedrive's open, contacted, qualified, or unqualified status with a custom field preserving the original stage label.

PerfectView Cases (support tickets) map to Pipedrive Goals if the destination account is on the Professional plan or above, using the Goal type and label fields to preserve case subject, status, and assignee. If Pipedrive Goals are not available on the customer's selected plan, we map Cases to Activities with type label CASE, assignee, and status preserved as custom fields. Case priority migrates as a custom field on the Goal or Activity. Case conversations migrate as linked Activities or as Note attachments on the parent record.

PerfectView Document records migrate to Pipedrive Files attached to the parent Person, Organization, or Deal record. Document name, description, and upload date transfer as file metadata. The document binary migrates via Pipedrive's file upload API. Linked Relation records are resolved to the corresponding Person or Organization during attachment. Documents without a parent Relation link attach to the primary Organization on the account as a fallback.

PerfectView Quote records with line items map to Pipedrive Deals with Product instances attached via the Deals-Products association. Quote status (draft, sent, accepted, rejected) maps to a custom Deal field. If PerfectView maintains a separate Quote object, we create Pipedrive Deals in the Won stage with a custom field quote_id__c carrying the original PerfectView Quote number. Quote PDF attachments migrate as Files on the Deal.

PerfectView Invoice records migrate to Pipedrive Deals with invoice metadata preserved in custom fields (invoice_number__c, invoice_date__c, payment_status__c, amount_paid__c). Line items migrate as Product instances on the Deal. We flag invoice records during discovery because some teams use invoices for billing tracking rather than pipeline management; in those cases, we discuss whether to import as Deals or as a separate spreadsheet alongside the CRM. Note that invoice numbering may need adjustment if the destination requires sequential numbering.

PerfectView User records (sales reps, admins, case assignees) map to Pipedrive Users by email address match. We extract all distinct owner references across Relations, Activities, Leads, and Cases and resolve each against the destination Pipedrive User table. Any PerfectView owner without a matching Pipedrive User goes to a reconciliation queue for the customer to provision before record migration resumes. Inactive PerfectView users migrate as inactive Pipedrive users to preserve historical assignment.

Custom fields on PerfectView Relations, Activities, and Leads are discovered during the scoping phase via the API and UI export. We map each to an equivalent Pipedrive custom field using the closest matching Pipedrive field type (string, number, date, single-select, multi-select, person, organization, or deal). Multi-select picklists in PerfectView map to Pipedrive multi-select fields. Custom field labels and help text transfer as field description. We validate that the destination Pipedrive plan supports the required custom field count before migration begins.

When a custom field is defined at the Relation level in PerfectView, we determine its subject (individual contact or company) during discovery and map it to the corresponding custom field on Person or Organization in Pipedrive. Fields that apply to both individual and company data (e.g., industry classification, region) map to Organization custom fields. Fields that apply only to individuals (e.g., job title, direct phone) map to Person custom fields. This decision is validated against sample data before bulk migration.

PerfectView Products in the Sales module map to Pipedrive Products with Standard Price Book entries. Product name, SKU, description, unit price, and category transfer directly. We create Pipedrive Standard Price Book entries during the Product migration phase so that Deals can reference them immediately. If PerfectView uses product variants (size, color), these map to Pipedrive Product Variations if the destination plan supports them, or to separate Product records with variant labels in a custom field.