Use caseArchives ahead of a migration

Scanned archive backlogs

A landlord holds eleven years of tenant scans: 412,000 files in date-named folders, no index. The new repository goes live in April.

The share is measured before anything movesEach document gets a type, a lease and a retention ruleThe archivist validates what the AI cannot place

Actions on this scan
Where each document goes

One point needs a person · the archivist confirms or corrects

The capture resultFive documents found

One file, one tenant file: a lease on pages 1 to 6, its appendix, a move-in inspection on pages 9 to 12, a letter, and one page to review.

source · 0031.tif, 14 pages
01

The friction

At a glance

412,000 files, and the only description any of them carries is a scan date. Each one holds several documents for several tenants. To find one lease, someone opens folders until it shows up. The archive is unreadable as a collection, and if it moves as it is, the new repository inherits the same search.

The archive gets read before it moves. The operations engine measures the share in place, the AI splits each scan, types each document and links it to its lease, and the archivist's rules set its retention. Every document reaches the new repository with a type, an owner and a rule, and a person has validated what the AI could not place.

Source inventoryOperations engine
Measured in place. The share as it really is, counted before a single file moves.
Lease BL-2012-08841Repository
Filed, at last. The Bennetts' documents under their lease, each with its rule and the scan it came from.

Taken one by one, these screens are routine. The project lives in their order: the backlog is measured in place, read on a sample, run at scale, and moved in waves that each leave a trace. Ryan and Claire take it a year at a time below, and so do the steps.

02

Measure before moving

Before any document is typed, the team learns what is on the share and agrees where each kind of document belongs.

Step 1Discovery

The share is inventoried in place

Ryan, the IT project lead, points the operations engine at the archive share. It lists every folder and file with its format, its page count and its date, and groups exact duplicates. Nothing on the share moves during the scan.

3,912 folders412,000 files1.4 million pages6 percent duplicates
Inventory reportOperations engine
The report becomes the work list for the rest of the project.
The project is sized on real volumesRyan plans the batches and the review effort on what the share actually holds. The estimate stops being a guess.
Step 2Settings

The archivist sets the types and the rules

Claire, the archivist, reviews a sample of 300 files with the rental team. They agree on 18 document types, each with its metadata and its retention rule from her records schedule. The target filing plan has one folder per building and one per lease.

Document typesAdmin console
Each type carries the metadata to read and the rule that follows it.
The rules are the archivist'sThe AI can suggest a retention period. The one that applies is the one Claire wrote, and every document says which.
Step 3Pilot

One year runs first, on a sample

Ryan runs the chain on the 2016 folders: 31,000 files. Claire checks 400 documents drawn at random and finds the type right on 391. Most of the nine errors are tenant letters typed as complaints. She adds a few of them as examples, and the rules are replayed on the year.

Pilot, 2016Capture
The archivist approves or corrects each value. Nothing moves without her sign-off.
Before you sign off: would you migrate eleven years of archives on a rule nobody had tried on one year first?
The full run starts on proven rulesThe errors are found on 400 documents. The rules that run on 412,000 files are the ones that passed, and each batch records which version it used.
03

Read the whole backlog

Eleven years in nightly batches. Each document needs a type, a lease and a date before it can be filed, and some need Claire.

Step 4AI check

Each scan is split into documents and typed

A single TIFF often holds a whole tenant file. The AI splits it document by document and classifies each one on the landlord's 18 types. Pages below every threshold are set aside for a person.

2013-02-18_lot1/0031.tifViewer
The source file stays in the metadata, so any document can be traced back to its scan.
One file becomes five findable documentsThe lease no longer hides behind an inspection report in a folder named by date. Each document stands on its own.
Step 5AI check

Each document is linked to a lease

The AI extracts tenant name, address and dates from each document. The operations engine reads the housing management database, which holds every lease since 2004, and associates the document with the one that matches. Documents with two candidate leases, or none, go to review.

Record linkingOperations engine
The housing database is the reference. It is read, never written to.
Documents find their owner on their contentThe link comes from what the document says, checked against the landlord's own records. The folder name plays no part.
Step 6Review

The archivist works the review queue

Claire's queue shows each document with what the AI proposes and why it stopped. For two leases with the same name in the same building, the date usually settles it. She asks the assistant which lease was open when the letter was written, checks the answer, and confirms.

