iManage and Microsoft 365: what works, what doesn't

iManage runs its own document management backend for matter documents; Microsoft 365 storage handles everything else in the firm (templates, precedents, marketing, internal comms, HR). Most firms end up running both, and they can coexist cleanly. The trouble starts when the OneDrive sync client is quietly configured (usually by default) to sync the same folders iManage uses for its own local cache. This piece walks through the specific pitfalls, the fix patterns that keep the two systems out of each other's way, and how Cloud Drive Mapper gives fee-earners the mapped-drive experience they know from iManage, applied to Microsoft 365 storage.

What breaks when iManage and the OneDrive sync client collide?

Six recurring issue patterns. All of them come from OneDrive sync operating over files or folders iManage assumes it has to itself.

iManage's local cache gets swept into OneDrive sync

iManage Work Desktop stores checkout copies and cached documents inside the user's Windows profile. If that profile has been touched by OneDrive Known Folder Move (KFM), the iManage cache can end up inside an OneDrive-synced Documents folder. OneDrive then tries to sync every DMS checkout as it happens, producing bandwidth churn and "conflict copy" versions of matter documents that should never exist outside iManage.

Outlook email-filing produces duplicates or hangs

iManage Communications Manager files emails from Outlook into matter workspaces. It uses temp files in the user profile during that process. If Outlook's temp folder or the working file location is OneDrive-synced, filing operations can hang, fail silently, or file the same message multiple times as OneDrive interferes with the intermediate files.

Local search-index files churn against sync

iManage Work Desktop maintains a local search index. If the index lives in a OneDrive-synced location, OneDrive tries to sync every index update: high-volume small-file changes, sync backlogs, and eventually the index corrupts under conflict pressure. Users complain that search results are inconsistent or missing entirely.

Offline sync doubles up

iManage has its own offline sync capability for fee-earners working away from the office. If OneDrive is simultaneously syncing the same content, you get two competing offline stores with no clear source of truth, and the fee-earner's laptop becomes a battleground of change conflicts.

Templates and precedents fail to load under Files On-Demand

Fee-earners regularly open template documents or precedent files from shared libraries while iManage is mid-operation. If those files live on OneDrive with Files On-Demand and have not been hydrated recently, the open request can time out or fail before the sync client can pull the file down.

SharePoint isn't accessible in a way fee-earners recognise

The SharePoint browser experience and the OneDrive desktop client are not the drive-letter, folder-hierarchy view fee-earners have used inside iManage for two decades. Even when the M365 side of the firm's storage is configured correctly, users find it awkward and default back to emailing documents to themselves. Adoption of the SharePoint tier of the firm's storage suffers as a result.

Why iManage and the OneDrive sync client don't naturally coexist

iManage and the OneDrive sync client are both trying to be authoritative about the same class of thing: a document, its versions, its lock state, its cache. Neither was designed with the other in mind. When they overlap on the same folders they trip each other up, because each thinks it owns the file lifecycle.

Add the drive-letter mismatch on top: iManage presents documents through its own DMS UX that fee-earners are trained on; OneDrive presents documents through Explorer folders and browser tabs. Two UX patterns for what looks like the same task is friction, and firms end up with fee-earners who quietly ignore whichever system they did not master first.

For the broader take on why sync clients struggle with applications that assume they own the filesystem, see Desktop applications and real file paths. iManage is a specific case; the underlying mismatch affects the wider category of DMS, DAM and matter-management tools that maintain their own local caches.

What are the fix options?

Three approaches. The first two are boundary-setting; the third is the drive-mapping approach this page is about.

Carefully configure OneDrive to skip iManage folders

Set OneDrive selective sync (and Known Folder Move exclusions) to leave iManage's local cache, Outlook temp locations and search-index folders alone. Effective when done meticulously, and fragile because a new user setup, a profile migration or a Windows update can reintroduce the overlap silently. Works best in tightly-managed environments where IT retains firm control of user profile configuration.

Move non-DMS content to SharePoint but skip the OneDrive desktop client

Store non-matter content in SharePoint libraries. Have fee-earners access those libraries through the browser or through Teams. Avoids the sync-client conflicts entirely. The trade-off is UX: the browser view does not match the mapped-drive muscle memory fee-earners have from iManage, and adoption of the SharePoint tier typically lags.

Use a drive-mapping approach (Cloud Drive Mapper)

Present SharePoint document libraries as real Windows drive letters. Fee-earners get the mapped-drive view they know from iManage, applied to the firm's non-matter Microsoft 365 content. No sync client is involved, so nothing overlaps with iManage's own cache or Outlook filing workflows.

How Cloud Drive Mapper fits with iManage

CDM is not a DMS. It does not replace iManage's matter numbering, security-group model, workflow automation or full-text search across the matter corpus. Where CDM fits is on the non-DMS side of the firm's storage, and (for firms considering it) on the migration side.

