NetDocuments vs iManage: Mid-Size Firm Guide 2026

Key Takeaways

• Neither vendor posts a rate card, so the only price that counts is a written quote that lists users, email filing, AI, walls, storage, migration, and training.

• NetDocuments still sells its cloud document system, and it also owns Worldox and eDOCS. eDOCS is an on-premises product NetDocuments says it will keep supporting.

• iManage still sells Work as the document and email system, and it sells a wider catalog around it: sharing, desktop drive, mobile access, security policy, threat monitoring, records, and disposition.

• The choice is the matter file, not the AI assistant. An assistant can summarize what is already filed. It does not replace client and matter profiles, ethical walls, or an audit history.

• A workflow sitting above either system is useful only after the profile fields exist and a named person reviews exceptions before anything goes to a client or opposing counsel.

What you are actually choosing

A legal document management system is the matter file of record: documents and email saved to a client and matter, with versions, permissions, and a history of who touched them.

TL;DR: Pick NetDocuments if you want the vendor to run one cloud file and you will make the quote show whether email filing and AI are included. Pick iManage if you want the governance products large firms already run and you have someone to own workspace design and the rollout. Skip both if you only need shared folders, a public price list, or a register of contract renewal dates.

Neither name in this search was retired or renamed. Both companies still sell a document system in 2026. Two older names sit in the NetDocuments story and should not be shortlisted as independent vendors. NetDocuments acquired Worldox on October 18, 2022 according to NetDocuments (2022). Treat a Worldox estate as a migration question. Ask NetDocuments for the current support position in writing before you extend that estate.

The job this page covers is the matter file. Pleadings, correspondence, email, and work product have to land on the right client and matter, stay on the right version, and stay behind the right wall. A contract system that tracks renewal dates and clause positions answers a different question. An AI assistant that drafts from documents answers a third question. Buying the assistant and skipping the file leaves the firm with two places where the "real" document might live.

Who this is for

This comparison is for the operations or IT lead at a mid-size law firm who already knows the firm needs a matter-centric file and is close to a decision. You are weighing a cloud service the vendor operates against a platform whose catalog also includes policy barriers, threat monitoring, and records disposition. You can sit through a scripted demonstration and still demand a written scope.

Red flags: you will not talk to sales without a public price list; you only need a shared folder and will not profile documents to clients and matters; you need renewal dates and clause positions rather than a matter file.

Use this short list in the demonstration, in this order. Ask each vendor to file an email from Outlook onto a matter without a second copy left in the mailbox. Ask them to show a lateral hire blocked from a walled matter, then show the log of that denial. Ask them to open a prior version and to show who last changed the current one. Ask them to run an AI answer on a walled document using an account that should not see it, and confirm the answer is refused. Ask them to point at the line on the quote for email filing, AI, walls, storage, migration, and training.

How we evaluated these tools

The weights below are our buying criteria for this reader. They are not a score the vendors earned, and they are not a ranking. We set them so a mid-size firm spends its demonstration time on the failures that are expensive to undo.

Matter structure carries 25% because the cabinet model is the system. A firm that files by client and matter, then later discovers the product wants a different parent and child, is looking at a migration, not a setting. Email filing carries 20% because most of the record still arrives as mail. If filing is clumsy, lawyers leave mail in the inbox and the firm quietly runs two files. Walls and audit history carry 20% because lateral hiring and conflicts do not wait for a large-firm badge. Cloud operations carry 15% because someone has to own uptime, residency, and restores, and that someone is either the vendor or the firm. Microsoft 365 fit carries 10% because Word, Outlook, and Teams are where the hours actually go. Permission-aware AI carries 5% because a summary of the wrong documents is worse than no summary. Quote scope carries 5% because neither vendor publishes a price, so the written inclusions are the only comparable number.

We did not award points for slogans, logo walls, or unpublished per-user rumors. We also did not treat a rival's comparison page as proof about the other product. Where a page states a count, a rating, or a date, that figure is quoted once, next to the page, and it is not reused as a different number later.

The public record, separated from our read

These figures are what the companies publish. They are reach and adoption claims, not a measure of which product will fit one firm.

AM Law 100 share: 79% according to iManage (2026), which in the same March 10, 2026 release also reported 83% of the Top Global 100, 40% of the Fortune 100, 71% of its global customer base on its cloud, 340 new customer logos in 2025, more than 1 million professionals at 4,000 organizations, Cloud uptime of 99.98% in 2025 and 99.99% over the trailing 12 months, and a benchmark in which 85% of organizations were piloting or implementing AI while 17% had fully integrated it. The same release says Ask iManage answers from governed content with citations back to the source, and that its outside-tool connector was targeted for general availability in the first half of 2026.

Our read of that record: iManage is the default name at the top of the market, and a cloud subscription is the majority path, not the only way the installed base runs. The AI benchmark is iManage's own report about organizations, not a census of law firms. A mid-size firm should not treat those percentages as a promise that the rollout will be short. The release does not publish a project length.

Cloud law firms: 1,500+ according to iManage (2026), which also states a 5:1 margin among ILTA members choosing its cloud. That page is iManage arguing against NetDocuments. Use it for iManage's own counts. Do not use its descriptions of the other product as settled fact. On price, the same page's questions section says the amount varies by firm size, products, deployment, and implementation scope, and it does not list a dollar rate.

Filing, walls, and the Microsoft desktop

Day to day, lawyers meet the product in three places: the matter workspace, the Outlook file button, and the permission check that should stop a walled document from leaving. NetDocuments describes workspaces and client portals built around matters and projects, version history that includes sub-versions, and one-click predictive filing of email. Its security pages describe walls at the user, document, or workspace level, data-loss prevention, activity logs, optional customer-managed encryption keys, and a choice of where content is stored geographically. iManage describes matter workspaces, email inside Work, and a Security Policy Manager that places barriers at client, department, or project level. Threat Manager, Records Manager, and Disposition Manager are separate named products on its security pages, not a single checkbox.

iManage's own administration guide is the right place to see how a firm actually labels the file. The internal property many firms caption as Client is the parent, and the property they caption as Matter is the child. A system property keeps its own name even when the label on screen changes. That is the field in the illustration below.

An illustrative 40-lawyer litigation group, not a firm anyone measured, takes in 120 new filings in a week. At 8 minutes to name, profile, and save each one, the arithmetic is 120 times 8 minutes, which is 960 minutes, or 16 hours. Cut the profile step to 4 minutes and the same 120 filings take 480 minutes, or 8 hours, which hands 8 hours back to the lawyers. The save still has to write iManage's last_user property so the history shows who touched the file, and a conflicts clerk still checks the client and matter values before anyone shares the document outside the workspace.

The table is the same illustration, not a timed study and not a vendor benchmark. The point of the arithmetic is that the minutes live in profiling, and the control lives in the person who may release the file. Speeding the save without that check just moves a bad profile faster. External sharing belongs in a separate decision from filing, which is why a firm should read a client document sharing comparison beside the wall settings rather than assuming the document system is also the client portal.

AI sits on top of that file. NetDocuments' assistant page says a user can question selected documents, build a chronology, and make tracked edits in Word, with the content staying inside the tenant and behind the same permissions. iManage's March 2026 release describes Ask iManage the same way: a question across documents, matters, and email, with the answer tied back to the source. Bind reports a Harvey technology partnership with iManage announced on 5 June 2025 and an open beta on 11 August 2025, according to Bind (2026). Read those dates as evidence that the assistant and the file are different products wired together. A review workflow still needs a human on the citation, which is the same discipline as an automated legal document review that refuses to send work product out unreviewed.

Pricing checked against the public pages

Pricing checked October 10, 2026.

On that date, the pricing path on NetDocuments' site and the pricing path on iManage's site did not open a rate card. Neither page listed a plan price. Bind, which sells contract software and says neither vendor publishes a rate card, also dates NetDocuments' ndConnect program with Harvey and Legora to 31 July 2025, according to Bind (2026). Gartner's product note describes NetDocuments as a subscription shaped by user count and modules, and it does not list a dollar figure either. Until a vendor publishes a rate card, the honest price is Quote-based.

iManage's comparison page says NetDocuments licenses ndMail, ndMirror, and the full AI suite separately. That is a rival's statement, and NetDocuments' own cloud page presents predictive email filing and the assistant as part of the product story. The practical move is the same either way. Make the quote mark email filing, AI, walls, encryption-key control, residency, storage, migration, training, and the first year of support as included or extra. Do the same for iManage's Security Policy Manager, Threat Manager, Records Manager, Disposition Manager, Share, and Drive. A thin per-user number that hides those lines is not a price you can compare.

Closing packages are a separate line from the subscription. Document bundling and a signature step still have to land back on the matter with the signed version, not in someone's downloads folder. If the signature tool is its own purchase, price it beside the file using a signature workflow for legal documents, and name who checks the signed copy before it is profiled.

