What is insurance defense case management?

Insurance defense case management is the specialized workflow process and software methodology used by law firms, carriers, and claims administrators to manage litigation involving insured parties. It coordinates underlying insurance policies, carrier reporting guidelines, defense counsel assignments, litigation budgets, tenders, and multi-party procedural claims throughout a legal matter.

What is the difference between insurance defense case management and general legal case management?

General legal case management platforms are built for standard law firm workflows—tracking basic deadlines, time entries, and client contacts. They typically treat every matter as a 1:1 relationship between one client and one invoice. In contrast, insurance defense case management software is built around the complex tripartite relationship between the insured, carrier, and defense counsel. It supports multi-layered policy towers, split billing ratios, strict carrier LEDES e-billing guidelines, carrier-specific status reporting, and tracking tender requests or reservation of rights positions across primary, umbrella, and excess carriers.

How does insurance defense software handle multiple carriers?

When multiple insurance carriers share defense costs across co-defendants, additional insureds, or layered policy towers, specialized software assigns custom cost-allocation percentages or split-billing rules to individual time entries and expense codes. The system manages complex carrier hierarchies by mapping each billable action to specific coverage layers or participating carriers. This allows panel counsel to generate separate, guideline-compliant LEDES file submissions, such as LEDES 1998B or eEbill XML, for each insurer while maintaining a unified, single-matter master record in Microsoft 365.

How does insurance defense software manage multiple parties?

Unlike standard case management platforms that list entities in flat contact lists, purpose-built insurance defense software relies on a relational entity structure. It links each party individually to its specific procedural status, primary and excess insurance carriers, claim numbers, defense counsel, and coverage position letters across main actions, cross-claims, and third-party complaints.

What is the difference between a cross-claim and a counterclaim?

A counterclaim is a cause of action brought by a defendant against the opposing plaintiff in the lawsuit. A cross-claim is brought by one party against a co-party on the same side of the litigation, such as one co-defendant asserting an indemnity or contribution claim against another co-defendant.

What is a third-party complaint or impleader?

A third-party complaint, or impleader action, is a procedural mechanism where an existing defendant brings a new outside entity into the lawsuit. The defendant alleges that this new third-party defendant is or may be liable to pay all or part of the damages that the plaintiff might recover against the original defendant.

How does insurance defense software track multiple insurance policies and policy limits?

The software models layered policy towers in a visual, relational view. It connects primary policies, umbrella layers, excess lines, and self-insured retentions (SIRs) to specific insureds. In defense matters where litigation costs erode policy limits, the software tracks real-time billable time, expenses, and pending reserves directly against the policy's aggregate and per-occurrence caps. Through automated reporting dashboards and budget triggers, the system alerts defense teams and carrier claims managers as defense spend approaches critical thresholds.

What is a reservation of rights in an insurance defense matter?

A Reservation of Rights (ROR) is a formal statement by an insurance carrier notifying the insured that while the carrier is providing a legal defense, it reserves the right to deny coverage for damages later if the litigation reveals that the underlying claims fall outside policy coverage terms.

When may independent or Cumis counsel be involved?

Independent counsel rules vary by jurisdiction. Cumis counsel is specifically associated with California under California Civil Code §2860, which addresses independent counsel selection when a carrier's Reservation of Rights creates an ethical conflict of interest for panel counsel. Other jurisdictions apply distinct statutory or common-law standards to determine when defense counsel's ability to shape trial outcomes creates a coverage conflict requiring independent representation funded by the carrier.

How can law firms track carrier reporting deadlines and litigation budgets?

Carrier reporting requirements vary by carrier, claim type, litigation stage, and applicable guidelines. Depending on the carrier, requirements may include initial evaluations, litigation plans, budgets, periodic status reports, pre-trial reports, and settlement authority requests. For carriers that use 30-day, 60-day, 90-day, or other recurring reporting milestones, the system can schedule and monitor those obligations. Firms utilize automated compliance engines to enforce these requirements and track integrated legal spend against approved budgets and carrier limits.

