Insights · Government IT hiring · 5 minute read

How to Staff a Government Records Migration

Staff a government records migration so agency employees can still find, open, and verify the records they rely on. Start with a retrieval task and use it to define the roles and the evidence needed to accept the move.

By Vitaver Staffing ·

This guide draws on the Vitaver Playbook’s Mission First principle. Define what agency staff must be able to verify before assigning the migration work.

Start with a record someone must be able to find

When an agency moves records to a new platform, a useful acceptance test starts with a real staff task. Imagine a county office that must retrieve a permit by its original number, open all its attachments, and determine which version was approved. The deciding question is whether authorized staff can still perform that task after the migration, using the identifiers and access rules the office relies on. Establish the answer before estimating staffing or committing to a cutover.

The U.S. National Archives’ Universal Electronic Records Management Requirements give federal agencies a starting point for defining electronic records capabilities. Its electronic records design guidance discusses preserving the link between records and metadata through migration. These are useful technical references. Have the agency records officer confirm the local requirements, including which records enter the project and who may see them.

Staff the work around four decisions

If the agency has a data engineer who knows the source system, the first staffing need might be an analyst who can put the records office’s expectations into a testable mapping. If the mapping is agreed but the extract and rerun are unreliable, engineering is the first priority. A small team can combine delivery roles, provided the person who accepts the result can independently inspect the evidence.

Reconcile the data and test the staff task separately

For an illustrative pilot, choose one record series with common items and exceptions. Record the source count and the set of source identifiers. Account for each item as migrated, deliberately excluded under an approved rule, or unresolved. Compare file counts and parent-child relationships for documents with attachments. For files intended to remain byte-for-byte identical, compare checksums. Where the process deliberately changes a format, record the transformation and verify that the resulting file can be opened and interpreted as intended.

Then ask an authorized user to search by old identifier, browse alternate versions, and open the expected attachment. Ask a second test user with different permissions to repeat the parts they are authorized to perform. For example, a run can produce the expected number of files and still attach an inspection photo to the wrong permit. The handoff should include both sets of results so the acceptance owner can see exactly what was verified.

Use a small, comparable interview exercise

Give candidates for the same role the same fictional file manifest, a short mapping, and a sample search result. Include a duplicate identifier and an attachment listed against the wrong record. Ask them to identify what they can prove, which source they would check next, and how they would rerun the check. Evaluate reasoning, traceability, and whether the candidate recognizes decisions that belong to the agency. Use synthetic records and assess any formal access eligibility through the authorized process.

Before opening the requisition, schedule the pilot review with the records owner and system owner. State the approved work environment, access lead time, and any on-site or cutover hours. Ask the person taking over the system to rerun one reconciliation and repeat one retrieval test using the handoff alone. That gives the agency evidence that it can operate the migrated records after the engagement ends.

← All Insights