Use caseApplication retirement

Application retired, records kept

An unsupported AP server stays on, license and all, for eight years of invoices auditors may ask for. Two people still know how to search it.

Each database row becomes a record with its fileRetention and legal holds are set on arrivalCompliance tests the records before anything is switched off

The operations engineInventory, AP application

5.7 million business rows linked to their files. 16,789 invoice rows have no file, and 3,402 files have no row.

source · discovery scan, database and file store
Actions on this campaign
The verdict on the batch

Some items need a person · each one is named, with its reason

01

Why it drags today

The whole thing in one move

In an application like this one, an invoice scan means nothing without its database row: the supplier, the amount, the fiscal year that make it findable. Export the files alone and the auditors get millions of scans with no way in. Keep the application, and you pay for a server to hold an archive.

Row and file travel together and become one record of the repository, with its properties, its retention rule and any legal hold. Compliance tests the records, signs, and only then is the application switched off.

AP application · todayAdmin console
Paid for, barely used. The application stays on for one reason: the invoices nobody else can find.
Retired application: APRepository
An archive with a way in. Each class keeps its retention, and the supplier under hold is marked where an auditor will see it.

Nothing is switched off until the last link holds: map the rows and the files, design the records and their retention, move and reconcile year by year, then let compliance sign the shutdown. Henrik and Omar map, Claire tests, and Sofia answers the IRS long after the servers are gone.

02

What the application holds

A document here makes sense only with its database row, so the team maps both before deciding anything else.

Step 1Discovery

Inventory the tables and the file store

Henrik Vos owns the old application. He connects the operations engine to its SQL database and to the store where it kept its scanned files, through a connector set up for this application. The scan links each file to its row and reports the orphans on both sides.

Rows with no fileFiles with no rowLinks between tables
Source inventory, AP applicationOperations engine
Nothing moves during the scan. The report becomes the work list.
The archive is known before it movesThe team knows what the application holds, and which pieces were already missing inside it.
Step 2Repository

Design the records the repository will keep

Omar Bashir, the records manager, defines one record class per business object: supplier invoice, purchase order, payment proof, dispute file. Each record takes its properties from the database row, so an invoice is found by supplier, number, fiscal year and amount.

An EDI invoice that never had a file still becomes a record, with its data and no document. The link between an invoice and its purchase order is kept as a link between records.

Record class: supplier invoiceRepository
The repository stores records that do not all look alike: with a file, or with data only.
Records are found by what people knowThe auditors ask by supplier and year. The properties that answer that come straight from the old rows.
Step 3Retention

Attach a retention rule and carry the legal holds

Claire Russell, the compliance officer, sets the retention of each class with its trigger: invoices and payment proofs ten years after the end of their fiscal year, purchase orders five, dispute files ten after closure.

Two suppliers are under legal hold for an ongoing dispute. Their records get the hold on arrival. While it stands, the planned deletion is suspended, whatever the retention date says.

Retention scheduleRepository
The periods are the company's own schedule, set with its legal team.
The rules arrive with the recordsNobody keys the retention in again after the move. Each record lands with its period and any hold already on it.
03

Extraction and proof

The application is still running, read-only for finance, while the team moves everything, checks it, and hands compliance the result.

Step 4Extraction

Move rows and files together, year by year

Henrik runs one batch per fiscal year. For each record the operations engine reads the row, fetches its file, applies the class, the retention and the holds, loads the record and checks what arrived.

Batch: invoices, fiscal 2019Operations engine
Every row becomes a record, with its file or with its data only.
Each year is a batch the auditors can followThe fiscal year is how finance thinks. It is also how the proof is cut.
Step 5Reconciliation

Reconcile the records with the database

The reconciliation report compares each fiscal year with the database it came from: rows read, records loaded, files fetched, properties written. Every record has its own line, with the row key next to the new record identifier.

The 3,402 files that no row points to are listed apart, with their original path. Omar decides to keep them as unclassified records.

Reconciliation, all yearsOperations engine
The report exports as it is, and goes into the shutdown file.
The count matches the source, line by lineAn auditor can check any fiscal year against the database it came from, before the database is gone.
Step 6Compliance

Compliance tests retention and holds on real records

Claire picks twenty records across classes and years. For each one she checks the class, the retention end date and the hold where it should be. She opens an invoice of Brennan Packaging and sees LH-2024-03 on it.