What should law firms look for when choosing insurance defense case management software?

When evaluating case management software for insurance defense practices, firms should prioritize five core capabilities: native Microsoft 365 architecture with seamless integration with Outlook, Teams, SharePoint, and Power Automate; carrier reporting and LEDES automation with UTBMS phase and task coding; policy tower and coverage tracking for primary, umbrella, and excess layers and reservation of rights issues; multi-party and indemnity management for co-defendants, cross-claims, counterclaims, and third-party tender tracking; and ethical wall and governance controls for protecting confidential carrier information across co-panel defense representations.

Moving from iManage to SharePoint: A Law Firm Migration Guide

Migrating a law firm’s document management system (DMS) from iManage to SharePoint Online is a significant operational and technical transformation. While many law firms are moving toward Microsoft 365-native document management, a successful migration involves much more than transferring files from one platform to another.

An iManage to SharePoint migration must account for the relationships that make a legal document management system functional: client and matter workspaces, document metadata, version history, folder structures, email records, document relationships, and granular access permissions.

The challenge is to preserve this legal context while transitioning to SharePoint Online as the foundation of a Microsoft 365-based legal document management environment. Without a structured migration strategy, firms risk losing important document properties, disrupting established workflows, weakening access controls, and making historical matter information difficult to locate.

Written by Knowledge Team, posted on Nov 02, 2026

iManage to SharePoint migration architecture for law firms transitioning to Microsoft 365

Why Law Firms Are Transitioning to Native Microsoft 365 Architecture

Transitioning legal document management to a Microsoft 365-native architecture reduces dependence on proprietary DMS infrastructure, makes better use of existing Microsoft 365 investments, and enables matter-centric collaboration through Microsoft Teams, Word, and Outlook.

Legacy DMS solutions create data silos, require expensive custom infrastructure, and lock firm data into proprietary environments. By shifting matter management to Microsoft 365, law firms gain:

Legal document management system migration architecture from iManage to SharePoint Online

Unified Microsoft 365 Governance

Centralize identity management and group-based access through Microsoft Entra ID, while applying Microsoft Purview capabilities for information protection, retention, compliance, and supported information barrier policies.

Reduced Infrastructure and DMS Licensing Overhead

Leverage your existing Microsoft 365 investment and reduce dependence on separate document management infrastructure, proprietary storage environments, and legacy DMS licensing.

Matter-Centric Collaboration

Enable real-time co-authoring, mobile access, and secure client sharing natively within Microsoft Teams, Word, and Outlook.

Law firm document management using Microsoft 365, SharePoint Online, and PageLightPrime

Evaluating iManage to SharePoint Migration Approaches

Law firms migrating from iManage to SharePoint must choose between specialist migration platforms for full metadata/ACL preservation, custom API scripts for legacy database structures, or native file exports for simple archive-only data.

When planning your move to SharePoint Online and Microsoft 365, evaluate these primary migration paths:

Migration Approach	When to Consider It	Key Requirements & Verification
Specialist Migration Platform or Service	You require structured, automated migration of client/matter workspaces, rich metadata schemas, security ACLs, and delta synchronization.	Require vendors to demonstrate successful metadata transformation, security remapping, internal link handling, and delta syncs directly on a pilot dataset.
Custom Extraction & Migration	Your source environment involves unique transformation scripts, legacy on-premises databases, or custom API mappings.	Verify that your integration team has robust error logging, handles Microsoft Graph API throttling limits, and maintains data integrity across thousands of matters.
Native File Export & Upload	You are implementing a simple archival strategy without preserving active matter structures or metadata.	Microsoft’s native migration capabilities are designed primarily for supported file shares and SharePoint environments. Migrating from iManage typically requires a specialist migration solution or custom extraction and transformation processes to preserve document metadata, version history, workspace structures, and security permissions.

