Migrate from Jarvis Legal to Microsoft Dynamics 365 Sales

Jarvis contacts (lawyers, opposing counsel, clients) map directly to Dynamics 365 Sales Contacts. We preserve original create dates as a custom datetime field since Dynamics CreatedOn is set at migration time. Contact UUID stored as Source_System_ID__c for delta-run de-duplication. If duplicate contacts exist across matters, we apply a naming convention suffix to distinguish records while preserving all original identifiers.

Jarvis matters represent client matters or cases — the closest CRM equivalent is Dynamics Account (representing the client entity). Matter name becomes Account Name; matter status maps to a custom pick-list field (Matter_Status__c). Each matter links to its primary contact via AccountId.

For firms needing full matter-centric tracking in Dynamics, we create a custom Matter__c table (Dataverse) that preserves matter number, practice area, responsible attorney, status, open date, and close date as separate fields — this table links to Account and Contact for full relationship context.

Jarvis documents and the Document Merger outputs (contracts, briefs, letters) re-upload to SharePoint integrated with Dynamics 365 Sales. Each document gets a SharePoint URL stored on the related Account or Matter__c record. Original document names and creation timestamps preserved. Folder hierarchies are recreated to match the matter structure from Jarvis, with version history maintained where the API supports retrieval.

Jarvis billable-time entries map to a custom field (Total_Billable_Hours__c) on Matter__c for summary reporting. Detailed entries migrate as Task or custom Activity records with Subject, Description, ActualDurationMinutes, and Owner — preserving date, billable/non-billable flag, and attorney attribution. Non-billable entries retain their classification through the new_IsBillable__c flag, enabling accurate utilization reporting post-migration.

Jarvis invoices link to matters with line items, amounts, and payment status. We map invoice number to Invoice Number, total amount to Total Amount, and invoice date to Date. Invoice line items become Invoice Products linked by ProductId or as description-only entries.

Jarvis custom fields (practice_area, referring_attorney, conflict_check_status) use UUID identifiers. We read the field UUID from the Jarvis field URL, retrieve field values, and create a corresponding new_* field in Dynamics 365 Sales Dataverse with matching data type — pick-lists, text, numeric, and date fields all handled.

Jarvis task management (deadlines, court dates, filing reminders) maps to Dynamics Tasks and Appointments. Subject, due date, priority, and status transfer directly. Tasks linked to a matter inherit the Matter__c lookup — attorney assignments resolve by email match to Dynamics users.

Jarvis email synchronization logs emails to matters. Emails migrate as Dynamics Email activities with Subject, Description (body), From, To, and Regarding (linked to Account or Matter__c). Timestamps and sender/recipient information preserved. Attachments referenced in email bodies are downloaded and reattached to the corresponding SharePoint document location, ensuring that email context remains complete within Dynamics 365 Sales.

Jarvis organizes documents in folders per matter. We replicate this hierarchy in SharePoint with a Document Library per Account or per Matter__c. The folder structure maps to SharePoint URL paths — documents re-upload with original filenames, creation dates, and attorney-attributed versions.