Migrate from PCLaw(r) to Microsoft Dynamics 365 Sales

Trust account balances have no native Dynamics 365 CRM equivalent

PCLaw's IOLTA trust accounting tracks deposits, withdrawals, and running balances per client-matter with regulatory compliance built in. Dynamics 365 Sales is a CRM, not an accounting system. The platform has no native trust account concept. We handle this by preserving trust balance, account number, and bank name as custom currency and text fields on the Account record. Full transaction history migrates as Notes entries or a custom Billing_History__c entity. Your firm will need to maintain trust accounting separately in Dynamics 365 Finance, Business Central, or a dedicated legal accounting tool post-migration. This is a structural limitation of the destination platform, not a data loss issue—FlitStack surfaces all financial balances in a reference format.

PCLaw custom report fields require manual schema creation in Dynamics 365

PCLaw allows firms to define custom fields per-database using the Reports module, and these custom fields are distinct from standard matter properties. Dynamics 365 Professional tier limits custom tables to 15; Enterprise tier allows unlimited custom fields. We export all PCLaw custom field definitions, translate their data types to Dynamics 365 equivalents, and pre-build the schema plan for your Dynamics 365 solution. However, the fields must be physically created in your Dynamics 365 environment before the migration runs—FlitStack delivers the field definition spec, and your admin (or our team) creates them in the solution before data lands.

Contact-to-matter relationship is many-to-many in PCLaw but Account-to-Contact is one-to-many in Dynamics 365

PCLaw allows a single contact (e.g., a paralegal) to be associated with multiple matters simultaneously. Dynamics 365 Contact records have a primary AccountId lookup, with Account Contact Relationships handling secondary affiliations. We handle this by designating the most-active matter as the primary Account for each contact and surfacing the remaining matter associations as Account Contact Relationship records. This preserves the full relationship history but requires your team to review whether the N-to-N model needs a custom junction entity for compliance or billing attribution purposes.

PCLaw does not expose a modern REST API; export depends on native file output

PCLaw does not provide a documented public API for programmatic data extraction. Migration depends on PCLaw's native export functionality: Matter export for client-matter data, Reports module for custom field values, and built-in report writers for billing history. These exports generate CSV or XLSX files with character encoding limitations and field-width constraints that can truncate long text fields or special characters. FlitStack runs pre-migration data profiling to identify truncation risks and applies string normalization before importing into Dynamics 365 Dataverse API.

Dynamics 365 Professional tier caps custom tables at 15—Enterprise required for extensive custom schemas

If your PCLaw database uses more than 15 custom report fields across different field groups, or if you require a custom Billing_History__c entity for detailed financial records, the Dynamics 365 Sales Professional license will hit its 15-table ceiling. Upgrading to Sales Enterprise removes this limit and adds advanced forecasting, Copilot AI, and territory management. FlitStack includes a license-tier recommendation in the migration plan based on your custom field count and data volume; this avoids the cost surprise of mid-migration license upgrades.