Skip to content

Systems and records

Archive retention cost scenarios: keep the whole archive or complete cases?

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Compare keeping a whole archive with preserving complete cases by first fixing the legal floor, meaning holds, retention duties and contracts, which every scenario must meet. Above that floor, preserve complete cases when access is ending soon and value sits in linked work from start to finish; keep the whole archive when a hold covers it or you cannot yet tell which cases matter. Rate cost, risk and future utility side by side.

System export

Archive retention cost

This page covers archive retention cost scenarios: keep the whole archive or complete cases.Illustrative

Key takeaways

  • Holds, retention duties and contracts set a floor that no preservation scenario may go below.
  • Above the floor, the choice is between keeping everything and keeping complete cases with their context.
  • A complete case links the starting request, every action, attachments and the verified outcome.
  • Keeping everything is not automatically the low-risk choice; over-retention carries security and privacy exposure.
  • The access deadline and how concentrated the archive's value is are the two assumptions that most often flip the decision.

How do you compare preserving a whole archive with preserving complete cases?

Fix the legal floor first, then compare scenarios only above it. The floor is everything a legal hold, a retention duty or a contract requires you to keep, and every scenario must include it. The real choice is what else to keep: the rest of the archive as it is, or only complete cases with the context needed to understand them.

Preserve complete cases when access is ending soon, the archive is large, and its value sits in linked units of work, such as a ticket with its messages and outcome or a job with its quote, dispatch and invoice. Keep the whole archive when a hold covers it, when you cannot yet tell which cases matter, or when the export of everything is cheap and the system is about to disappear anyway.

This guide is for owners and restructuring teams facing a shutdown date. It gives an illustrative worksheet with three scenarios, the inputs each needs and a worked case, and it shows where the decision needs a lawyer or records specialist rather than a spreadsheet.

What sets the floor that no scenario can go below?

Three sources set the floor: legal holds, retention duties and contracts. List each one with the record families it covers before comparing anything, and have counsel confirm the list.

Legal holds come first because losing held records has consequences no cost saving justifies. Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved in anticipation or conduct of litigation and is lost because a party failed to take reasonable steps to preserve it. If any hold touches the archive, the held records are kept whole, in a form that keeps their metadata, regardless of the scenario chosen for the rest.

Retention duties vary by record type and jurisdiction. The IRS, for example, says records supporting a federal return should be kept until the period of limitations runs out: generally three years, at least four years for employment tax records, seven years for claims involving worthless securities or bad debts, and six years if unreported income exceeds 25 percent of reported gross income. Industry regulators, state law and customer contracts add their own periods, so the floor is a list compiled for your company, not a single number.

What counts as a complete case, and how do you prove it can still be read?

A complete case is every record needed to follow one unit of work from the starting request to the verified outcome without going back to the source system. For a support desk it is the ticket, every message and internal note, attachments, status changes, the assignee history and the resolution. For field service it is the request, quote, dispatch, technician notes, parts used, invoice and any callback.

Proving the case can still be read matters as much as exporting it. The Library of Congress assesses digital formats for long-term preservation on factors including disclosure, adoption, transparency, self-documentation and external dependencies. An export in an open, documented format that carries its own field definitions scores well; a vendor backup that only the retired software can open does not.

Use this readability proof before the source system goes away.

  • Export totals reconcile to the source system's own counts for each record type and year.
  • A sample of cases opens and reads end to end with ordinary tools, attachments included.
  • A short readme explains each field, status code and abbreviation, written by someone who used the system.
  • Links between records survive as stable IDs, so a message still points to its ticket and an invoice to its job.
  • File formats avoid dependencies on the retired software, or a viewer and its license are preserved with the export.

The cost, risk and future utility worksheet

Rate each line for each scenario as low, medium or high, and write the evidence behind each rating in a notes column of your own copy. The ratings here are illustrative defaults for a mid-sized archive with a near deadline; your inputs replace them.

Decision rule: drop any scenario that fails the floor. Among the rest, prefer the one with no high risk rating; if more than one remains, prefer the one with the better future utility rating unless its cost rating is two steps worse.

