Migrate from Outlaw Practice to Microsoft Dynamics 365 Sales

Dynamics 365 Sales Professional caps custom tables at 15 — most firms exceed this after creating Matter, TimeEntry, TrustAccount, TrustTransaction, CourtDate, and TimeEntry detail fields

D365 Sales Professional enforces a 15-table limit on Dataverse custom tables. Firms that create Matter__c, TimeEntry__c, TrustAccount__c, TrustTransaction__c, CourtDate__c, and supporting detail tables quickly exhaust this cap. If the firm licenses Professional, they cannot save the Matter or TrustAccount tables and the migration fails at the schema-creation step. We check the license tier before migration begins and flag the upgrade requirement to Enterprise or Premium if the custom table count exceeds 15. The D365 license upgrade is outside FlitStack's scope but is a mandatory prerequisite.

Outlaw Practice trust-account ledger has no native D365 equivalent — IOLTA balance logic must be rebuilt as custom fields and a post-migration reconciliation procedure

Outlaw Practice's trust-accounting module stores running IOLTA balances, per-client trust ledgers, and transaction types (deposit, withdrawal, fee transfer) that reflect bar-association compliance requirements. Dynamics 365 Sales has no trust-accounting entity — there is no built-in IOLTA ledger, no running-balance calculation, and no trust-versus-operating account split. We migrate trust-account balances as custom currency fields on a TrustAccount__c table and trust transactions as line items on a TrustTransaction__c table, but D365 cannot compute a running balance or enforce a trust-account minimum. The firm must establish a manual reconciliation procedure or implement a dedicated legal billing add-on (such as a third-party IOLTA app from AppSource) to restore automated trust-account logic post-migration.

Outlaw Practice workflow automations have no D365 equivalent and do not transfer — rebuilt automations in Power Automate require a separate configuration phase

Outlaw Practice includes workflow automation for client intake pipelines, court-date reminder emails, and document-generation triggers. Dynamics 365 Sales has no native legal workflow engine; automation requires Power Automate, which is a separate product with its own designer, connector library, and licensing model (included with Microsoft 365 Business Standard and above, but not automatic). We export Outlaw Practice workflow definitions as structured JSON and a step-by-step walkthrough for rebuilding each automation in Power Automate. This export covers trigger conditions, action sequences, and conditional branches. The firm should budget a configuration sprint (typically 1–2 weeks of Power Automate setup) after the data migration completes before expecting equivalent automation coverage.

D365 has no native legal billing engine — Outlaw Practice invoices and billing records migrate as read-only reference data, not functional invoices

Outlaw Practice includes a complete billing and invoicing engine: time-entry-to-invoice conversion, billable item tracking, client statements, and trust-fund payment application. Dynamics 365 Sales Professional includes product catalogs and quote management but no legal billing, no time-entry-to-invoice logic, and no client statement generation. We migrate Outlaw Practice invoice history as a custom InvoiceReference__c table (invoice number, date, amount, status, matter link) for historical reference, but the firm must configure Dynamics 365 Business Central or a third-party legal billing add-on to generate new invoices. This is a significant functional gap that affects daily operations post-migration and should be addressed in the overall migration roadmap before go-live.

Matter number uniqueness and audit requirements in some states require a custom D365 auto-number field with a bar-compliant format

Several state bar associations require that matter or case numbers on client communications and invoices follow a specific alphanumeric format (e.g., YYYY-NNNNN). Outlaw Practice generates these automatically based on firm configuration. D365 custom text fields do not enforce uniqueness unless combined with a validation plugin or Power Automate flow. We recommend creating a custom auto-number field on the Matter__c table using the D365 auto-number format string (e.g., MAT-{SEQNUM:6}) and adding a pre-create Power Automate flow to validate uniqueness before record creation. This is a compliance consideration, not a data-migration blocker, but it should be configured before go-live if the firm is subject to bar audit requirements.