JurisPulse
Legal Tech

E-Discovery Cloud Migration: Confidentiality, Preservation, and the 2028 Deadline

Rafael A. Paz, Esq.

calendar_todayschedule6 min read

A vendor's product roadmap does not amend the Model Rules or the Federal Rules of Civil Procedure. It does decide when you have to apply them. Relativity's policy requires new matters created on or after January 1, 2028 to be hosted in its cloud platform, which turns a background technology question into a matter-intake decision 3.

My position is that you should treat the deadline as a forcing event for a documented analysis on two tracks. The first is confidentiality under the Rule 1.6(c) reasonable-efforts requirement as ABA Formal Opinion 477R applies it. The second is preservation and process under Rules 37(e) and 26 2, 5, 6.

What the Policy Requires, and What It Leaves to You

Relativity announced in January 2025 that new matters created on or after January 1, 2028 must be hosted in RelativityOne, with "limited geographical and use case exceptions" 3, 4. The company has since renamed its cloud platform, formerly RelativityOne, Relativity aiR 1. In October 2026, CEO Phil Saunders confirmed the deadline. He said the policy is "to make sure that no net new matter is going to Server effective Jan. 1." 1

Legacy matters keep Server support. Existing Server matters created on or before December 31, 2027 "will continue to be supported in Server," and Relativity says Server "isn't going away in 2028" 3. A provider that exits Server hosting or reprices its infrastructure can turn a legacy matter's continuity into a contract dispute, with your client's data caught in it.

Vendor exceptions carry no ethical weight. Nothing indicates they track the circumstances in which 477R says special precautions may be required 2. A client with a genuine need for heightened security may qualify for no exception. For that client, the answer may be stronger controls in the cloud or a different platform instead of staying on Server.

"New matter" has no definition. Saunders framed the rule around "net new" matters 1. Resolve that question in your provider agreement.

Confidentiality: Extending a Transmission Opinion to Hosted Data

The ABA Standing Committee on Ethics and Professional Responsibility issued 477R 2. It concludes that a lawyer generally may transmit client information over the internet without violating the Model Rules where the lawyer "has undertaken reasonable efforts to prevent inadvertent or unauthorized access." 2 It advises that special precautions may be required when a client agreement or the law requires them, or when the nature of the information demands a higher degree of security 2.

Applying that to years of hosting a review database is an extension. The opinion addresses transmission, and it updated Formal Opinion 99-413 on email 2. The extension holds up because 99-413 rested on the Rule 1.6 duty to use reasonable means to maintain confidentiality, and a hosted database stays exposed to unauthorized access continuously instead of only in transit 2. The operative standard is Rule 1.6 reasonableness as your jurisdiction applies it, with 477R as persuasive guidance.

The AI connector is a separate decision

In 2027, Relativity plans to make matter intelligence available through an MCP connector, so an authorized user in a tool such as Claude could query a matter 1. Enabling the connector moves matter data into a second vendor's environment. Before you rely on 477R alone, check whether the ABA or your state bar has issued guidance specific to generative AI 1, 2.

Preservation and Process Through a Platform Change

When migration becomes a Rule 37(e) problem

Rule 37(e) has a threshold. It reaches only ESI "that should have been preserved in the anticipation or conduct of litigation." 5 Migrating closed matters with no pending or anticipated litigation does not trigger the rule. Moving any data under a hold does. The rule then asks two questions: did a party's failure to take reasonable steps cause the loss of the information, and can additional discovery restore or replace it 5?

If the court finds prejudice, it may order measures no greater than necessary to cure it. Adverse presumptions, adverse jury instructions, dismissal, or default require a finding of intent to deprive 5. A documented validation plan gives you your best evidence of reasonable steps and your best answer to an intent argument.

Inaccessibility and cost you created

Under Rule 26(b)(2)(B), a party need not provide discovery of ESI from sources it identifies as not reasonably accessible because of undue burden or cost. On a motion, the party resisting discovery must make that showing 6. A decommissioned on-premises instance could plausibly fit the description. Expect skepticism if the inaccessibility results from your own voluntary decision to retire a system holding data you had a duty to preserve 5, 6.