The cost, risk and future utility worksheet
Worksheet lineA: whole archive kept in the live systemB: whole archive exported to cold storageC: complete cases plus the floor set
Ongoing run costHigh: licenses, hosting and an administrator continueLow to medium: storage only, rises with volumeLow: smaller volume in open formats
Up-front effort before the deadlineLowMedium: full export and reconciliationMedium to high: case selection, linking and readme
Retrieval effort when someone needs a recordLow while the system runsMedium to high: restore, then search raw exportsLow to medium: cases are already assembled
Risk of missing the legal floorLowLowMedium unless the floor set is defined first
Over-retention and breach exposureHigh: everything stays reachableMediumLower: less personal data kept
Risk the data becomes unreadableRises as the software agesHigh if exports are proprietaryLow with open formats and a readme
Future utility for analysis or licensingMedium: complete but tied to old softwareMedium: complete but context is scatteredHigh for the chosen case families; none for the rest
ReversibilityReversible until the system is retiredReversible for the storage periodIrreversible for records not selected once the source is gone

The input dictionary for each scenario

Each rating should rest on a measured input with an owner. Where an input is unknown, write a range and the date it will be known; do not guess a single number.

The input dictionary for each scenario
InputHow to measure itOwnerIf unknown
Access deadlineContract end, notice period, administrator departure dateIT ownerUse the earliest plausible date
Volume by record familyRecord counts and storage size by year, attachments separatelyIT ownerRange from the admin console or a sample
Floor setHolds, retention periods and contract duties by record familyCounselTreat the family as fully held
Case families with likely future useWhich work types are repeated, documented and linked to outcomesOperations leadKeep the whole family until decided
Export capabilityNative export, API, or vendor service; what it includesIT ownerTest one case before committing
Expert contextPeople who can explain fields and codes, and until whenOperations leadSchedule the readme interview first
Rights exceptionsClient-owned files, contract limits, notice gapsCounselExclude from case selection pending review

Which cost lines are easy to miss?

Four cost lines are routinely left out, and each can reverse an apparently obvious answer. The first is minimum storage commitments. Cold storage tiers are cheap per unit but carry terms; Amazon S3 Glacier Deep Archive, for example, has a 180-day minimum storage duration, and the S3 documentation lists its retrieval times in hours rather than seconds. A plan that moves data to cold storage and then deletes most of it within a few months pays for storage it did not use.

The second is retrieval. Restoring a whole raw export to answer one question takes time and someone who knows where to look, and that cost recurs every time a record is needed. Assembled cases are slower to build and faster to use.

The third is people. The administrator and the experienced users who can explain status codes and custom fields are often leaving at the same time as the system. Their hours before the deadline are the scarcest input in every scenario.

The fourth is software dependencies. If the export only opens in the retired product, keeping a working copy of that software, a license and a machine to run it is part of the archive's cost for as long as the archive is kept.

Is keeping everything the low-risk choice?

No. Keeping everything lowers the risk of missing a record you later need and raises the risk of holding data you should not. Both risks belong in the worksheet.

The FTC's Start with Security guide tells businesses to keep sensitive data only as long as they have a business reason to have it and to dispose of it properly once that need is over. For personal data about people in the European Union, GDPR Article 5 requires data to be limited to what is necessary and kept in identifiable form no longer than necessary for its purposes, with narrow allowances for archiving, research and statistics under safeguards.

This is why scenario C keeps the floor set whole and selects complete cases above it for a stated purpose, rather than keeping an undifferentiated archive indefinitely. If the stated purpose is future analysis or licensing, write that purpose down and have counsel confirm it is consistent with the notices and contracts that apply.

Worked scenario (illustrative): a help desk and dispatch system with sixty days of access left

This example is illustrative. A commercial HVAC services company with about 200 employees is replacing its help desk and dispatch platform, and the vendor contract ends in 60 days. The system holds nine years of history: about 310,000 service tickets, 1.4 million messages and notes, and roughly 2 terabytes of attachments, mostly photos and PDFs.

The floor: counsel confirms no active holds. Invoices and payroll-related records already live in the accounting system, so the help desk floor set is limited to warranty claims from the last six years, about 9 percent of tickets.

