Migrate from Law Ruler to Microsoft Dynamics 365 Sales

Law Ruler contacts migrate to Dynamics 365 Sales Contact records. The contact's full name splits into firstname and lastname fields in Dynamics. Email address, phone, and address fields map directly. Each Contact requires a parent Account (the client law firm or company) to exist in Dynamics before the Contact record can be linked via the parentcustomerid field.

Law Ruler companies map to Dynamics 365 Sales Account records. The company name becomes Account.Name. Website, industry, number of employees, and annual revenue fields migrate directly. Parent-child company hierarchies in Law Ruler map to the Parent Account ID relationship in Dynamics. Multi-company associations on a single contact collapse to the primary Account lookup.

Law Ruler matters are the core legal record and map to Dynamics 365 Sales Opportunity entities. The matter name becomes Opportunity.Name, estimated value or billing amount maps to EstimatedValue, and matter status maps to Opportunity Stage. Matter-type custom fields (practice area, matter number, referring attorney) become new_ custom columns on the Opportunity record. Each Opportunity must be linked to a primary Account representing the client.

Law Ruler matter lifecycle stages (New Matter, In Progress, Pending, Closed, Archived) require explicit value-by-value mapping to Dynamics Opportunity Stage picklist values. Probability weights and forecast category assignments re-apply based on Dynamics stage configuration. Stage-transition timestamps from Law Ruler are preserved as custom datetime fields on the Opportunity record.

Law Ruler milestones attached to a matter migrate as Dynamics 365 Sales Task records linked to the corresponding Opportunity. Task subject, due date, assigned user, and status map directly. Completed-flag and completion-date fields populate the CompletedDateTime and StateCode on the Dynamics Task entity. Each Task links via the Regarding field to its parent Opportunity.

Law Ruler intake form field values (referral source, practice area, initial consultation date, lead source) become new_ custom columns on the Dynamics Opportunity entity. Practice-area picklist values require value-by-value mapping to Dynamics custom picklist options. We generate a Dataverse Column Definition export so your admin can pre-create these fields in the Dynamics solution before migration.

Law Ruler documents and attachments associated with matters are extracted, re-uploaded to the Dynamics-connected SharePoint location or stored as Note (Annotation) records in Dataverse. File metadata (original filename, created date, author) is preserved in the Annotation documentbody and notetext fields. SharePoint integration must be enabled in the Dynamics solution before document migration runs.

Law Ruler client portal login events and document-view timestamps have no direct Dynamics 365 Sales equivalent. We preserve portal activity as custom datetime fields (new_lastportallogin__, new_documentviewcount__) on the Contact record for reference and reporting continuity. Portal functionality must be rebuilt using Power Apps Portals or an equivalent third-party solution.

Law Ruler invoices and billing records are legal-specific financial records with no direct Dynamics 365 Sales equivalent — Dynamics Sales does not include trust accounting. We export invoice records as a structured CSV and recommend Dynamics 365 Business Central for full billing and trust-accounting capability. If only basic opportunity revenue tracking is needed, invoice amounts map to Opportunity EstimatedValue.

Law Ruler staff and attorney owners resolve by email match against Dynamics 365 Security Principals. Unmatched owners are flagged before migration so the firm can invite them to Dynamics or assign records to a fallback owner. OwnerId on migrated records (Contact, Account, Opportunity, Task) populates from the resolved SystemUser record.

Law Ruler two-way SMS records have no native Dynamics 365 Sales equivalent. We migrate SMS as custom activity records (new_smsmessage) linked to the Contact. For compliance retention, the notetext and direction fields capture sender, recipient, and message body. SMS capability in Dynamics requires third-party integration such as Azure Communication Services or a compatible add-in.

Any Law Ruler custom objects (e.g., Practice Group, Referral Partner) map to custom Dataverse tables with the new_ schema prefix. N:N relationships in Law Ruler translate to Dataverse many-to-many relationships using the Intersect entity pattern. We surface the relationship graph in the migration plan before schema creation begins.