Migrate from Practice Master Pro to Microsoft Dynamics 365 Sales

Practice Master Pro's Client record maps 1:1 to Dynamics 365 Account. The client name maps to Account.Name, primary address fields map to Address fields on Account, and client type or status maps to a custom field (Practice_Client_Status__c). Matters linked to the client require a secondary mapping decision (see Matter row below).

Contact records map directly to Dynamics 365 Contact. Each contact links to its primary Account via the AccountId lookup. Practice Master Pro supports multiple contacts per client; the primary contact (flagged by most-recent-activity rule or explicit designation) becomes the primary Contact record, with others surfaced as related Contact records.

Practice Master Pro has no standalone matter object — matters are a property of the Client record. Dynamics 365 Sales has no native matter concept either. We create a custom Matter__c table on Dataverse keyed by the Practice Master Pro matter ID, with fields for matter name, status, practice area, client (Account lookup), and billing rate. Alternatively, matters map to Opportunities if the practice uses a sales-cycle model.

Practice Master Pro's Fee module stores billable hours, hourly rate, and service description. Dynamics 365 Sales has no native time-tracking or billing entry. We create a custom TimeEntry__c table with fields for date, hours, rate, billable flag, matter lookup (Matter__c), and staff member (User lookup). For practices already using Project Service Automation, msdyn_timeentry is the equivalent destination.

Practice Master Pro's Cost module stores expense entries with date, amount, category, and matter link. Dynamics 365 Sales has no native expense tracking. We create a custom Expense__c table with date, amount, category, reimbursable flag, and matter lookup. For organizations using Project Service Automation, msdyn_expense is the built-in equivalent.

Practice Master Pro calendar events map to Dynamics 365 Appointment entities (for scheduled events with duration) or Task entities (for to-dos). The event subject maps to Subject, start/end times map to ScheduledStart / ScheduledEnd, and the client and matter links map to regardingObjectId lookups pointing to the migrated Account and Matter__c records. Original timestamps and owner assignments are preserved.

Practice Master Pro journal entries map to Dynamics 365 Annotation records (the Note object). Subject maps to Notetext, created date maps to CreatedOn, and the parent record link maps to ObjectId pointing to the migrated Account or Contact. Rich-text formatting is preserved as HTML within the Annotation body.

Practice Master Pro attachments stored on matters and clients are downloaded and re-uploaded to SharePoint document libraries linked from the corresponding Account or Matter__c record. Dynamics 365 Sales stores files in SharePoint Online or Dataverse File Field type — the migration creates the folder structure mirroring the Practice Master Pro matter hierarchy.

Practice Master Pro staff records are matched to Dynamics 365 Sales SystemUser records by email address. Unmatched staff members are flagged before migration — teams either provision Dynamics 365 users first or assign records to a fallback owner. Time-entry records are re-linked to the matched SystemUser after migration completes.

Practice Master Pro custom fields on client, contact, and matter records map to custom fields on the corresponding Dynamics 365 table. Field data types are matched (text to text, date to datetime, picklist to picklist) and any value-mapping lists are applied value-by-value before import.

Practice Master Pro stores billing rates per client or per matter. These migrate as a custom BillingRate__c table linked to Account and Matter__c, or as product price-list items in Dynamics 365 if the practice uses the Opportunity-product pricing model. Rate structures with multiple tiers or time-of-day multipliers are mapped as custom fields on the rate table.