Start a Legacy EHR Data Archival and Decommissioning Service

1. 1

   Understand why the niche exists and never empties

   Retention law is the engine: state rules commonly require 5 to 10 years of adult records (far longer for minors, and hospital rules in some states stretch to 20 years or more), HIPAA adds six years on compliance documentation, and malpractice exposure makes conservative counsel keep everything. Meanwhile the retired system still bills license, support, and infrastructure fees, often six figures a year at hospital scale. Every EHR migration ever completed created one of these stranded systems; consolidation keeps minting more.

2. 2

   Learn the archival craft as distinct from migration

   Migration moves the active clinical subset into the new EHR; archival handles everything else: full extraction from the legacy database (discrete data, documents, images, audit trails), transformation into durable formats (C-CDA, PDF renditions, indexed databases), validation against record counts, and a searchable archive clinicians and release-of-information staff can actually use. Release-of-information requests and legal holds against archived data are the workflows your product must serve on day one.

3. 3

   Choose your delivery model

   Three lanes: pure consulting (you run decommissioning projects using the client's chosen archive platform), partner or white-label (you deliver projects on an established archive vendor's platform for a margin), or eventually your own hosted archive (highest recurring revenue, highest security burden: encryption, access controls, audit logging, breach insurance, SOC 2 expectations, and a signed BAA on every engagement because this is all PHI). Start in the first two lanes; earn your way to the third.

4. 4

   Package the decommissioning project

   A standard engagement: inventory the legacy system and its data types, map retention obligations by record class and state, extract and validate, stand up the archive with role-based access, document the destruction or preservation decisions, and formally terminate the old vendor contract. Project fees commonly run from tens of thousands for a single-practice system to six figures for hospital platforms, with hosted-archive subscriptions continuing for the retention life of the data, which is measured in decades.

5. 5

   Sell against a number the CFO already hates

   Your pitch is arithmetic: current annual legacy system cost versus one-time decommissioning plus a far smaller archive subscription. Target organizations mid-migration (archival should be planned alongside go-live, and rarely is), recently merged systems standardizing platforms, and anyone still running a sunsetted product the vendor has stopped patching, which is also a security time bomb worth naming.

6. 6

   Build the referral flywheel

   Implementation consultancies (the sibling card in this library covers that business) constantly finish migrations and leave the legacy question unanswered; become the partner they hand it to. EHR vendors' sales teams, healthcare attorneys advising on retention, and HIM associations round out a referral network that can keep a small firm booked without cold outreach.

Do not take our word for the money. Put your own numbers in and see what this idea has to earn before it works. Free, instant, no account needed.

Best for: EHR analysts and health IT people who like databases, compliance, and unglamorous recurring money

Not for: Anyone who dislikes databases, compliance, and unglamorous recurring work, since that is the whole business. It is also not for people who will handle PHI without a BAA and strong security, because retention data is all protected health information. Retention rules vary by state; this is not legal advice.