Use caseRecords management software

Customers upgraded to the new release

Two years after launch, most of Corvane's 140 counties still run version 8. Each upgrade is custom, and no county can stop issuing permits.

Every county's data is inventoried before anything movesEach move is rehearsed on the county's real recordsVersion 8 stays live until the county signs

The operations engineWhat Westbrook holds

1.9 million records over 41 types, 11 custom fields, and 214 records whose file is already missing on the old share.

source · Westbrook database and file share, read in place
Actions on this county's move
The reconciliation verdict

Missing before the move · the county records it

01

Where it stalls today

The short version

Two years ago, Corvane shipped version 10 of its records management software for local governments. Version 10 runs on a new document repository. Version 8 keeps its documents in a database and a file share, on servers in each county's building. Corvane still maintains both, and every upgrade is run by whichever consultant is free. The new release is ready; the installed base is not moving.

Corvane turns the move into a program. Every county's version 8 is inventoried in place, one versioned mapping carries every county with its own fields on top, and each county gets a test run on its real records, reconciled document by document. The county's key users check their own records, and the county signs before version 8 is switched off.

Installed base · todayOperations engine
Stuck at the first stage. Most counties never leave version 8, because each upgrade starts from a blank page.
Westbrook County · version 10 moveOperations engine
The same county, as a program. Rehearsed weeks ahead, switched in one weekend, closed by the county's own signature.

One rule runs the whole program: the county's data is known before the plan is written, every move is rehearsed and reconciled, and the switch happens only on the county's signature. The three acts read the base, rehearse Westbrook, then close its move.

02

The installed base

Ingrid Solberg, Corvane's migration lead, starts with what is actually out there in 140 county buildings.

Step 1Discovery

Every county's version 8 is read in place

With read-only access each county grants, the operations engine analyzes the version 8 database and file share where they sit. It counts records per type, measures volumes, lists the custom fields each county added, and finds files the database references but the share does not hold.

SQL databaseFile shareCustom fields
Discovery · Westbrook CountyOperations engine
Nothing moves during the scan. The report becomes the work list.
The surprises come out before the planMissing files and odd formats are found while version 8 runs, months before any county's window.
Step 2Planning

Counties are grouped into waves

Tomasz Nowak, VP of product, groups counties into waves with Ingrid, on the volumes the inventory measured. Wave 1 takes six small counties with few custom fields, to prove the method. Carrick, with 27 custom fields, gets a wave of its own. No wave lands on a county's fiscal year-end or on local elections.

Wave plan · version 10 programOperations engine
Migration is structured by entity and by wave, here one county per entity.
Each county agrees on its own windowThe plan is built on measured volumes and moves when a county asks.
Step 3Mapping

One mapping for every county, extended per county

Version 8 and version 10 do not store a permit application the same way. Ingrid writes the standard mapping once: old record types to new document types, old status codes to workflow states, old references kept as a searchable property. Each county's custom fields go on top. Every version of the mapping is kept.

Mapping 4.2 · WestbrookOperations engine
Rules are versioned: each run says which version of which rule it used.
Look back at your last ten upgrades: how many were rebuilt from scratch by the consultant on duty, with nothing the next one could reuse?
The tenth county costs less than the firstThe standard mapping is written once. Each county adds its own fields and nothing else.
03

The rehearsal

Four weeks before its window, Westbrook County gets a test run on its real data while version 8 keeps running.

Step 4Test run

Westbrook's records move into version 10, unseen by users

Ingrid runs mapping 4.2 on a sample first, then on all of Westbrook. The operations engine extracts, transforms and loads the records into Westbrook's new space on version 10, which no user sees yet. It runs at night to spare the county's servers, pauses during business hours and resumes from where it stopped.

Run R-WB-01 · WestbrookOperations engine
An interruption resumes from its checkpoint. Nothing starts from zero, nothing is duplicated.
The county keeps workingPermits are issued on version 8 all week. The test run happens next to it.
Step 5Reconciliation

What moved is checked document by document

The reconciliation report compares what was expected with what arrived, one line per record, with the version 8 and version 10 identifiers side by side. Westbrook's report names 214 records whose file was already missing on the old share, and 38 old fax scans converted for the new version.

Reconciliation R-WB-01Operations engine
A record that failed a control is listed and can be handled.
The old gaps are named before the moveThe 24 missing files were lost years ago. The report says so, in the county's own records.
Step 6Viewer

The key user checks the records she knows

Rosa Delgado leads permit administration at Westbrook. She picks 40 records herself: a recent application, a 1998 appeal, a protected tree permit, a file with large plans. She opens each one in version 10, in the browser, compares it with version 8 on her second screen and ticks it off.

