Migrate from Perfect Portal to Microsoft Dynamics 365 Sales

Perfect Portal Matters contain the case name, client reference, status, and all nested parties and milestones. Dynamics 365 has no native Matter equivalent — we map Matters to a custom Opportunity table, creating custom fields for MatterType, CaseReference, BillingArrangement, and priority. The Opportunity Name maps from Matter.MatterName or Matter.CaseReference.

Direct map. MatterName populates Opportunity.Name as the primary display label. Where MatterName is empty, we use Matter.CaseReference as a fallback Name value. The display label appears in Dynamics 365 pipeline views, related lists, and reporting charts, so selecting the most descriptive field ensures your team immediately recognises each record without opening it.

Perfect Portal fee amounts map to EstimatedValue on the Opportunity record. Where Perfect Portal stores fee ranges rather than a single amount, we populate EstimatedValue with the midpoint and flag it in EstimatedValue_Source__c. This preserves transparency — your pipeline totals use a consistent numeric value, while the source flag lets finance teams filter or exclude estimated ranges in custom reports.

Perfect Portal Matter statuses (Active, On Hold, Closed Won, Closed Lost) map to Dynamics 365 StateCode (Open/Won/Lost) plus a custom pick-list field (PP_Status__c) preserving the exact source label. Value-by-value mapping ensures no status label is lost in translation. The PP_Status__c field displays the original Perfect Portal status in Dynamics 365 views, so your team instantly sees the legacy status without cross-referencing the source system.

Dynamics 365 sets CreatedOn at record-creation time during migration. We preserve the original Matter.OpenedDate as PP_OpenedDate__c (Date field) so reports reflect when the matter actually began in Perfect Portal. This custom field appears in Dynamics 365 advanced find, pipeline reports, and Power BI dashboards, giving your team the true case origin date for compliance tracking and historical analysis.

Owner resolved by email match against Dynamics 365 users. Unmatched fee earners are flagged before migration — your team either creates the user in Dynamics first or assigns to a fallback owner. No record lands without a valid OwnerId. The exception report lists each unresolved email with a proposed fallback owner, so your admin resolves all gaps before the migration run begins.

Organisational parties map to Account records. Individual parties map to Contact records. Where a Matter has multiple parties of mixed types, the primary party becomes the Account/Contact and additional parties are added via Account Contact Roles with a PP_PartyRole__c custom pick-list label.

Party records with contact details (email, phone, address) map 1:1 to Dynamics 365 Contact. Contact.FullName maps from Party.FullName; Contact.EmailAddress1 maps from Party.Email. OwnerId on Contact resolved by email match to Dynamics users. Where a contact already exists in Dynamics, we match on EmailAddress1 to avoid duplicating records, merging in any additional fields present in the Perfect Portal Party record.

Dynamics 365 has no native milestone construct. We map each Perfect Portal Milestone to a pair of custom fields: PP_Milestone_[Name]_Date__c (Date) and PP_Milestone_[Name]_Completed__c (Boolean). Stage-transition timestamps from Perfect Portal are preserved as separate custom datetime fields for audit continuity. These fields display in the Opportunity timeline view, giving your team a chronological record of every stage entry and exit without querying custom reports.

Perfect Portal stores document references as URLs pointing to internal storage. We download each document and re-upload to the relevant Account or Contact SharePoint document location, then write the file URL into a PP_DocumentURL__c custom field on the parent Opportunity record.

Matter notes and activity log entries migrate as Dynamics 365 Annotations on the parent Opportunity. Original timestamps and author information are preserved in the Annotation.CreatedOn and Annotation.OwnerId fields. Each Annotation record is linked to the Opportunity, so your team sees the full activity history in the Dynamics 365 timeline without switching between screens or exporting data to audit logs.

Matter status updates and system-logged changes migrate as closed Tasks on the Opportunity. Task.Subject is set to 'Matter Update: [status change description]' and Task.ActualEnd reflects the original update timestamp. These closed Tasks appear in the Opportunity activity history, giving your team a chronological audit trail of every status change without relying on external log exports or manual spreadsheets.