Document 0219-1Capture
A proposal stays a proposal until the archivist confirms it.
The hard cases get a person and a leadClaire does not search the archive for clues. The AI brings the candidates and the date that decides, and she makes the call.
04

Every document gets a place

What is left out is approved, what moves goes in waves, and every wave leaves a trace.

Step 7Settings

The archivist approves what does not move

The engine proposes three kinds of documents to leave out: exact duplicates, documents past their retention rule, and blank pages. Claire reviews the lists by type and year. Two leases are under a court case, so a legal hold keeps their documents whatever their age.

Left out, 2013 to 2016Operations engine
Nothing is deleted on the share. What is left out is listed with its rule and its approver.
The new repository starts cleanDuplicates and expired documents stay behind, with the archivist's name on each list. The legal hold wins over the age of a document.
Step 8Migration

The documents move in waves

Each closed year moves to the new repository as one wave. On the way, each document is converted to PDF/A, filed under its building and lease, and its metadata and retention rule travel with it.

TypeLeaseDatesSource scanRetention rule
Wave 2016Operations engine
Source and target identifiers sit side by side on each document's line.
A failed document gets its own lineThe one line that failed its control can be handled and replayed alone. The wave does not start again.
Step 9Reporting

Each wave closes on its reconciliation

Every Monday Ryan shares progress with the steering committee. Each wave ends on a reconciliation report: what left the share, what arrived, what was set aside and why. The next wave starts only when that report is clean.

Backlog progressOperations engine
The report exports as it is, for the steering committee and for the auditors.
Go-live rests on evidenceThe committee does not take the migration on trust. Every wave has its count, and every gap has its reason.
05

The possible results

When a year closes, each of its documents is filed, waiting for Claire, or approved to stay behind on the share.

Filed

Type, lease and rule are clear

The type is above its threshold, one lease matches, the rule comes from the schedule.

What follows: the document moves with its year's wave.
To review

One point needs a person

A type below threshold, two candidate leases, or none. The queue says which, with the line it rests on.

What follows: the archivist confirms or corrects, and the document joins its wave.
Left out

It does not need to move

An exact duplicate, a document past its rule, a blank page. The engine lists it with the reason.

What follows: the archivist approves the list; a legal hold keeps what it covers.
What the AI leaves to you

It sets no retention period. It leaves nothing out on its own. It picks no lease between two candidates. Across the nine steps on this page, every document left out and every uncertain link is approved by the archivist, with her name on the list.

The AI splits, types and links. The rules are written by the archivist and tested on a sample, so they hold on eleven years of scans.

06

What it is worth

Measured on this landlord's backlog. An archive with other formats or other retention rules will land elsewhere.

0 filesmoved or changed on the share during the inventory and the pilot.
400 documentschecked by hand before the rules ran on 412,000 files.
1 lineper document in every wave, with its source and target side by side.

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

The rules behind the gains

Zero blind migrationsProductivityThe share is measured and the rules are tried on a sample before the full run.
Zero lost documentsProcess reliabilityEvery document has its line in a wave, and what failed can be replayed alone.
Decision supportA person decidesThe AI proposes types, links and retention. The archivist validates and approves what is left out.
07

Who it is for

The project lead, the archivist and the rental team are the ones who live with the result. Here is the difference for each of them.

IT and architecture

CIOs and project leads

Nobody can describe the archive you are asked to migrate.

  • The share is inventoried in place before you commit.
  • Rules are tried on one year, then run at scale.
  • A failed batch resumes where it stopped.
  • Each wave closes on a reconciliation report.
Administration

Archivists and records managers

The retention rules are yours, and nobody can apply them to unindexed scans.

  • Document types and rules are yours.
  • A review queue with the reason each document stopped.
  • Nothing is left out without your approval.
  • A legal hold keeps what it covers.
Business operations

Property managers

One lease, and folders to open until it shows up.

  • Documents filed by building and lease.
  • Each one carries its type and its dates.
  • The source scan stays traceable.
  • The few questions you get come with the candidates.

How to begin

With the inventory. Point the engine at the share and read the report: volumes, formats, duplicates. It changes nothing and sizes everything.

Then one year as a pilot, checked by your archivist on a sample, before the rules run on the rest.

Your move

Size your own backlog

Give us read access to a sample of your scanned archive. We will inventory it, run a pilot on one year and go through the results with your archivist.

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.