Application PRJ-2019-0412 · Site planViewer
Plans and old scans open in the browser, with no download.
The county's own expert says yesRosa checks what only she would notice. Her one finding goes into mapping 4.3 before the window.
04

The cutover

The test run is clean. Westbrook moves in its agreed window, and the program turns to the next wave.

Step 7Migration

Only the changes since the test run move

On Friday, September 10 at 5:00 p.m., Corvane sets version 8 to read-only at Westbrook. The operations engine synchronizes only what changed since the test run, with mapping 4.3, then reconciles again. Daniel Hughes, Westbrook's IT manager, opens version 10 to users on Saturday afternoon.

Cutover · WestbrookOperations engine
The final reconciliation decides whether users switch.
The weekend carries thousands, not millionsThe bulk moved weeks ago. The window holds only what changed, so it fits in a weekend.
Step 8Workflow

The county signs, then version 8 is retired

Westbrook's staff work in version 10 from Monday. Version 8 stays intact and can take users back. After two weeks with no blocking issue, Daniel approves the acceptance task in Corvane's customer process. Only then are the old servers retired with the county's IT.

Final reconciliation archivedKey-user checklist 40 of 40Two weeks live, no blocking issue
Acceptance · Westbrook CountyCase management
The approval is a workflow task with its owner and its date.
The county decides when it is doneCorvane does not retire an installation that has not been accepted.
Step 9Reporting

The whole program on one board

Tomasz follows the program across every wave: counties accepted, counties in test run, anomalies waiting on a county, and the next windows. Each wave's trace exports as it is. He uses it to decide when version 8 can stop receiving updates, a date counties hear well in advance.

Program boardOperations engine
Every wave leaves its trace: what left, what arrived, what was set aside and why.
One product to maintain, on a date you can sayThe board shows when version 8 can end. Figures on the dashboard are sample values.
05

The possible results

Each of Westbrook's 1.9 million records gets one of three results, and each result sends someone to do something different.

Match

The record arrived as expected

Count, file and properties line up between version 8 and version 10.

Next: the next batch, or the next step, can start.
Gap explained

Missing before the move

The file was already absent on the old share. The report says so.

Next: the county looks for it, or records the gap in its own files.
Mismatch

Something did not arrive right

A record failed a control on the way. It is listed with both identifiers.

Next: only the affected batch reruns, once the cause is fixed.
What the migration does not decide

It switches no county over. It retires no server. It drops no field. Across the nine steps on this page, the switch and the acceptance are the county's, made by named people on their own records.

The operations engine reads, transforms, loads and reconciles. The control is in the sequence: inventory, test run, key-user check, cutover, signature.

06

Time back

Westbrook County alone produced these counts. Another installed base, with other versions and other customers, will produce its own.

1 mappingshared by every county, with each one's custom fields as an extension.
40 recordschecked by the county's key user herself, before the window.
6,412 recordsmoved during the cutover weekend. The other 1.9 million had moved weeks earlier.

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 three principles behind those numbers

Known before movedPlanningEach old installation is read in place. The plan is built on what it really holds.
Rehearsed on real dataProcess reliabilityEvery county gets a test run and a reconciliation before its window.
Signed by the customerA person decidesThe old version stays live until the county approves the move.
07

Who it is for

An installed base moves when the vendor's head of product, its migration lead and each customer's IT manager are ready to sign. This is what moves each of them:

Product leadership

Heads of product

You maintain two products because customers will not move.

  • The installed base measured, county by county.
  • Waves planned on real volumes.
  • A date for the end of the old version.
  • One board across every wave.
CIO and architecture

Migration leads and architects

Every upgrade is rebuilt by hand by whoever is free.

  • Reads SQL databases and file shares in place.
  • One versioned mapping, extended per customer.
  • Resumes after an interruption, no duplicates.
  • A reconciliation line for every record.
Your customers

Customer IT managers

You cannot lose a record, and you cannot stop service for a week.

  • Your old version runs during the test run.
  • Your key users check your own records.
  • Old gaps named before the move.
  • Nothing is retired before you sign.

Start small

With one small customer and the inventory. Read their old installation in place and compare what it really holds with what your upgrade guide assumes.

Then write the standard mapping on that customer, and run it on a sample of their records before any window is set.

See it live

See it on your own installed base

Share the data model of your old and new versions and one customer's volumes. We will plan a first wave with you and run a test on real data.

The screens on this page are drawn to show one step at a time, with example data. Corvane, the counties and the people named are fictional.

Uxopian Software helps software companies move their customers' content to their new platforms, in waves, without stopping the service those customers run.