Migrate from MerusCase to Microsoft Dynamics 365 Sales

MerusCase parties (attorneys, plaintiffs, defendants, witnesses) map to Dynamics 365 Contacts linked to an Account. Multi-role parties where one person serves multiple roles (e.g., attorney who is also a witness) collapse to a single Contact record with custom Role__c and Role_Type__c fields capturing the MerusCase role(s). Primary firm party maps to Account record as the organization.

MerusCase cases map 1:1 to Dynamics 365 Opportunities. Case status (Open, Closed-Won, Closed-Lost) maps to Opportunity StateCode. Case type (Personal Injury, Workers' Comp, Criminal, Employment) becomes a custom Opportunity field Case_Type__c pick-list. The MerusCase case ID is stored as Source_Case_ID__c on the Opportunity for traceability.

MerusCase assigns roles to parties on cases (Plaintiff, Defendant, Attorney, Witness, Mediator). These merge into Dynamics 365 OpportunityContactRole records with the role name from MerusCase preserved. Multiple roles on the same case-party link create multiple Contact Role entries. If a contact has no role assigned, a default 'Involved Party' role is applied.

MerusCase activities (calls, emails, meetings, tasks, notes) map to Dynamics 365 ActivityPointer records. The activity_type_id discriminates the type: telephone calls map to Task with Type='Phone Call', emails map to Email, meetings map to Appointment. Original activity date, time, and description are preserved. Activities without a case link in MerusCase become standalone activities in Dynamics 365.

MerusCase ledger entries with billable time (task_code=L-Code) have no direct Dynamics 365 equivalent. FlitStack creates Hours_Worked__c, Billing_Rate__c, and UTBMS_LCode__c custom fields on the Opportunity to preserve time-entry data. For firms using Dynamics 365 Quotes, line items can be created representing billable hours with the L-Code stored as a product attribute.

MerusCase expense ledger entries (expense_code=E-Code) migrate to Opportunity custom fields: Expense_Amount__c, Expense_Category__c, and UTBMS_ECode__c. Original expense dates and descriptions are preserved. If the firm uses Dynamics 365's expense tracking, expenses may alternatively map to separate Expense records linked by the Source_Case_ID__c.

MerusCase custom fields (Date, Currency, Text up to 250 chars, Numeric, Yes/No) map to Dynamics 365 custom columns on the corresponding table. Text fields map to nvarchar columns; Currency maps to money columns; Numeric maps to decimal or integer; Yes/No maps to bit. Field display labels are preserved from MerusCase. Note that Dynamics 365 Sales Professional limits custom columns to 15; Enterprise removes this limit.

MerusCase Document Archives are zipped file packages containing case documents plus a CSV of case activities. FlitStack downloads the archive, extracts documents, and re-uploads them to the SharePoint document library associated with the Opportunity record. The activity CSV is imported as a separate data file for reference. File size limits from SharePoint (50MB per file) apply.

MerusCase Settlement records have settlement amount, date, and payment terms with no Dynamics 365 native equivalent. FlitStack creates Settlement_Amount__c (currency), Settlement_Date__c (date), and Settlement_Terms__c (text) custom fields on the Opportunity. If the firm tracks post-settlement payments, separate custom records or Opportunity Line Items may be needed.

MerusCase users and assigned attorneys map to Dynamics 365 SystemUser records. Resolution is by email match — if a MerusCase user email matches a Dynamics 365 user email, the record OwnerId is assigned to that user. Unmatched owners are flagged before migration; firms either invite them to Dynamics 365 or reassign records to a fallback user.

MerusCase Workflows automate task creation and calendar reminders based on activity tags or descriptions. Dynamics 365 has no workflow migration path. FlitStack exports the workflow definitions as a JSON specification document so the firm's Power Automate admin can rebuild equivalent flows post-migration. Automated statute reminders, deadline tracking, and task generation must be recreated.

MerusCase Statutes auto-generate tasks based on case filing dates and jurisdictional rules. This automation logic has no direct Dynamics 365 equivalent. FlitStack exports statute configuration data as a reference file. Firms using Dynamics 365 Sales Enterprise can rebuild statute tracking in Power Automate using the case filing date and jurisdiction custom fields migrated from MerusCase.