The same logic limits proportionality arguments. Rule 26(b)(1) weighs whether "the burden or expense of the proposed discovery outweighs its likely benefit" 6. That factor measures the cost of the discovery requested and ignores a party's elective hosting costs. Sedona Principle 6, which Magistrate Judge Peck applied in Hyles and cited in Rio Tinto as consistent with his view, provides that responding parties are best situated to evaluate the technologies appropriate for preserving and producing their own electronically stored information 8, 9. The corollary is that the choice, and its cost, generally belong to the responding party.

Review protocols do not transfer automatically

Da Silva Moore recognized computer-assisted review as "an acceptable way to search for relevant ESI in appropriate cases." It did not endorse any vendor or any particular computer-assisted review tool, and it cautioned that the approved protocol would not suit every future case 7.

Later decisions built on that holding:

A stipulated ESI protocol can lock in your process during a migration. If the new platform changes your review workflow, renegotiate the stipulation before you switch.

What to Do Before January 2028

  1. Inventory incoming matters. Flag matters likely to open after December 31, 2027. Identify client agreements, legal requirements, or data sensitivity that may call for special precautions 2, 3.
  2. Pin down your provider. Ask whether it is moving to the cloud, running a hybrid model, or holding out. Get written commitments on continued support for legacy matters you leave on Server 1, 3.
  3. Diligence the hosting contract. Confirm data location, subprocessors, breach notification timing, data return or deletion at matter close, and audit rights. These terms are your evidence of reasonable efforts 2. If you need a geographical or use case exception, get it in writing 3.
  4. Raise platform changes at the Rule 26(f) conference. Build hosting, migration, and validation terms into the ESI protocol and the scheduling order.
  5. Validate any migration of held data. Reconcile document counts, compare metadata fields, and match coding before any legacy instance goes dark 5.
  6. Gate AI connectors separately. Allow frontier-model access to a matter only after a separate assessment, a review of vendor retention and training terms, and client consent where the engagement or the data calls for it 1, 2.

Relativity made a business decision. You now face a professional responsibility and preservation decision, and a client, a disciplinary authority, or a court may review the record you build now 2, 5.

Sources

  1. Relativity CEO Says 2028 Server Deadline Stands; Will Prioritize Partnering with Frontier Labs Over Legal AI Companies — LawNext, accessed October 2, 2026
  2. ABA Formal Opinion 477R: Securing Communication of Protected Client Information — American Bar Association, accessed October 2, 2026
  3. Embracing the Future of Legal Data in 2025 and Beyond — Relativity, accessed October 2, 2026
  4. Putting A Nail In the Coffin of Its On-Prem Product, Relativity Sets 2028 Deadline for All New Cases to Move to the Cloud — LawSites (LawNext), accessed October 2, 2026
  5. Fed. R. Civ. P. 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions (Rule 37(e)) — Cornell Legal Information Institute (Federal Rules of Civil Procedure), accessed October 2, 2026
  6. Fed. R. Civ. P. 26. Duty to Disclose; General Provisions Governing Discovery (Rule 26(b)(1)) — Cornell Legal Information Institute (Federal Rules of Civil Procedure), accessed October 2, 2026
  7. Da Silva Moore v. Publicis Groupe & MSL Group, No. 11 Civ. 1279 (S.D.N.Y. Feb. 24, 2012) (Peck, M.J.) – Opinion and Order — Justia (U.S. District Court, S.D.N.Y.), accessed October 2, 2026
  8. Rio Tinto PLC v. Vale S.A., 306 F.R.D. 125 (S.D.N.Y. 2015) (Opinion & Order, Peck, M.J.) — CourtListener (U.S. District Court, S.D.N.Y.), accessed October 2, 2026
  9. Hyles v. City of New York, No. 10 Civ. 3119 (S.D.N.Y. Aug. 1, 2016) (Opinion & Order, Peck, M.J.) — Justia (U.S. District Court, S.D.N.Y.), accessed October 2, 2026

The Digital Docket

A weekly synthesis of legal innovation, ethics, and technology delivered to your inbox.

No spam. Unsubscribe at any time.

Continuing the Argument