For most law firms, the choice of migration approach depends on the complexity of the existing iManage environment. Firms with active matters, extensive document metadata, multiple document versions, and complex ethical walls generally need a structured migration solution rather than a basic file export. Archival migrations with limited requirements may use simpler extraction and upload processes.

Law firms evaluating a move away from iManage should also consider the broader range of alternatives available within the Microsoft 365 ecosystem. Our guide to iManage Alternatives: Microsoft 365, SharePoint and Legal DMS explores how law firms can modernize document management without relying on traditional DMS platforms.

Law Firm DMS Migration Checklist

A successful legal DMS migration requires pre-defining exact mapping specifications for workspaces, metadata fields, version stacks, security ACLs, email headers, audit trails, and cutover freezes before executing bulk transfers.

Use this checklist to audit your technical requirements before migrating production data:

Workspaces & Matters

Map source client/matter workspaces to an appropriate SharePoint architecture using sites, document libraries, folders, content types, and metadata columns. Avoid unnecessarily deep folder structures and ensure the destination architecture supports matter-level access control and document discovery.

Document Metadata

Map essential legal properties—including Document IDs, client/matter numbers, document types, authors, and creation/modification dates—to SharePoint custom columns.

Migration of legal documents from iManage to SharePoint Online with metadata preservation

Version History

Determine whether to migrate full version histories or designated major versions, and verify how version stacks display to end users.

Permissions & Security

Map legacy iManage ACLs to an appropriately designed SharePoint security model using Microsoft Entra ID groups and SharePoint permissions. Validate inherited and unique permissions, external sharing restrictions, and ethical wall boundaries using representative user accounts. Minimize unnecessary item-level permissions and design the workspace structure to support manageable permission scopes.

Emails & Attachments

Ensure original .msg and .eml files retain their original content and relevant header information, including sender, recipient, subject, and timestamps. Validate that migrated emails and attachments can be located through the destination search experience.

Legal document metadata mapping from iManage to SharePoint custom columns

Document Relationships, Links and Shortcuts

Validate document-to-document references, email-to-attachment relationships, and links embedded in documents where applicable.

Records & Audit Trails

Plan how historical audit logs will be archived and how governance policies will apply in Microsoft Purview.

Cutover Strategy

Define baseline data syncs, incremental delta passes, the editing freeze window, and sign-off criteria.

Document Identity and Deduplication

Establish how source document identifiers will be mapped to destination documents, identify duplicate files, and maintain traceability between original iManage records and migrated SharePoint documents.

PageLightPrime extending Microsoft 365 and SharePoint into a legal document management system

Recommended 6-Phase Project Sequence

The optimal legal DMS migration project sequence moves linearly through discovery, destination architecture, pilot testing, data reconciliation, phased wave migration, and post-cutover validation to maintain business continuity.

A seamless migration follows a structured methodology to ensure business continuity at cutover:

1. Inventory the Source

Catalog document and version counts, total storage volume, active workspaces, custom metadata fields, and permission exceptions.

2. Design the Destination

Architect your SharePoint Online taxonomy, content types, and metadata schemas prior to bulk data loading.

Preservation of legal document version history during iManage to SharePoint migration

3. Run a Representative Pilot

Test the migration pipeline against a diverse sample of restricted workspaces, multi-version files, archived emails, and cross-referenced documents.

4. Reconcile the Pilot

Audit pilot document counts, metadata accuracy, version stacks, and security permission boundaries.

5. Migrate in Waves

Execute data transfers in manageable waves, run incremental delta passes for active documents, and reconcile document counts, metadata, permissions, and migration exceptions after each wave.

6. Post-Migration Validation

Maintain the legacy system in a read-only state during an agreed validation window prior to decommissioning.

Microsoft 365-native legal document management architecture using SharePoint, Outlook, Word, and Teams

How PageLightPrime Extends SharePoint into a Legal DMS

SharePoint Online provides the document storage, collaboration, security, and governance foundation of Microsoft 365. However, law firms need additional capabilities to manage documents around clients and matters, organize legal workspaces, file emails, automate document workflows, and connect document management with practice management.

