Records Migration Quality Assistant

HRS Talent Solutions; Bracknell; Remote; GBP 41,000 - 44,000; Full time

Job summary

HRS Talent Solutions is seeking a Records Migration Quality Assistant to perform post-import checks on migrated records in a remote, home-office setting. The role focuses on ensuring accuracy of migrated data without coding tasks.

You will compare source and destination entries, verify that links reach the correct files, record missing pages or mismatched fields, and report precise exceptions to the project team.

Qualifications

• Attention to detail and patience for data quality work.
• Ability to follow a defined set of migration checks.
• Comfort with online systems and project trackers.
• Ability to work remotely with minimal supervision.

Responsibilities

• Compare source and destination record identifiers and fields.
• Open imported document links to verify correct files.
• Record missing pages, blank fields or mismatched status accurately.
• Note when differences reflect approved mapping rules and report to team.
• Keep separate cases for different source records and ensure auditability.
• Mark checks complete only after the specified fields have been reviewed.

Job description

Records Migration Quality Assistant

Office Administration · Digital Records · Remote · Part-time or full-time
£29.50-£31.75 per hour

Moving records into a new online system can make them easier to find, but only if the imported entry still points to the correct person, document and history. This role performs basic checks on a defined group of migrated records after the technical import has been completed. You would compare assigned source and destination entries, note omissions and send exceptions to the team that can correct them. You would not design the migration, write code or decide to delete a source record.

Compare what is there

The employer may supply a checklist of fields such as a reference, date, document title and status. Open the permitted source record and the matching entry in the new system, then compare the specified details. An empty field may be a genuine missing value or a source record that never contained that information. Record which you observed rather than filling a gap with an assumption. If a document link opens the wrong file, flag the specific entry and the result you saw.

An imported record may also have a new system identifier. Use the mapping supplied by the project team instead of expecting old and new numbers to match. Where two possible destination records appear, leave the case for review. A quick merge or reassignment by an inexperienced checker can make the underlying data harder to recover. Your finding should give the responsible colleague enough context to investigate without copying unnecessary private details into a separate spreadsheet.

Checks you may be assigned

• Confirm that the listed source record has a corresponding destination entry.
• Compare the permitted identifiers and a small set of designated fields.
• Open an imported document link to verify it reaches the expected file.
• Record a missing page, blank field or mismatched status accurately.
• Note when an apparent difference reflects the approved mapping rule.
• Keep separate cases for different source records.
• Recheck a corrected item when the project team asks you to do so.
• Mark the check complete only after the specific fields have been reviewed.

Suppose the old system shows a customer request from April with two attachments, but the new entry has only one. You would verify the source and report the missing attachment reference. Do not upload your own copy into the new system unless the process explicitly assigns that action. If the project team later restores it, check that the link opens correctly and update the quality record. "Fixed" should describe a confirmed result, not a message saying someone will fix it.

This is remote office administration that indirectly supports customer service. A support colleague needs trustworthy records when answering a person's question. You will work with online systems from a private home office, following access controls and using only the project tracker for findings. Previous data migration experience is not necessary. The employer will teach the comparison rules and the limited set of fields assigned to you. Accuracy and patience are more useful than technical jargon.

The hourly range appears above. The client will confirm its actual full-time or part-time schedule. The work can be repetitive within a batch, so take care not to let one entry blur into another. A good result is a list of checked records and specific exceptions that a qualified colleague can act on, not a claim that every record in the whole system is perfect.

The project team may ask you to check a sample rather than every migrated item. Record which batch and entries you examined so your result is not mistaken for a complete audit. If you discover a recurring problem, such as links failing for several records of the same type, flag the pattern and the specific examples. Do not change the agreed sample or announce that all records are affected without evidence. That combination of precise examples and a clearly stated scope helps the technical team investigate efficiently.