Coexistence: SharePoint as a mapped drive alongside iManage

Most firms run CDM alongside iManage. iManage owns matter content and everything that goes with it; CDM gives fee-earners a drive-letter view of SharePoint document libraries for everything else. The two systems never touch the same files, and there is no OneDrive sync client to interfere with either.

Because CDM does not use a local cache the way OneDrive does, iManage's cache folders, Outlook temp locations and search-index files are unaffected by CDM being installed on the endpoint. Everything OneDrive struggles with is a non-issue.

Migration: SharePoint as the storage layer, DMS features re-created separately

Some firms are actively considering retiring iManage in favour of SharePoint-native document handling. This is a big undertaking and CDM alone does not complete it: matter numbering, security-group models and DMS workflows have to be rebuilt inside SharePoint. What CDM delivers is the storage-side experience. Fee-earners see SharePoint document libraries as mapped drive letters, with familiar folder navigation and native SharePoint check-out for document locking. If matter documents themselves move to SharePoint, CDM gives fee-earners a view of those matter folders that closely resembles what iManage delivered locally.

Hybrid: iManage plus M365 plus CDM

A common current pattern. iManage (Cloud or Work Server) handles the matter DMS; SharePoint handles precedents, templates, marketing, internal comms; CDM presents SharePoint as mapped drives. Fee-earners have two workflows (iManage for matters, mapped drive for everything else), each clean and unambiguous.

iManage-specific configuration notes

Nothing exotic is required. Install CDM as normal and map SharePoint document libraries to the drive letters the firm uses (typically M:, N:, or similar). Fee-earners do not need to change how they work with iManage itself; the mapped drive appears in Explorer and File Open/Save dialogs alongside their iManage workspace.

If the firm is moving away from OneDrive Known Folder Move, unenrol users cleanly before deploying CDM. If KFM is being retained for personal OneDrive space, ensure iManage's local cache and Outlook temp locations are excluded from KFM's Desktop, Documents and Pictures redirection.

CDM supports iManage-adjacent workflows in the following deployment models:

• Windows desktops (direct)
• Citrix Virtual Apps and Desktops
• Citrix DaaS
• Azure Virtual Desktop (AVD)
• Windows 365 Cloud PC
• Omnissa Horizon (formerly VMware Horizon)

Cloud Drive Mapper is used across law firms and legal departments to give fee-earners the mapped-drive experience they know from a DMS, applied to Microsoft 365 storage.

Frequently asked questions

Does Cloud Drive Mapper replace iManage?

No. CDM is drive-mapping middleware for Microsoft 365 storage, not a document management system. It does not provide matter numbering, security-group models, workflow automation or DMS-grade full-text search across the matter corpus. Firms that want to retire iManage need to rebuild those DMS features inside SharePoint separately; CDM handles the storage-layer experience during and after that transition.

Does Cloud Drive Mapper work alongside iManage Cloud?

Yes. iManage Cloud handles matter content and everything the firm has structured inside it; CDM handles everything else the firm stores in Microsoft 365. The two systems operate on separate content and do not interfere with each other. Most CDM-in-legal deployments run alongside iManage in some form.

Will CDM interfere with iManage's local cache or Outlook filing?

No. CDM does not maintain a local sync cache. iManage's own cache folders, Outlook temp files and Communications Manager filing operations are completely unaffected by CDM being installed on the endpoint. This is one of the main reasons firms move away from the OneDrive sync client and towards a drive-mapping approach.

Can CDM present matter documents from SharePoint as a mapped drive?

Yes, when those matter documents live in SharePoint (either because the firm has migrated them there or because they were stored in SharePoint from the beginning). CDM presents SharePoint document libraries as Windows drive letters regardless of what content is inside them.

Does CDM work with iManage Work Desktop and its predecessors (DeskSite, FileSite)?

Yes. CDM does not touch iManage's local cache or configuration. iManage Work Desktop (and legacy DeskSite and FileSite clients) operate against the iManage DMS backend as they always have; CDM operates against Microsoft 365 storage on the same endpoint. The two live side by side without contention.

Which locking model does CDM use for SharePoint documents?

SharePoint's native check-out. When a fee-earner opens a document from a CDM-mapped drive, CDM triggers a SharePoint check-out automatically. A second user opening the same document sees it as checked out and receives a read-only copy. This mirrors the exclusive-lock model iManage users are already familiar with.

Related solutions

• Desktop applications and real file paths (the underlying problem class)
• OneDrive for Business in Citrix (many firms run DMS + M365 over Citrix)
• Replacing your file server with SharePoint
• Overcoming the OneDrive 300,000 file sync limit (matter archives frequently hit this)
• Cloud Drive Mapper for legal and professional services

← Back to all solutions