PageLightPrime extends Microsoft 365 into a purpose-built legal document management software and law firm practice management platform. Rather than introducing another proprietary document repository, PageLightPrime uses the law firm’s Microsoft 365 environment, with matter-related documents remaining in the firm’s SharePoint Online and OneDrive infrastructure.

This architecture allows law firms to combine Microsoft 365’s identity, security, collaboration, and governance capabilities with specialized legal workflows for document management, matter management, time tracking, billing, trust accounting, and client collaboration.

Microsoft Entra ID groups and SharePoint permissions for secure law firm document management

Key Capabilities of PageLightPrime:

Native Microsoft 365 Integration & Governance

Operates within your firm’s Microsoft 365 environment, keeping matter documents in your own SharePoint Online and OneDrive infrastructure while leveraging Microsoft Entra ID and Microsoft Purview capabilities for identity, access control, and information governance.

Automated Matter-Centric Collaboration

Automatically provisions client and matter workspaces with standardized document libraries, metadata structures, and access controls.

Migration and organization of legal emails and attachments from iManage to Microsoft Outlook and SharePoint

Seamless Email & Document Management

File emails directly from Microsoft Outlook into client and matter workspaces, retaining relevant email metadata and maintaining relationships between filed emails and their attachments through integrated law firm email management system.

Enterprise Legal Search

Search across matter documents, custom metadata, and filed emails using centralized legal search capabilities integrated with the Microsoft 365 environment.

Complete Practice Management Suite

Unify document management with legal time tracking, trust accounting, client portals, and workflow automation in a single platform.

Validation of migrated legal documents, metadata, versions, and security permissions

“

Planning an iManage Migration?

PageLightPrime helps law firms transition to Microsoft 365-native legal document management while keeping matter documents within their own Microsoft 365 environment. Contact us to discuss your existing iManage architecture and migration requirements.

Ethical walls and matter-level access controls in Microsoft 365 for law firms

“

Frequently Asked Questions (FAQ)

Can law firms migrate from iManage to SharePoint Online?

Yes. Law firms can migrate from iManage to SharePoint Online Legal DMS using specialist migration platforms, custom extraction and migration processes, or a combination of both. The appropriate approach depends on the source environment, document volume, metadata complexity, version history, workspace structures, and security requirements.

Can iManage document metadata and version history be preserved during migration?

Yes, provided the migration process explicitly supports metadata transformation and version-history migration. Document identifiers, client and matter numbers, document types, authors, timestamps, and version information should be mapped to the corresponding SharePoint properties and version history. These mappings must be validated through representative pilot migrations.

How are iManage permissions and ethical walls handled in SharePoint?

Legacy iManage access permissions must be analyzed and mapped to the destination SharePoint security architecture. This typically involves Microsoft Entra ID groups, SharePoint site and library permissions, and appropriate information protection and compliance controls. Ethical wall restrictions must be tested using representative user accounts to verify that unauthorized users cannot access restricted matter information.

Does migrating from iManage to SharePoint require moving all documents into a new document repository?

Not necessarily. A Microsoft 365-native legal DMS can use the law firm's existing SharePoint Online and OneDrive infrastructure for document storage. With PageLightPrime, matter documents remain within the firm's Microsoft 365 environment rather than being transferred to a separate PageLightPrime document repository.

Can SharePoint replace iManage for law firms?

SharePoint Online provides enterprise document storage, collaboration, security, and governance capabilities. However, law firms generally require additional legal-specific functionality, including matter-centric workspaces, Outlook email filing, document automation, legal search, and practice management. A purpose-built legal DMS such as PageLightPrime extends Microsoft 365 with these capabilities.

How long does an iManage to SharePoint migration take?

The timeline depends on document volume, number of workspaces, metadata complexity, version history, security requirements, and the migration approach. A structured project typically includes source discovery, destination architecture, pilot migration, reconciliation, phased migration, and post-migration validation. A realistic timeline should be established after assessing the source environment.