The Real Reason Leaving an E-Discovery Vendor Costs So Much

The price of leaving is set in the fee schedule, long before the drives are returned.

Leaving an e-discovery vendor costs so much because the vendor holds data you remain answerable for, and it prices the return of that data at the moment you have least room to refuse.

I would ask the reader to consider one point of law before any point of price. The Federal Rules of Civil Procedure require a party to produce ESI within its "possession, custody, or control," yet, as a 2019 Florida Bar Journal article by Effie D. Silva, Sonia Zeledon and Justin M. L. Stern observes, the rules never define that phrase. Courts have filled the silence with three competing tests: the legal right standard, the legal right plus notification standard, and the practical ability standard. Under the last, a party may control information it neither owns nor physically holds, for instance where a contract empowers it to obtain that information from a non-party.

That is the vendor's position exactly. Your collection sits on its servers. Your duty does not move with it.

It appears, then, that an exit fee is rarely a charge for storage alone; it is a charge levied upon a lawyer's continuing obligation, and it is worthy of notice how seldom the contract says what that charge will be. The invoice is where the matter first shows itself.

Where do exit charges sit on an e-discovery invoice?

Exit charges sit outside the rates buyers compare. Firms benchmark hourly and per-document review prices, while per-GB transfer and hourly export labour stay unpriced until departure.

Before signing a hosting agreement, I would put three plain questions to the proposal, and I would want each answered in writing:

1. What is the charge, per gigabyte, to move the entire matter out of the platform?
2. What hourly rate applies to building and checking load files, and is there a ceiling on those hours?
3. Does monthly hosting continue to bill while the export is being prepared?

Before any vendor meeting, it is worth asking for the rate card line that governs export, and noting whether one exists at all. The Winter 2025 eDiscovery Pricing Survey, conducted by ComplexDiscovery OÜ and EDRM, found that in 2025 most remote attorney review rates fell between $25 and $40 per hour, and that GenAI-assisted review was most often priced at $0.26 to $0.50 per document. In 2025, the same survey described per-GB pricing for GenAI review as "still largely undefined", and found that about 50% of respondents were uncertain how special processing or exception handling is priced.

The common assumption is that the review rate decides what a matter will cost. I am inclined to think otherwise. In 2025 the survey's publisher reported that review fell from 73% of eDiscovery task spending in 2012 to 64% in 2024, with a projected 52% by 2029, while collection and processing took a larger part of each bill. Ask which of those larger lines would recur on the way out. Exit is data handling.

Nor is the underlying work imaginary. Practitioner guidance in the American Bar Association's GPSolo magazine lists, among its platform selection criteria, the ability to produce and export documents in formats that meet court requirements. That is a fair requirement. Yet the guidance, as I read it, sets no price upon the capability, and in 2023 services rather than software held more than 65% of the eDiscovery market, which is to say that much of the spend is labour, and labour is commonly billed by the hour.

An analysis of 4 sources shows the same pattern: the export is named as a duty and left off the rate card. Ask where on the invoice export work would appear. Ask, as well, for a written estimate of export hours on a matter of your size.

For a large enterprise this is an irritation; for a small firm it weighs far more heavily. Relevant e-Discovery was built to be operable and affordable for a solo or small firm on a single messy matter, the very segment that Relativity and Everlaw price out and cannot serve without an administrator. Firms in that position ought to read exit terms as closely as review terms, in the same spirit as they would read the clauses that let an AI review vendor swap models mid-matter. And even a clean export, it appears, does not end the expense, for the coding and privilege calls a team has built rarely travel with the files.

Why is switching platforms hard even after the data is exported?

Switching stays hard because files travel and work product often does not. Coding decisions, privilege calls, and the link from each answer to its source exhibit are what a departing firm loses.

I have observed that buyers picture an exit as the moving of boxes. It is rather the moving of a library whose catalogue was written in the old building's private shorthand. The catalogue is the asset. Three things, in particular, are at risk in the passage:

• Coding and tags. Responsiveness and issue tags live in the platform's own fields, and each must be mapped, field by field, into the receiving tool.
• Privilege decisions. Every call, and the reasoning behind it, must arrive intact, or the new team repeats the labour at its own expense.
• Provenance. The path from a conclusion back to the document that supports it is easily severed in conversion.

A 2023 discussion on Reddit's r/ediscovery set out the mechanism with unusual candour. One practitioner wrote that DISCO and Everlaw "convert everything to PDF and force you into their workflow." Another commenter observed that a large body of reviewers, paralegals and lawyers trained on Relativity were "too expensive to train on another platform," which gave service providers a standing reason to stay where they were.

