Migrate from Lawmatics to Microsoft Dynamics 365 Sales

Lawmatics contact fields map directly to Dynamics 365 Contact columns. Dynamics 365 requires each Contact to link to an Account via AccountId — contacts without a primary Lawmatics Company get attached to a default 'Unassigned' Account record. Email is the primary lookup key for de-duplication.

Lawmatics contacts with no associated Matter records are unconverted prospects. These map to Dynamics 365 Lead records. Lead Source, original create date, and owner are preserved. When a Lead is later qualified in Dynamics, it converts to a Contact and Account — this lifecycle is new territory for Lawmatics-sourced records.

Lawmatics Company name, domain, industry, phone, and address fields map to Dynamics 365 Account Name, Website, Industry, Telephone1, and Address composite fields. Parent-child company hierarchies in Lawmatics map to Account.ParentId. Lawmatics allows N:1 contact-to-company; Dynamics 365 enforces primary AccountId plus Account Contact Relationships.

Lawmatics Matter is the central record for legal intake — it carries the client (Contact), opposing party, practice area, referral source, intake status, and estimated value. Dynamics 365 Opportunity is the analogous pipeline record. The mapping carries Matter name as Opportunity Name, estimated_value as EstimatedValue, close_date as CloseDate, and status as a custom Opportunity Status field. The law firm's Matter stage (Intake, Consultation, Retained, etc.) maps to a value-mapped custom Opportunity Stage field since Dynamics stages are win/loss-keyed by design.

Lawmatics practice areas (Personal Injury, Family Law, Estate Planning, etc.) have no native equivalent in Dynamics 365 Sales. We create a custom pick-list field Practice_Area__c on both Contact and Opportunity. For firms with fewer practice areas that align with Dynamics 365 Business Segment, that field can be used instead, but law-firm-specific practice areas always require a custom field.

Lawmatics automations — triggers like form submission or date-field conditions, actions like email send or task creation — have no equivalent in Dynamics 365 Sales. We export automation definitions as a JSON reference document. Your Dynamics 365 admin or a FlitStack consultant uses this to build equivalent Power Automate flows. Automations covering intake pipelines are the highest priority to rebuild since they drive firm revenue operations.

Lawmatics email history stored as timeline activities maps to Dynamics 365 Email activity records. Subject, body (HTML), timestamp, direction (sent/received), and owner are preserved. Email activities link to the Contact or Opportunity record they were logged against in Lawmatics. The Email entity uses the ActivityPointer table with Email Direction values set as 'Incoming' or 'Outgoing'. All HTML formatting is retained.

Lawmatics call logs (subject, duration, outcome, owner) map to Dynamics 365 PhoneCall activity records. The PhoneCall activity links to the Contact or Opportunity via the regarding_objectid field. Call disposition notes become the PhoneCall.Description field. Inbound/outbound direction is preserved. The PhoneCall entity stores call duration in minutes and uses the PhoneCall.StatusCode field to track completion status. All call metadata including the originating phone number maps to the PhoneNumber field.

Lawmatics Events with title, start/end datetime, location, attendees, and status map to Dynamics 365 Appointment records. The RequiredAttendees and OptionalAttendees fields are populated from Lawmatics attendee records where available. Event type (consultation, deposition, court appearance) is preserved as a custom field.

Lawmatics notes with embedded text and attachments split during migration: text body goes to a Dynamics 365 Note (Annotation) record linked to the Contact or Opportunity. Attachments are downloaded and re-uploaded to the SharePoint document location associated with the Account. SharePoint Document Location URL is stored as a custom field on the parent record for traceability.

Lawmatics files attached to Matters or Contacts — PDFs, images, intake documents — are downloaded and uploaded to SharePoint-integrated document management under the corresponding Account's document library in Dynamics 365. The file's original upload date, uploader, and Matter association are stored as metadata fields.

Lawmatics SMS messages (sent and received) have no native equivalent in Dynamics 365 Sales. Inbound/outbound SMS content, timestamp, and direction are stored in a custom SMS_History__c text area on Contact and as a Task with Type='SMS' for each individual message. SMS opt-out status maps to a custom DoNotSMS__c boolean field.

Lawmatics time entries linked to Matters (billable hours, activity descriptions) are aggregated by Matter and stored as custom numeric and text fields on the corresponding Dynamics 365 Opportunity. Total billable hours, total non-billable hours, and last entry date are carried over. Detailed time-entry line items are exported as a CSV attached to the Opportunity's SharePoint document location.

Lawmatics tags used for firm-specific labeling (referral source tags, matter-category tags, attorney-assignment tags) have no direct equivalent in Dynamics 365. Tags are preserved as a comma-separated custom text field (Tags__c) on Contact and Opportunity for filtering and reporting. A separate Tag_Mapping_Reference CSV is delivered for rebuilding tags as Dynamics 365 multi-select option sets if the firm has fewer than 20 unique tags.