Case families: preventive maintenance visits and emergency repairs make up about 70 percent of tickets and link cleanly to outcomes and callbacks. Internal IT requests and spam make up most of the rest and have no future use.

Ratings: scenario A is dropped because licenses cannot be extended past the contract. Scenario B is feasible but the native export is a set of flat files without message-to-ticket links, so readability rates high risk. Scenario C keeps the warranty floor set whole, assembles complete cases for the two main families with a field readme written with the dispatch lead before her planned departure, and excludes the rest. The team estimates 120 to 180 hours of effort and chooses C, with a full raw export kept for 12 months as a fallback while the cases are checked.

Would a later deadline or scattered case families change the choice?

Two assumptions flip the choice most often: the access deadline and how concentrated the archive's value is. Test both before deciding. If the deadline moves from 60 days to a year, scenario A may become reasonable for a transition period. If useful cases are spread across many small families rather than two large ones, the effort of scenario C grows and scenario B with a readme may win.

Show uncertainty as ranges on the worksheet, such as 120 to 180 hours or 60 to 75 percent of tickets in the main families, and note which end each rating used. A third assumption, whether any hold applies, is binary: if counsel cannot confirm there is none by the deadline, keep the affected records whole and revisit later.

Hand the decision to specialists when the archive includes health, financial or children's records, when a regulator sets the retention period, or when the export cannot be reconciled to the source counts. Those are records management and legal questions, not cost questions.

What preserved complete cases can support later

Complete cases with a readme are the form of archive most likely to stay useful: for audits, for training new staff, for analysis and, when rights allow, for licensing. Raw exports without context tend to become storage that nobody can interpret.

SourceX licenses business data directly from companies, and preserved cases that link a request to its outcome are the record family that review looks at first. Large preserved archives can stay in the company's own storage or ship on encrypted drives, so keeping them under your control does not rule out a later licensing review. A short assessment of the company, with no upload, is where that starts.

Frequently asked questions

Is it cheaper to keep the whole archive or only selected records?

Keeping selected complete cases usually costs less to store and retrieve but more to prepare before the deadline. Keeping everything in cold storage is cheaper to set up but can be expensive to search and read later. Compare both on the same worksheet, including people's time and software dependencies.

What is a complete case in an archive?

It is the full set of linked records that shows one unit of work from request to outcome, such as a ticket with its messages, attachments, status history and resolution. A complete case can be understood without the original system. Single messages or rows without their links are not complete cases.

Can we delete records that are not part of the selected cases?

Only after counsel confirms that no hold, retention duty or contract requires them. Many teams keep a full raw export for a short fallback period while the selected cases are checked. Record the deletion decision and who approved it.

How do we prove an exported archive is still usable?

Reconcile export totals to the source system's counts, open a sample of cases end to end with ordinary tools, and write a readme that explains fields and codes. Check that links between records survive and that formats do not depend on the retired software.

What happens if the shutdown date arrives before preservation is finished?

Prioritize the floor set first, then the case families with the clearest future use, and take a full raw export as a safety net. Ask the vendor about a short extension or a read-only period, and capture expert context from departing staff before anything else.

Sources

  • The IRS says to keep records until the period of limitations runs: generally three years, at least four years for employment tax records, seven years for worthless securities or bad debt claims, and six years when income is underreported by more than 25 percent. Source
  • Federal Rule of Civil Procedure 37(e) addresses electronically stored information that should have been preserved for litigation and is lost because a party failed to take reasonable steps to preserve it. Source
  • The Library of Congress evaluates digital formats for long-term sustainability on disclosure, adoption, transparency, self-documentation, external dependencies, impact of patents and technical protection mechanisms. Source
  • Amazon S3 documentation lists a 180-day minimum storage duration for S3 Glacier Deep Archive and retrieval times measured in hours. Source
  • The FTC's Start with Security guide advises keeping sensitive data only as long as there is a business reason and disposing of it properly once that need ends. Source
  • GDPR Article 5 requires personal data to be limited to what is necessary and kept in identifiable form no longer than necessary, with allowances for archiving, research and statistics under safeguards. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies