Migrate from Perfect Portal to Pipedrive

Perfect Portal clients map directly to Pipedrive Persons. Email address is the primary lookup key. Clients with multiple matters appear as a single Person record linked to multiple Deals. All existing contact details, including phone numbers and addresses, are transferred to the Person record. Duplicate detection uses email as the anchor, ensuring a single unified view per client across Pipedrive.

If the client is a business entity, Perfect Portal's client organisation maps to Pipedrive Organization. Sole-trader clients have no separate Organisation record — only the Person record exists. The Organisation record captures company name, website, and address. For sole traders, all contact information remains on the Person record, avoiding redundant entries. This separation mirrors Pipedrive's Person‑Organization relationship model.

Perfect Portal third-party parties map to Pipedrive Persons with an Organisation link. Their role in the matter is preserved as a custom Person field (Third_Party_Role__c) since Pipedrive has no native third-party access model. The Third_Party_Role__c field records the party type (estate agent, mortgage broker, referrer) and can be used for segmentation and reporting. Additional contact details such as email and phone are transferred to the Person record for full traceability.

Each Perfect Portal matter maps to one Pipedrive Deal. The Matter_Number__c custom field preserves the original Perfect Portal matter identifier for traceability. Matter type (sale, purchase, remortgage) maps to a custom Deal field. The deal title is set to the matter description for straightforward identification. Deal value, owner, and expected close date are transferred from the matter record, while the custom fields capture type and identifier.

Perfect Portal matter stages (Instructed, Searches, Compliance, Completion) map value-by-value to Pipedrive deal stages. We apply a stage-mapping table before migration and validate that every source stage has a destination stage destination. Any unmapped stages trigger a review flag so the mapping can be adjusted before the migration run. This ensures no stage history is lost or misaligned during import.

Perfect Portal records when each matter stage was entered. Pipedrive's stage history is not a native field — we preserve each stage-entered timestamp as a custom datetime field (Stage_[Name]_Entered__c) on the Deal for reporting continuity. These datetime fields enable SLA reporting and client turnaround analysis even though Pipedrive does not store native stage timestamps.

Perfect Portal automated client-update emails and SMS notifications tied to matter stages have no Pipedrive equivalent. We export the template definitions as a reference document for rebuilding as Pipedrive Automations post-migration. The exported templates include trigger conditions, recipient logic, and message bodies, giving your Pipedrive admin a clear blueprint for recreating automated client communications.

Matter documents and file attachments are downloaded from Perfect Portal and re-uploaded to Pipedrive Files attached to the corresponding Deal. File size limits apply (25MB per file in Pipedrive). Large files exceeding the limit are split or compressed, and each file retains its original name and metadata. We also preserve the link between the file and the specific matter for straightforward retrieval.

Matter activities (calls, emails, meetings, notes) map to Pipedrive Activities. Each activity preserves its original timestamp and owner. Bulk activity migration is subject to Pipedrive's API rate limits — we paginate by date range to avoid truncation. Date-range pagination ensures that activity history is imported in manageable chunks, reducing the risk of hitting rate limits and maintaining data integrity.

Perfect Portal custom matter fields (property address, mortgage lender, referring solicitor, etc.) require pre-creation in Pipedrive as custom Deal fields before migration. We provide a field-creation checklist as part of the schema setup plan. The checklist includes field name, type (text, number, picklist), required flag, and any picklist values. This ensures all custom fields are ready before the migration run, preventing data loss.