There is a particular spreadsheet that runs a lot of flight schools. It has a tab per aircraft, color coding that only one person fully understands, a column that was added for a reason nobody remembers, and a formula in row 400 that broke in March.
We have written before about the signs you have outgrown it. This post assumes you are past that and have decided to move. It is the practical part: what to actually do, in what order, in about an afternoon.
First, appreciate what the spreadsheet was good at
This is not sentimentality. Understanding why the spreadsheet lasted this long tells you what your replacement has to do, and it is the step people skip.
Spreadsheets survive in flight schools because they are infinitely flexible and instantly editable. When a student calls to move a lesson, someone types over a cell. When an aircraft goes down, someone highlights a row red. There is no workflow, no permission, no field that will not accept what you want to put in it.
That flexibility is exactly what breaks at scale, but it is also why your staff like it. If the replacement makes the common case slower, people will keep a shadow spreadsheet, and then you have two systems and no truth. Whatever you move to, the test is whether moving a lesson takes less time than typing over a cell.
What to move
Far less than you think.
Aircraft. Tail number, make and model, category, hourly rate, active or not. There are usually between one and fifteen of these. Enter them by hand, it takes a few minutes and it is more accurate than anything else.
Instructors. Names and contact details. Again, a short list.
Students and members. This is the one real list. Names and email addresses are the minimum, since email is how they get invited in.
Future bookings. Everything already committed. Depending on how far ahead your school books this is somewhere between twenty and two hundred entries.
Currency records. Flight review dates, medical class and expiry, last three landings, IFR currency where it applies. Enter these one at a time and check each against your source. This is the part of the migration where a typo has regulatory consequences rather than merely annoying ones. Our currency tracking guide sets out what each field means and which FAR governs it.
What to leave behind
Historical bookings. Keep the spreadsheet. Archive it, name it clearly, put it somewhere you will find it. You do not need three years of completed lessons inside a new system, you need them retrievable, and a saved file does that.
The color coding. Whatever the yellow means, the new system will express it as a field, a status, or a flag. Write down what each color meant before you archive the file, because in six months you will want to know.
Your workarounds. Every long-lived spreadsheet has structures that exist to compensate for it being a spreadsheet. Duplicate rows to represent recurring bookings. A separate tab for cancellations. A column that holds three pieces of information separated by slashes. None of these should be recreated. Work out what each one was for and let the new system do that thing properly.
Formulas nobody can explain. If you cannot say what it does, it does not move.
An afternoon plan
First 30 minutes. Enter your aircraft with rates, and your instructors. Small lists, high accuracy, worth doing carefully.
Next 30 minutes. Add students. If you have a lot, an email list is enough to start, and details can fill in as they log in.
Next hour. Enter currency records and verify each one against the spreadsheet as you go. Slow, deliberate, checked twice. This is the part that matters.
Next hour. Enter future bookings, working forward from today. Do the next two weeks first so that if you run out of time you have covered the period where being wrong actually hurts.
Last 30 minutes. Book a flight, cancel a flight, take an aircraft down for maintenance, and try to book a student who is out of currency. Confirm each does what you expect before anyone else touches it.
That is an afternoon for a typical small school. A larger fleet takes longer, but the sequence is the same.
Then run both for two weeks
Keep updating the spreadsheet in parallel for a fortnight. It is double work and it is the difference between a smooth switch and a bad Saturday.
Two weeks of real use finds the things a quiet afternoon cannot: the standing slot that does not fit, the instructor with an unusual arrangement, the aircraft whose rate has an exception. You want to find those while the spreadsheet still works.
Set an end date and stick to it. Parallel running that goes on indefinitely turns into permanently maintaining two systems, which is worse than either alone.
Telling your staff
The person who built the spreadsheet is going to have feelings about this, and they are usually the most operationally knowledgeable person you have. Involve them early rather than presenting it as done. They know every edge case in your school, which makes them the best possible person to test with, and the worst possible person to surprise.
For instructors, ten minutes on the mobile view is the entire training requirement. For students, one short email with a direct link to set a password, sent twice.
What to expect afterwards
The first fortnight feels slower. That is normal and it passes. What you should see by the end of the first month:
Double bookings stop, because the system will not allow them rather than because someone is being careful.
Currency stops being something you remember to check and becomes something that tells you. Expiries surface before they happen rather than after.
You get numbers you did not have. Which aircraft actually earns, what your utilization is, how many bookings get cancelled. Our fleet management guide covers what to do with those once you have them.
Students book themselves, which is where most of the admin time actually goes.
What you should not expect is that the software fixes your processes. If your no-show problem is really a policy problem, software enforces the policy you have rather than inventing a better one. Our no-show policy post covers writing that policy first.
Where SkyFSBookings Fits
The free plan covers one aircraft and one instructor with unlimited students, permanently, with no credit card. That is enough to do this entire migration, run it in parallel with your spreadsheet, and decide whether it works, without spending anything.
Currency tracking with expiry alerts is included on every tier, because that is usually the actual reason the spreadsheet has become dangerous rather than merely annoying. When you are ready for more aircraft, paid tiers start at $15 a month, and your data exports back out to CSV whenever you want it.
If you are moving from another software platform rather than a spreadsheet, switching without losing your booking history covers the extra steps involved. If you are still deciding, how to choose flight school scheduling software has the questions to ask.
Create a free account and give yourself an afternoon.
