How to migrate an audit schedule from a spreadsheet: a data guide
How to migrate an audit schedule from a spreadsheet to scheduling software: which data to extract, how to map and clean it, and what to check before going live.
Key takeaways
- A migration is mostly data: auditors, competences, availability and audits.
- Competence and validity dates are the most important and messiest data.
- Write rules down in plain language before configuring anything.
- Run old and new side by side on the same period before switching.
To migrate an audit schedule from a spreadsheet, extract four data sets (auditors, competences with validity dates, availability and audits with windows), map each column to the new system's fields, clean duplicates and gaps, write your rules in plain language, then run the new system on the same period and compare before switching over.
The four data sets you need
| Data set | Key fields | Common problems |
|---|---|---|
| Auditors | ID, name, home base, internal or external, day rate | Duplicates, missing locations |
| Competences | Auditor, standard, technical area, role, valid from and to | Free-text codes, no expiry dates |
| Availability | Leave, training, part-time patterns | Held in personal calendars |
| Audits | Client, site, standards, codes, duration, window | Windows missing, only target dates |
Most bodies find the audit and auditor lists straightforward. Competence data is where the work is, because it's often held in several places in inconsistent formats.
Mapping and cleaning
- Standardise codesConvert free-text technical areas to one list, such as IAF codes or scheme categories.
- Add validity datesRecord start and expiry for every competence and qualification.
- Split rolesSeparate lead, auditor, technical expert, trainee and observer.
- De-duplicateMerge auditors or clients that appear under several spellings.
- Fill windowsReplace single target dates with earliest and latest dates.
- Flag gapsList what's missing rather than guessing; the system can surface it later.
A field-mapping example
| Spreadsheet column | System field | Clean-up needed |
|---|---|---|
| ‘Name’ | Auditor ID + display name | Create IDs; merge duplicate spellings |
| ‘Codes’ (free text) | Technical area list | Map ‘construction’ and ‘IAF28’ to IAF 28 |
| ‘Lead?’ | Role per standard | Split into roles for each standard |
| ‘Expiry’ (sometimes) | Valid to | Fill gaps; flag unknowns |
| ‘Due’ | Window start and end | Derive from certification decision date |
| ‘Notes’ | Rules or conflicts | Turn recurring notes into explicit rules |
The notes column is often the most valuable. It hides rules and conflicts that were never written anywhere else, such as “not Tom, previous consultancy”.
Write the rules down
Before configuring any system, write your scheduling rules as plain sentences: “No auditor audits the same client more than three consecutive years.” “Internal auditors are preferred over contractors when qualified.” “No more than 150 km one way without an overnight stay.”
This exercise often reveals rules that only one planner knew. It is also the fastest way to configure scheduling software correctly, and it becomes useful evidence for assessors. See ISO/IEC 17021 scheduling requirements for the rules the standard implies.
Side by side before switching
- Week 1Extract and cleanFour data sets exported and standardised.
- Week 2Configure and runRules configured; one or two months allocated by the new system.
- Week 3ComparePlanners review the new plan against the real one, audit by audit.
- Weeks 4+PilotOne division goes live while the spreadsheet stays as a fallback.
This mirrors the path most customers take: a two-week demo on their data, then scoping and an eight-week pilot. See how to run a proof of concept.
Pitfalls
MythWe need perfect data before we start.
RealityStart with what you have; the system will show where gaps matter.
MythWe can switch everyone over in one go.
RealityA pilot with one division builds trust and catches edge cases safely.
MythOnce migrated, the spreadsheet can be deleted.
RealityKeep it read-only for a few months as a reference.
ScheduleAI is audit scheduling software built for testing, inspection and certification (TIC) organisations, with a planner approving every plan.
How long does migration take?
Two to four weeks for the data work, then a pilot of around eight weeks.
Who should own the migration?
A senior planner for the rules and data meaning, with a data contact to produce the extracts.
ScheduleAI imports auditors, competences, availability and audits from a spreadsheet or ERP extract, flags gaps such as missing expiry dates, and runs side by side with your real plan before you switch.
Book a demo Estimate your savingsQuestions
How do you migrate an audit schedule from a spreadsheet?
Extract auditors, competences, availability and audits, map and clean them, write your rules down, then run the new system alongside the old one before switching.
What's the hardest data to migrate?
Competence records, especially technical areas and expiry dates.
Do we need clean data first?
No. Start with what you have; the new system highlights the gaps that matter.
Should we switch everyone at once?
Pilot with one division first, keeping the spreadsheet as a fallback.