Compliance sampleRepository
She leaves a note on each record she checks. The notes are her sign-off.
Imagine the IRS asks tomorrow for one supplier's invoices from 2018. Who on your team could answer without the old application?
Compliance signs on what it sawThe sign-off rests on twenty records she opened herself, each one carrying her note.
04

Switch-off, and the years after

The records are in place and tested. The application can go, and the people who need the records find them in the repository.

Step 7Closure

Sign the shutdown

Henrik prepares the shutdown file in the repository: the reconciliation report, the compliance sign-off, the decision on the orphan files and the date the servers go off. Claire signs it. The license is not renewed.

Shutdown fileRepository
The decision to switch off is a record too, with its evidence attached.
The shutdown has a file an auditor can readWhat moved, how it was checked and who signed. It is all in one place, next to the records.
Step 8Assistant

The auditor answers an IRS request

Sofia Marin, in finance audit, gets a request: every invoice from Kerrow Logistics for fiscal 2018. She asks the assistant in plain language. It returns a table of 214 records, names the record class it searched, and offers an Excel export.

She opens the disputed one in the viewer, in the browser, without downloading it.

Retired application: APAI console
Each row opens its record. The answer reads only what Sofia is allowed to see.
Nobody learns the old screensThe request is answered by the person who received it, with one question and one export.
Step 9Retention

The first records reach the end of their retention

In January 2027, the invoices of fiscal 2016 reach the end of their ten years. The retention rule starts a review workflow. Omar gets the list, sees that the held records are excluded, and approves the deletion.

The deletion is logged like every other action, so the trail shows what was destroyed, when and on whose decision.

Retention reviewRepository
Nobody deletes by hand. The rule starts the review, the records manager decides.
Kept as long as the rule says, and no longerThe records leave on schedule, the held ones stay, and the trail says who decided.
05

Where each file lands

Every fiscal year closes in one of three states. Only the first lets compliance test it and brings the shutdown date closer.

Reconciled

Every row is a record

Counts agree with the database, retention and holds are on every record.

What follows: compliance tests a sample and signs the year.
Exceptions listed

Some items need a person

A file with no row, a row with a value the rule rejects. Each one is listed with its reason.

What follows: the records manager decides, and only those items run again.
Batch held

Counts disagree with the database

Rows read and records loaded do not match for a table or a year.

What follows: the shutdown date waits until the cause is found and a person decides.
What the software does not decide

It switches off no server. It sets no retention period and lifts no legal hold. It deletes nothing on its own. Across the nine steps on this page, the shutdown and every deletion are signed by a named person.

The operations engine moves and reconciles, the repository applies the rules it was given. The periods and the holds belong to compliance, written once and applied to every record.

06

The payoff

These counts come from one AP application and its eight fiscal years. Yours will follow your own application and your retention schedule.

1 serverand its license switched off, once the records were signed by compliance.
0 retention dateskeyed in by hand after the move. Each record arrived with its rule.
1 exportto answer an IRS request, made by the person who received it.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

What makes these gains possible

Row and file togetherRecordsEach record carries the data that makes it findable, and its file when there is one.
Rules on arrivalRetentionPeriods and legal holds are set at load time and tested before the shutdown.
Proof before switch-offReconciliationEach fiscal year is reconciled with the database while the database still exists.
07

Built for

Switching off an application that holds records takes a yes from IT, from compliance and from the people who search the archive. Each yes rests on something different:

IT and architecture

CIOs and application owners

You pay every year for a server nobody uses, except to look up old invoices.

  • The application's database and files are read through a connector.
  • Each row and its file become one record.
  • Fiscal years move as separate batches.
  • The servers go off once compliance has signed.
Risk and compliance

Compliance and privacy officers

You are asked to approve a shutdown without seeing where the records went.

  • Retention is set per class, with its trigger.
  • Legal holds are on the records from the first day.
  • You test a sample and your checks are recorded.
  • Deletion follows a review workflow and is logged.
Finance and audit

Auditors and records managers

Two people know how to search the old system, and one of them is leaving.

  • Records are found by supplier, number, year and amount.
  • A plain-language question returns a table to export.
  • Documents open in the viewer, in the browser.
  • Search respects your rights.

Where to start

With one fiscal year. Map the tables and files of the application, design the record classes, and move one year as a pilot. One year is enough for compliance to judge the method.

The application keeps running read-only until compliance signs, so finance never loses access to its archive.

Ready to try

Name the application you keep for its archive

Tell us which system stays on only because of what it stores. We will map its tables and files with your team and draft the record classes and the retention schedule.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.