A converted file is not the original. Once natives have become images, a later exit must either accept what was lost or pay to rebuild it. Neither appears on the rate card.

It is worthy of notice who feels this and who does not. A 2024 thread asking about the profession's pain points drew a reply of four words: "To stop paying for it." The same thread held that "lawyers don't care about pain points in e-discovery because they don't feel the pain." The attorney who signs the hosting agreement is seldom the person who later rebuilds a privilege log by hand. That gap, between the signer and the sufferer, is where migration costs grow unexamined.

The remedy, as I see it, lies in how the record is kept from the first day. At Relevant e-Discovery, every answer traces to its source: outputs link back to the exact exhibit they came from, so an attorney can verify with one click before filing. Originals are held immutable with content hashing, beneath an append-only audit trail and a documented chain of custody, so the record of what was done to each document exists apart from any one screen. The same discipline matters at the front door, where one-click cloud collection tools miss several things a defensible record needs.

A record kept this way can be carried. A record kept only in a vendor's interface must be reconstructed, and reconstruction is billed by the hour, which brings us to what a firm can fix on paper before it ever signs.

How can a small firm cap e-discovery exit costs before signing?

Ask for two clauses before signing, a fixed per-GB exit ceiling and a capped export labour budget, then test the vendor on your own messy collection before committing.

Ask the vendor, in writing, what it would charge to return every matter on the last day of the term. Cutting the cost of document review is one aim; ask also for a written export estimate sized to your own matter. Neither clause below is offered as a market standard. Both are negotiation asks, and I would expect resistance to each.

Clause one: a fixed per-GB ceiling on egress and export

Core Message: the price of taking data out should be fixed at the same moment as the price of putting it in.

Before (the usual silence): the agreement prices ingest, processing and monthly hosting per gigabyte, and says only that export services are available at the vendor's prevailing rates.

After (suggested wording): Provider shall export all Customer Data, in native format with associated metadata, at a per-GB rate fixed at signing and no greater than the per-GB processing rate in Schedule A, for the full term and any renewal. Hosting charges cease on the date Customer requests export.

The second sentence carries as much weight as the first. Without it, the meter runs while the export is prepared.

Clause two: a not-to-exceed cap on export labour

Core Message: hourly work needs a ceiling and a defined finish line.

Before: load-file creation, quality control and migration support are billed hourly, with no estimate and no definition of a complete delivery.

After (suggested wording): Fees for load-file preparation, quality control and migration support shall not exceed the amount in Schedule B. Delivery is complete when Customer receives native files, extracted text, all metadata fields, hash values, coding and privilege fields, and load files in an industry-standard format.

A definition of done should also name exceptions, for the processing exceptions your vendor isn't showing you belong on that list rather than on a later invoice. Coding and privilege fields are named deliberately. They are the work product a firm paid to create.

The second safeguard is a test before commitment. Our own demonstration asks a buyer to bring a messy collection and a hard question, and to watch the tool read, code and cite their own evidence rather than read a case study about someone else's. The economics ought to be visible in the same sitting: at Relevant e-Discovery, AI-assisted review runs cents per document, against the dollars per document and roughly $19K/GB of manual review, a difference the buyer can see on their own matter.

Our deployment model also answers the exit question at its root. Processing runs single-tenant, or inside the client's own AWS account under the client's own keys, with no vendor retention and no model training. A firm that holds its own keys has no egress to negotiate. The clauses above still matter for any hosted vendor, and they matter most where an export must arrive complete enough to satisfy a court.

What should a firm settle before it signs its next e-discovery contract?

Settle three things in writing: the per-GB export rate, a ceiling on export hours, and what a complete export must contain, including metadata, hash values and coding.

I am inclined to think the next quarrel over vendor data will be fought in court rather than over an invoice. The Florida Bar Journal authors note that district courts in the 11th Circuit moved toward the practical ability standard after 2006, and that one court, in Selectica, Inc. v. Novatus, Inc., applied that test to the duty to preserve. Ask, then, who at the vendor would answer a court's question about where the data sits and how quickly it can be produced.

The stakes are not small. In Coleman Holdings v. Morgan Stanley, a failure to preserve internal e-mails produced a $604.3 million verdict, and the verdict with fees came to over $1 billion.

An export that drops metadata is no longer a billing nuisance. It is evidence handled badly.

So the two clauses belong in the first draft, not the renewal, and the honest test is whether a vendor will put its exit price in writing on the day it asks for your data.