
Check your tester export
Changing PAT software? Start with a representative tester export. A features list is useful, but your own file gives you something concrete to check.
Keep the original
Before trying a migration, keep a separate copy of the file your tester produced. Work on a copy so you can compare the imported records with the source.
Bring a representative job
Choose an export that reflects your normal work. If you test for several customers in one day, include a sample that shows how those records are separated. Use demonstration data or remove customer-identifying information before sending a file outside your authorised workflow.
Check more than the filename
An extension is only part of the picture. Devices and export layouts can contain different fields. Ask the supplier to check the actual file your tester exports before buying.
Review the imported rows
In PatConnect, supported files are processed into the workspace. Check customer and site details, Asset IDs, dates and result fields against your source before saving. Review the data even when an import appears to complete successfully.
Follow the job through
See the customer assignment, finished PDF and saved report. If you use mixed-customer files, ask to see Split Report. Write down the steps you currently do by hand and ask to see those during the demo.
Make the demo useful
Magic Save expands abbreviations, removes blank rows and duplicate Asset IDs, standardises text and prepares branded PDFs. Judge whether it suits your workflow with a sample in front of you. Compatibility depends on your tester export.
PatConnect team · 26 October 2026
£399 once. Lifetime licence. No subscription. Book a free demonstration through the Shop page.