Switching driving school software: a checklist

Most driving schools stay on software they have outgrown because moving looks like it means losing five years of lesson history. It does not.

This is the order that works, the legal position on getting your data back, and where migrations go wrong.

What you are entitled to get back

Start here, because it changes the tone of the conversation with your current provider.

Your school is the data controller for your learners’ personal data. The software company is a processor — it holds and handles that data on your instruction, and nothing more. UK GDPR requires the contract between you to say so, and it requires a specific end-of-contract term.

The ICO’s wording on Article 28(3)(g) is that at the end of the contract the processor must “at the controller’s choice, delete or return to the controller all the personal data it has been processing for it” and “delete existing copies of the personal data unless UK law requires it to be stored”.

So “we do not do exports” is not a position a provider can hold. You are entitled to the data back, and you are entitled to have their copy deleted afterwards. Ask in writing and keep the reply.

Two practical notes. First, the request is about personal data — the learners, the lesson history, the payment records. A provider’s own analytics or internal reports are not covered. Second, deletion from live systems is not instant deletion from backups; the ICO accepts that backup copies age out on their normal cycle, provided they are not restored into use.

The seven steps

Step 1: ask for your data first

Before you cancel, before you sign anything else, email your provider and ask for a full export in CSV: learners, lesson history, payments, progress or skill records, and test results. Give a deadline and keep the thread.

Doing this first matters because a cancelled account is often a read-only account, and a read-only account is a slower conversation.

Step 2: check what actually arrived

Open every file. You are looking for four things:

• Learner email addresses. This is the key that ties every other file back to a person. If the export has names but no emails, ask again — matching 200 lesson-history rows on “J Smith” is a bad afternoon.
• Real dates, in a consistent format.
• Payment amounts with their dates, and some marker for what each payment was for.
• Anything showing what a learner still owes you. Outstanding balance is the thing schools most often discover is missing after they have cancelled.

Anything missing, go back now while the account is live.

Step 3: run one week in parallel

Set the new system up and book one real week in both, with real learners, real cancellations and one payment taken.

This is where the differences surface, and they are never the ones on the feature list. How does availability work when an instructor blocks out an afternoon? What happens to a package when a lesson is cancelled inside the notice window? Does the learner get told? A week in parallel finds all of that while you can still fall back on the old system.

Step 4: import learners first

The learner roster is the spine. Every history file references a learner, so it has to exist before the rest go in.

Passdesk’s importers take your CSV rather than a fixed template — you map your own column headings onto the fields on screen. Rows that cannot import are skipped with the reason shown, and you can download just the skipped rows, fix them and re-run. Re-running the same file does not duplicate what already came in.

Two rows that commonly get skipped and are worth expecting: a malformed email address, and an under-18 learner with no guardian details, which needs consent before the record can exist.

Step 5: import history

Roster in place, the rest go in any order — lesson history, payments, progress notes, skill ratings, test results. Each matches back to a learner by email.

Some specifics that save a re-run:

• Lesson history takes completed, cancelled and no-show lessons. Anything still scheduled belongs in the new diary as a booking, not as history.
• Payments import as already paid, so importing history never triggers a payment chase against someone who settled up two years ago.
• Skill ratings update in place on a re-import rather than stacking duplicates, so a corrected file is safe to run twice.
• Test results number themselves in date order, so a learner with a fail then a pass ends up with attempts one and two the right way round.

If you want to rehearse before touching your own data, the importers ship with sample files that walk the same order.

Step 6: reconcile

Before you tell anyone the switch has happened, check three numbers against the old system:

1. Learner count. Active learners in the old system, active learners in the new one.
2. Outstanding balances. Total owed should match, or you should know exactly why it does not.
3. Five spot-checked histories. Pick five learners at random and read their lesson history side by side.

If those three agree, the migration is sound. If they do not, you find out now rather than from a learner asking why their package says four lessons left when they know it is six.

Step 7: close the old account

Two separate actions, in this order.

Keep your own copy of the export. HMRC requires business records to be kept “for at least 5 years after the 31 January submission deadline of the relevant tax year”, and the new system holds what you imported, not necessarily every field the old one had. Archive the raw CSVs somewhere durable.

Then instruct deletion in writing, using the Article 28 wording above. Cancel the subscription after the deletion is confirmed, not before — you want the account live long enough to ask one more question.

Where migrations go wrong

Three failure modes, all avoidable:

Cancelling first. The single most expensive mistake. One month of overlapping subscription costs less than a week of reconstructing lesson history from memory.

Migrating mid-term. Move in a quiet week. The gap between a learner passing and their replacement starting is the ideal window; the week before a run of tests is not.

Not telling learners anything. They notice when the booking link changes and the reminder comes from a different name. A short message before the switch — this is changing, here is your new link, nothing about your lessons or your balance changes — heads off every one of the “have I lost my package?” messages you would otherwise get.

What it costs

Getting data into Passdesk costs nothing. Send us the export and it gets set up for you, on any plan, including during a trial.

If you are coming from a specific product, the comparison hub sets out what each one publishes on price and terms, including where Passdesk does less. And if you are moving because one instructor turned into three, the piece on growing past a solo diary covers what changes at that point.