NetDocuments, for a firm that wants one cloud system

NetDocuments fits a firm that wants the vendor to operate the cloud file, wants matter workspaces, and will live in a browser plus the Microsoft add-ins. It also fits a firm that already runs Worldox or eDOCS and wants one company to ask about a later move. It is a poor fit if you require the NetDocuments product itself on servers you patch. That product is described as cloud. The on-premises product in the family is eDOCS, and it is not the same system.

Customers worldwide: 7,000+ according to NetDocuments (2026), which also states 150+ integrations, a presence in over 90 countries, and completion of the eDOCS purchase from OpenText on January 12, 2026, with no end-of-life plan for that on-premises product. The same release says existing eDOCS customers are not required to move until they choose to. A firm that is stable on eDOCS should get that promise in its own contract, not only in a press note.

Gartner Peer Insights lists a 4.3 rating from 68 ratings for NetDocuments, with 49% at 5 stars, and describes the company as private, founded in 1998, based in Lehi, with 201 to 500 employees, according to Gartner (2026). That is a peer average, not a head-to-head trial against iManage, and the review count is the whole sample behind the average.

Limitations follow from the public record. There is no rate card, so module boundaries stay unclear until the quote. The security story is real on the page we opened: walls, data-loss prevention, logs, optional customer-managed keys, geo-aware storage, and a statement that the service is mapped to GDPR, HIPAA, and LGPD, with a FedRAMP mark displayed. None of that tells you which of those controls are in the base subscription. Administration does not disappear in the cloud. Someone still builds profile attributes, workspace patterns, walls, and the Outlook behavior, and someone still samples the logs.

Implementation, from what NetDocuments publishes, is configuration of a service the vendor runs rather than a server build. Budget time for the client and matter lists, the historical document load, the Microsoft add-ins, and a week of supervised filing with a pilot group before you turn off the old share. Ask for the exit terms in the same packet as the price: format of the export, whether versions and profile values come with it, and who pays for the extract.

iManage, for a firm that wants the governance catalog

iManage fits a firm that wants Work as the file and also wants named tools for policy barriers, threat monitoring, records, and disposition. It fits a firm whose clients already expect that stack, and a firm that can name an owner for workspace templates. The cloud-firm count above is a reason not to treat iManage as a product only the largest firms may buy. It is a weak fit if nobody will own the template design and the rollout, because the catalog is wide enough to buy badly.

Gartner's iManage vendor page lists iManage Work at 4.5 from 107 reviews in Document Management, according to Gartner (2026). Again, that is a peer average on a different sample size, not a bake-off. Do not subtract 4.3 from 4.5 and call the result a decision.

On the pages iManage publishes, the document products are Work, Share, Drive, and Mobility. The governance products are Security Policy Manager, Threat Manager, Records Manager, and Disposition Manager. Ask iManage is the in-product assistant. The company describes the platform as cloud-native and built for Microsoft 365, including Outlook, Word, Teams, Copilot, co-authoring, and autosave. Its own FAQ says a move to the cloud still runs through planning, design, configuration, data migration, testing, training, and production, and that the calendar depends on firm size, data volume, and integrations. No duration is published. Read that as a project with a statement of work, not as a switch.

Limitations are the mirror image of the catalog. A quote that says "Work" and stays silent on walls, threat monitoring, and records can look cheaper than a quote that includes them. Deployment is not "whatever you want" in the sense of a published menu with prices. You have to ask which new customers can still run somewhere other than the vendor cloud, because the company publishes a cloud share of the base rather than a current on-premises rate card. Search and AI features are only as trustworthy as the profiles underneath them. If client and matter values are dirty, Ask iManage will cite a confident answer from the wrong pile.

A proposed layer above the document system

The document system stores the file. The gap at many firms is the handoff: mail that never got profiled, a bundle that left without a wall check, or a signed copy that never returned to the matter. That gap is where a configured workflow can sit, and it is also where a careless one creates a second copy of the record.

A proposed US Tech Automations workflow watches a monitored mailbox for messages whose subject, sender, or matter number matches an open workspace. The action files a copy into the document system, writes the client and matter profile, and opens an exception row when the match is missing or ambiguous. The output is a filed message plus a review queue. This needs an API or a supported export from the document system, and a mailbox the firm is allowed to read. A person reviews the exception row before the message is treated as filed, and again before anything is sent to a client or to opposing counsel. This is a design you would configure. It is not a claim about a firm already running it, and it has no measured time savings.

