Support & operations · Practice guide

Check exported records are usable by the next team

Illustrative situation

A departing software supplier provides a data export that opens successfully but omits important relationships and uses undocumented identifiers. An export that opens can still be unusable if its references and relationships are unexplained. Agree what the receiving process needs, then inspect a representative sample with the responsible data owners.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

What this means for your practice

Define export acceptance around the organisation's actual recovery or migration needs. Verify structure and meaning using authorised test data and the relevant data owners.

An example to discuss with your team

Import a representative fictional export into a test destination and check relationships, missing values and error reporting.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

How to review the arrangement

Ask the incoming team to load a fictional export into a test destination. Can they connect related records, understand missing values and identify rejected rows? Obtain the field and reference explanations needed for that task. Acceptance should reflect usable information rather than the mere existence of a downloadable file.

Test the meaning of the exported information

Choose a sample representing the records and relationships the receiving process needs. Include an attachment, a missing optional detail and related entries that must remain connected. Use appropriate fictional or authorised test information, with the relevant data owners deciding the checks.

Ask the receiving team to explain the file without relying on the old supplier's screen. Column names, record references and date formats need enough documentation for the intended use. A matching number of rows cannot establish that every relationship or value has been interpreted correctly. Follow a few complete examples into the test destination and review anything rejected or unclear. Agree how corrections will be supplied and checked before the final transfer. The useful acceptance question is whether the next team can use the information for the agreed purpose, not simply whether an export button exists or a spreadsheet opens without an error.

How to check the result

Check how much of the required export the receiving team can understand, connect and account for, with remaining gaps clearly recorded.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.