Migrate from Legal Workspace to Microsoft Dynamics 365 Sales

Legal Workspace Clients map to Dynamics 365 Accounts. Client display name becomes Account.Name, and the primary address maps to the Account's address fields. We preserve the Client's original create date as a custom datetime field since Dynamics overwrites CreatedDate at migration time. Client records with no matters attach to a placeholder account or remain de-linked pending review.

Each contact associated with a Legal Workspace Client maps to a Dynamics 365 Contact with AccountId lookup to the corresponding Account. Primary contact roles (Attorney, Paralegal, Billing Contact) map to custom pick-list fields on Contact since Dynamics does not have a native contact-role label system. Email addresses resolve as primary email, and phone numbers map to standard Contact phone fields.

Legal Workspace Matters map to Dynamics 365 Opportunities with matter number preserved in a custom text field (Matter_Number__c). The matter name becomes Opportunity.Name, and matter status (Open, Closed, Pending) maps to a custom pick-list. Responsible attorney resolves by email match against Dynamics 365 users, with unmatched attorneys flagged for manual assignment before migration commits.

Legal Workspace matter statuses (Active, Pending, Closed Won, Closed Lost) map value-by-value to a custom Opportunity field (Matter_Status__c). Status transition timestamps require custom datetime fields since Dynamics tracks stage-changed dates only for the built-in Opportunity Stage field. We preserve the most recent status-change timestamp as Matter_Status_Updated__c.

Legal Workspace documents stored in their native file store map to SharePoint document libraries attached to the corresponding Opportunity record via the SharePoint Document Location entity in Dataverse. Document metadata (author, created date, matter association) migrates as SharePoint column values. Files exceeding Dynamics 365's attachment size limit are re-uploaded as SharePoint file attachments with the original URL preserved as a reference link.

Dynamics 365 Sales has no native hours-tracking entity. We create a custom Dataverse table (Billable_Hours__c) with fields for Hours__c, Rate__c, Attorney__c (lookup to Contact), Matter__c (lookup to Opportunity), and Date__c. The migration populates this table from Legal Workspace time-entry records, preserving billable vs. non-billable flags and the responsible attorney's email-linked user.

Trust-account balances and transaction history have no native Dynamics 365 equivalent. We create a custom Dataverse table (Trust_Account__c) with fields for Account__c (lookup), Transaction_Type__c (Deposit/Withdrawal/Disbursement), Amount__c, and Transaction_Date__c. This table is informational in Dynamics and requires Business Central for true accounting; FlitStack surfaces the reconciliation gap in the migration plan.

Legal Workspace activities linked to matters map to Dynamics 365 email, task, and note records with Regarding pointing to the corresponding Opportunity. Original timestamps, activity owners, and body content transfer directly. Email attachments are re-hosted in SharePoint and linked via URL reference since Dynamics attachments do not support inline embedding of large files.

Legal Workspace custom fields on Clients, Matters, and Contacts require custom Dataverse columns created with the new_ prefix. Field data types map to Dataverse column types: text fields become nvarchar, date fields become datetime, and pick-lists become option sets. We flag any unsupported field types for manual review before migration.

Legal Workspace staff members resolve by email match against Dynamics 365 SystemUser records. Unmatched users are flagged with their Legal Workspace ID preserved in a custom field (Source_User_ID__c). Migration of time-entry and activity records requires that owner lookups resolve to existing Dynamics users; inactive Legal Workspace users can be mapped to a fallback system user designated by the firm.

Legal Workspace workflow rules (matter-status triggers, document-routing rules, notification rules) have no native Dynamics 365 equivalent. FlitStack exports the rule definitions as JSON and human-readable documentation for your Power Automate admin to rebuild. Workflow logic does not auto-translate between platforms.