In the next step, US Tech Automations collects a packet only after a partner marks that packet ready. The action pulls the listed versions, applies the access list already stored on the workspace, and stops if a document sits behind a wall the recipient is not on. The output is a bundle record or a share link held for a records clerk. The prerequisites are the same API or export, a current wall list, and a named clerk. The clerk confirms membership on the wall and confirms the signed or final version is the one in the packet. Only then does the link go out. The document system remains the copy of record.

Zapier, Make, or n8n can support run histories, retries, error branches, and audit evidence when someone configures them. They are a fair way to move a file from a mailbox to a folder. The firm then owns observability, idempotency, escalation, access controls, and maintenance, including what happens when the same message is delivered twice or the document system rejects a profile. A proposed US Tech Automations design can keep the matter-profile check and the exception queue on one configured path, with the API or export as a prerequisite and with the clerk's approval as a required stop. The difference is who designs those controls and who gets called when a run fails. It is not a difference in whether a log can exist.

When NOT to use US Tech Automations

Do not add this layer when the document system's own email filing already catches the mailbox and lawyers actually use it. A second filer will create duplicates and a fight over which copy is official. Do not add it when the vendor will not provide an API or an export, or when nobody will staff the review queue. Do not add it when the only need is a shared folder for a small group that already lives in Microsoft 365 and does not require matter walls. In those cases the mailbox rule, the product's own filing button, or the folder you already have is the simpler tool, and an extra workflow is overhead.

Common mistakes before you sign

• Treating a per-user rumor from a review site as a price. The vendors have not published one, and the rumors do not match each other.

• Buying the AI assistant first. If email never lands on the matter, the assistant summarizes an incomplete file and the inbox stays the real record.

• Signing a Work quote that never mentions Security Policy Manager, Threat Manager, or records. You may discover the wall you saw in the demonstration is another product.

• Shortlisting Worldox or eDOCS as if they were still separate companies. They are NetDocuments products, with different support promises, and a new buy should be scoped that way.

• Automating filing before the client and matter lists are clean. Faster profiling of bad values makes the search and the wall worse.

• Forgetting the exit. Ask how versions, profile values, and email leave, in what format, and at whose cost, before you start the migration in.

Glossary

• DMS. The document management system. Here, the matter file of record for documents and email.

• Workspace. The container for one matter or project, holding the documents, mail, and permissions that belong to it.

• Profile attribute. A field on the document, such as client, matter, or document type, used to file and to search.

• Ethical wall. A permission barrier that keeps a person, or a group, from opening a matter they must not see.

• Version. A saved generation of a document. The current one is what people edit. Older ones are how you prove what was sent.

• Audit history. The log of views, edits, shares, and permission changes. It is the evidence, not the search box.

• Quote-based. The vendor does not publish a price. You get a number only after a scoped conversation.

• System of record. The one place the firm treats as official. Mail left only in a mailbox means you have two.

Questions to settle before the quote

Does either vendor publish a price?

No. Both are quote-based. The pricing paths we opened on October 10, 2026 did not show a rate card, and the independent write-up cited above says the same.

Are NetDocuments or iManage discontinued?

No. Both are still sold. Worldox and eDOCS are the names that changed owners, and eDOCS remains an on-premises product with no end-of-life announced on the acquisition note.

Does the AI assistant replace the document system?

No. Both vendors describe the assistant as reading documents the file already holds and pointing back at the source. Harvey and Legora, on the dates cited above, are additional layers, not a substitute matter file.

Is Microsoft 365 enough on its own?

It is enough when you do not need matter-centric email filing or ethical walls. It is the wrong sole system when those two controls are the reason you started this search.

What has to be on the written quote?

Every module you saw in the demonstration, marked included or extra, plus migration, training, storage, residency, and the cost of getting your documents out later.

Where does a filing workflow fail?

It fails when client and matter values are wrong, when the same message can be filed twice, or when nobody reviews the exception queue before a document leaves the firm.

Should an eDOCS firm move now?

Not on this record. NetDocuments says eDOCS customers do not have to move until they choose. Get the support term and any future move path in your own paperwork, then decide on the jobs the current system cannot do.

The decision to take back to the partnership

Choose the product whose matter model matches how the firm already names clients and matters, whose email filing lawyers will actually click, and whose quote lists the walls and the AI you were shown. Keep the assistant, the signature tool, and any later automation as layers on that file. If the matter file is chosen and the quote is itemized, see how US Tech Automations configures this as a review queue on top of that file, with an API or export as a prerequisite and a person on the exception row, not as a second document system.