Migrate from Lawcus to Microsoft Dynamics 365 Sales

Lawcus contacts migrate directly to Dynamics 365 Contacts. Lawcus stores the primary Client record as a lookup on the contact; we resolve that to Contact.AccountId. Lawcus source ID preserved as a custom field for delta-run de-duplication. All standard address fields (street, city, state, postal code, country) map to the corresponding Dynamics 365 address attributes, and any secondary phone numbers are stored in the Telephone2 and Telephone3 fields.

Lawcus clients (companies) map 1:1 to Dynamics 365 Accounts. Account.Name pulls from Lawcus client name. Domain, industry, employee count, and annual revenue map to matching Account fields. Parent-client hierarchies resolve to Account.ParentAccountId. Industry values are translated using a value‑mapping table, and any existing parent‑client relationships become Account.ParentAccountId references, preserving the organizational hierarchy in Dynamics 365.

Lawcus leads map directly to Dynamics 365 Leads. Lead status, source, rating, and estimated revenue all translate to standard Lead entity fields. Unqualified leads from Lawcus land as Dynamics 365 Leads for follow-up routing. Lead rating (Hot, Warm, Cold) maps to the standard Rating field, and any custom lead scores are stored in a custom integer field for reporting and segmentation.

Lawcus matters are legal work records; Dynamics 365 has no native matter entity. We map Matter to Opportunity: Matter.Name becomes Opportunity.Name, amount maps to estimated revenue, and close date maps to CloseDate. Practice area, billing classification, responsible attorney, and originating staff member migrate as custom fields on the Opportunity.

Lawcus practice areas (Family Law, Civil Litigation, Corporate, etc.) classify matters. Dynamics 365 Sales has no native practice-area field. We create a custom pick-list field Practice_Area__c on the Opportunity table and map each value by-value. If a practice area value in Lawcus does not have a matching option in the custom pick‑list, the unmapped value is logged for manual review and can be added to the pick‑list before the final migration run.

Lawcus matter statuses (Open, Closed, On Hold) map to Dynamics 365 Opportunity StateCode / StatusCode. Sub-status values map to StatusCode pick-list values. The mapping table is confirmed before migration runs. The mapping table includes both the primary state (Open/Closed) and the sub‑status reason codes; any mismatched statuses are flagged in the pre‑migration validation report for resolution.

Lawcus activity types map to their Dynamics 365 equivalents: phone calls to Task with Type='Phone Call', emails to Email activity, meetings to Appointment, and text notes to Note. Original timestamps and owner assignments are preserved across all activity types. Activity attachments and notes are preserved as Dynamics 365 note annotations, maintaining the original context for future follow‑ups.

Lawcus files stored within the platform require SharePoint document library setup in Dynamics 365 before migration. We create SharePoint Document Locations linked to each Account and Opportunity, then upload files as SharePoint attachments, preserving file names and original upload dates.

Any Lawcus custom fields defined on the Matter record (billing tier, referral source, insurance carrier, etc.) migrate as custom fields on the Dynamics 365 Opportunity entity. We create each custom field in the target environment before the migration run and map values field-by-field.

Lawcus workflow definitions, stage triggers, and automation rules have no equivalent in Dynamics 365 Sales. FlitStack exports workflow definitions as a reference document so your Dynamics 365 admin can rebuild them in Power Automate after migration. The export includes trigger conditions, action sequences, and stage-transition logic.

Lawcus intake forms and client portal access do not migrate. These are portal-layer constructs with no Dynamics 365 Sales native equivalent. FlitStack documents the form field structure and logic; Power Pages or Dynamics 365 Customer Forms rebuild is handled separately after go-live.

Lawcus team members map to Dynamics 365 SystemUser records. Matching runs by email address — if a Lawcus owner email resolves to a Dynamics 365 user, records assign to that user. Unmatched owners are flagged before migration so your admin can invite users or assign a fallback owner.