Microsoft Access migration in Newark, OH

Access Migration in Newark

Databases that hold the official record

Newark is a county seat, and county seats run on records. Permits, licensing, inspections and case files often sit in an Access database that one department built because the official software could not do what they needed. It works, it is relied on, and it is the only copy of something people have a legal interest in.

That raises the stakes on a migration in a specific way. The record has to be provably intact afterwards. Not approximately intact, provably, with counts and totals reconciled and the reconciliation written down.

The second Newark thread is contractors. The building activity in the county has grown companies past databases they built themselves, and those files now hold the job history the business is valued on.

What we would look at first in Newark

• Which records in the file somebody outside the organization has an interest in
• What the official software could not do, which is why this database exists
• How the record would be proven intact after a move, and who signs that off
• Whether anything in the file is the only copy of a legal or contractual record
• Who built it, who maintains it now, and what happens when they are unavailable

What Microsoft Access migration includes in Newark

• A free audit of every object, with what each one holds written down
• A blueprint approved before any data moves, including what gets archived
• A verified migration with record counts and totals reconciled on both sides, in writing
• A parallel run until the figures agree, so the official record is never in doubt
• Reports rebuilt so a new question does not need a developer
• The system, the data, the documentation and every login handed to you

OH-16 makes Newark a half-day trip, so we interview the people who actually use the database in person, where the undocumented rules come out.

How Access Migration works, step by step →