CRM migration
Field-level mapping, validation, and rollback between Insight Legal Case Management and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Insight Legal Case Management
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
12 of 12
objects map 1:1 between Insight Legal Case Management and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Insight Legal Case Management stores law-firm data as matters with embedded parties, key dates, correspondence chains, document histories, and financial ledgers — a structure built for legal practice management rather than generic CRM. Dynamics 365 Sales organizes data around Account, Contact, Lead, Opportunity, and Case entities on Dataverse, with a different relationship model and no native trust-accounting or matter-stage concept. We map Insight Legal clients to Contact records, third parties to either Contact or Account depending on their role, and matters to a combination of Case entity plus custom fields for legal-specific properties like matter type, key dates, and time recorded totals. Document attachments migrate to SharePoint or Dynamics 365 native storage depending on your configuration. Workflows, matter templates, and legal-process automation do not transfer — we export them as reference documentation for rebuilding in Power Automate and Dynamics 365 Business Rules. The migration runs via Dataverse Web API and Bulk API, sequenced so foreign-key dependencies resolve correctly: accounts first, then contacts, then cases, then activities and documents. A delta-pickup window captures any matter updates made during cutover.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Insight Legal Case Management platform overview
Scorecard, SWOT, gotchas, and pricing for Insight Legal Case Management.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Insight Legal Case Management object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Insight Legal Case Management
Client (Primary Contact on Matter)
Microsoft Dynamics 365 Sales
Contact
1:1Insight Legal's primary client on a matter maps directly to a Dynamics 365 Contact record. The client's email, phone, address, and firm name (if corporate) transfer as Contact fields. Owner resolution by email match against Dynamics 365 users ensures the contact's assigned lawyer appears as the record owner.
Insight Legal Case Management
Client (Corporate Entity)
Microsoft Dynamics 365 Sales
Account
1:1Corporate clients in Insight Legal — companies or LLPs listed as matter parties — map to Account records in Dynamics 365. Account.Name captures the company name; industry classification, employee count, and website transfer as standard Account fields if populated in Insight Legal.
Insight Legal Case Management
Matter
Microsoft Dynamics 365 Sales
Case
1:1Insight Legal matters are the primary record but they contain nested structures (parties, key dates, time entries) that don't exist as native Case sub-entities in Dynamics 365. We map the matter header to Case.title and Case.casetypecode, then use custom fields (Matter_Type__c, Matter_Number__c, Responsible_Fee_Earner__c) for legal-specific properties that Dataverse doesn't store natively.
Insight Legal Case Management
Third-Party Party (Individual)
Microsoft Dynamics 365 Sales
Contact
1:1Individual counterparties, witnesses, or other individuals on a matter map to Contact records. Their relationship to the matter is preserved via a custom matter-contact junction table (Matter_Party__c) with a Role__c field holding Insight Legal's party-type value (e.g., Defendant, Witness, Opposing Counsel).
Insight Legal Case Management
Third-Party Party (Corporate)
Microsoft Dynamics 365 Sales
Account
1:1Corporate third parties map to Account records with the same junction-table approach as individual parties. The Matter_Party__c junction holds the corporate entity's role on the matter, with the Account lookup ensuring the corporate party's details are accessible directly within the matter context. We preserve the original party-type designation from Insight Legal in the Role__c field.
Insight Legal Case Management
Key Dates
Microsoft Dynamics 365 Sales
Custom Fields on Case + Activities
1:1Insight Legal key dates (court deadlines, filing dates, limitation dates) have no direct equivalent in Dynamics 365. We map each key date as a custom datetime field (Key_Date_1__c, Key_Date_2__c, etc.) on the Case entity, and also create a corresponding CalendarEvent or Task activity so the firm's fee earners receive reminders via the Dynamics 365 activity timeline.
Insight Legal Case Management
Time Recording Entry
Microsoft Dynamics 365 Sales
Custom Time Entry Table
1:1Insight Legal time entries (fee, description, date, fee earner) cannot map to native Dynamics 365 Sales entities because the platform lacks a native time-tracking object. We create a Time_Entry__c custom table in Dataverse with fields for Fee_Earner__c, Date__c, Hours__c, Rate__c, Description__c, and a lookup to the Case. Reporting on time entries links back to the parent matter.
Insight Legal Case Management
Document / Attachment
Microsoft Dynamics 365 Sales
SharePoint / Dynamics 365 Attachments
1:1Matter documents and correspondence attachments from Insight Legal are downloaded and re-uploaded to SharePoint Online or Dynamics 365 native file storage, depending on your licensing. We preserve the original folder structure (by matter number) so documents remain findable. Inline images in correspondence are extracted and rehosted as separate files.
Insight Legal Case Management
Trust Account Entry
Microsoft Dynamics 365 Sales
Custom Trust Accounting Table
1:1Insight Legal trust ledger entries (client funds received, disbursements, balance) have no Dynamics 365 equivalent. We create a Trust_Entry__c custom table with fields for Transaction_Type__c, Amount__c, Date__c, Description__c, and a lookup to the Client Account (Contact or Account). For firms also running Business Central, trust entries can be exposed via Dataverse integration for ledger reconciliation.
Insight Legal Case Management
Correspondence Log
Microsoft Dynamics 365 Sales
Email (Activity) + Note
1:1Insight Legal correspondence entries (letters, emails, faxes logged against a matter) map to Dynamics 365 Email (activity) records. The correspondence direction (incoming/outgoing) maps to DirectionCode; the subject line preserves the letter or email subject. Timestamps and the sending/receiving party are preserved in the activity's From/To fields.
Insight Legal Case Management
Matter Status / Stage
Microsoft Dynamics 365 Sales
Case.StatusCode + Custom Stage Field
1:1Insight Legal matter stages (Active, On Hold, Closed, Archived) map to Case.StatusCode pick-list values. If your firm uses sub-stages (e.g., Drafting, Awaiting Court Date), we add a Matter_Stage__c custom pick-list field with your exact stage names preserved as values, maintaining continuity with your established workflow terminology and process classifications.
Insight Legal Case Management
Matter Template / Workflow
Microsoft Dynamics 365 Sales
Not Migrated
1:1Insight Legal matter templates and process workflows are practice-automation constructs that embed in the platform's logic. Dynamics 365 Sales has no equivalent — matter workflows must be rebuilt using Power Automate or Dynamics 365 Business Rules. We export your workflow definitions as a documented reference for your Dynamics admin to rebuild.
| Insight Legal Case Management | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Client (Primary Contact on Matter) | Contact1:1 | Fully supported | |
| Client (Corporate Entity) | Account1:1 | Fully supported | |
| Matter | Case1:1 | Fully supported | |
| Third-Party Party (Individual) | Contact1:1 | Fully supported | |
| Third-Party Party (Corporate) | Account1:1 | Fully supported | |
| Key Dates | Custom Fields on Case + Activities1:1 | Fully supported | |
| Time Recording Entry | Custom Time Entry Table1:1 | Fully supported | |
| Document / Attachment | SharePoint / Dynamics 365 Attachments1:1 | Fully supported | |
| Trust Account Entry | Custom Trust Accounting Table1:1 | Fully supported | |
| Correspondence Log | Email (Activity) + Note1:1 | Fully supported | |
| Matter Status / Stage | Case.StatusCode + Custom Stage Field1:1 | Fully supported | |
| Matter Template / Workflow | Not Migrated1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Insight Legal Case Management gotchas
No public API forces all migrations through vendor services
Hybrid hosting creates two distinct extraction paths
Thousands of fields per matter require explicit scoping
Trust account compliance data has regulatory retention requirements
Out-of-the-box workflows may not transfer to non-Insight systems
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Assess Insight Legal data export and Dynamics 365 schema requirements
We begin by reviewing your Insight Legal data export — typically via the platform's built-in export tools or API — to inventory matter types, party roles, key date categories, document counts, and trust entry volumes. Simultaneously, we document your target Dynamics 365 environment (Professional or Enterprise), existing entities, and security roles. This produces a migration plan specifying custom field creation, custom table design for trust accounting and time entries, SharePoint folder structure, and the mapping matrix for all objects.
Create custom fields and tables in Dataverse
Before data moves, we create the custom Dataverse columns and tables required for legal-specific data: Matter_Type__c pick-list on Case, Key_Date__c datetime fields, Matter_Number__c for reference, Time_Entry__c table, Trust_Entry__c table, and Matter_Party__c junction table. We also configure SharePoint document-library structure by matter number. Dynamics 365 admins review and approve the schema before we proceed to data migration, ensuring the target environment matches your firm's requirements.
Resolve fee-earner owners by email match
Insight Legal fee earners (the lawyers responsible for a matter) map to Dynamics 365 user records via email address. We run an owner-resolution pass: matched owners link directly to Case.OwnerId; unmatched owners are flagged for your team to either invite to Dynamics 365 or assign to a fallback user. No matter lands in Dynamics 365 without an assigned owner, preventing orphaned records.
Migrate in dependency order: Accounts → Contacts → Cases → Activities → Documents
We sequence the migration to resolve foreign-key dependencies correctly. Corporate parties migrate to Account first (so Contact.AccountId lookups resolve), then clients and parties to Contact, then matters to Case with owner resolution and custom field population. Correspondence and activities follow, then documents upload to SharePoint. Time entries and trust entries load last, after their parent Case records exist to satisfy the Dataverse relationship constraints.
Run sample migration with field-level diff before full commit
A representative slice — typically 50–200 records spanning all matter types, party roles, and document categories — migrates first. We generate a field-level diff between Insight Legal source values and Dynamics 365 destination values so you can verify key date mapping, matter stage mapping, party-role preservation, and trust-entry sign logic before the full run. You sign off on the diff before we proceed.
Execute full migration with delta-pickup and rollback capability
The full migration commits records to Dynamics 365. A delta-pickup window (typically 24–48 hours after full migration starts) captures any matters, time entries, or trust entries modified in Insight Legal during cutover. All operations are logged in an audit record. If reconciliation fails, one-click rollback reverts the Dynamics 365 environment to its pre-migration state. Post-migration, we deliver a summary report with record counts, skipped records, and owner-resolution exceptions for manual resolution.
Platform deep dives
Insight Legal Case Management
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Insight Legal Case Management and Microsoft Dynamics 365 Sales .
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Insight Legal Case Management: Not publicly documented.
Data volume sensitivity
Insight Legal Case Management doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Insight Legal Case Management to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Insight Legal Case Management to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Insight Legal Case Management
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.