For schools leaving MyFBO.com
MyFBO is closing.
Your flight school isn’t.
A flight school’s value is in its history: who flew what, when, on whose ticket, and what it cost. Send us a MyFBO backup and we bring the whole thing across — every aircraft, every student, every dispatch and receipt going back as far as your records do. We can run it again tomorrow, and the day after, without duplicating a single flight.
Nothing is deleted
Nothing is duplicated
Repeated nightly until you switch
The model
Run both, for as long as you like.
The hard part of leaving a system is never the copy. It is the weekend where the old one is read-only, the new one is half-loaded, and somebody still has to dispatch a 09:00 lesson.
So we merge rather than load. Every record is remembered against the MyFBO record it came from. Run it again and what already exists is updated in place, anything new is added, and anything your staff created inside AviFBO is left completely alone.
That makes the sensible migration a boring one: keep dispatching in MyFBO while we bring your data across each night. Bookings that moved, move. Dispatches that closed, close. Your staff learn the new board on real data with nothing at stake, because MyFBO is still the system of record. You switch over on the day the team is ready.
While both are live, MyFBO wins any disagreement: customers, aircraft and maintenance due points are refreshed from it on every pass. History is treated more carefully — new dispatches come across in full, recent ones are refreshed to pick up meter corrections, and receipts and payments already brought over are never altered.
The manifest
Where each MyFBO table lands.
Eight source groups, read in one pass. The left column is MyFBO's own naming — so anyone who has looked inside a MyFBO backup can check this against what you actually have.
| MyFBO | Becomes | What to know |
|---|---|---|
| Resources | Aircraft, instructors, sims, rooms | Tail numbers, types, meters and rates. Instructors arrive as both a resource — so they can be scheduled — and a person who can log in. |
| Customers + ExtendText | Customer records | Students and renters with certificates, medical and ratings, plus the long-form notes MyFBO kept in its side table, landing as customer comments. |
| Dispatches | Flights and receipts | Every closed dispatch becomes a flight with its meters and a receipt. Receipt numbers reuse the MyFBO dispatch id, so a receipt somebody printed in 2014 still finds its record. |
| Items | Receipt lines and payments | Charges and payments, read in MyFBO's own units — money in cents, hours and quantities stored at a hundred times their value. |
| Events | Reservations | Bookings, including the ones that moved since the last run. A future booking that has vanished from MyFBO is marked cancelled here rather than deleted. |
| Maintenance | Maintenance items | Inspection intervals and due points. Tach-tracked items are converted to hobbs-equivalents, with the true tach figure kept in the notes. |
| DutyTime | Time clock entries | Staff clock-in and clock-out history, re-stamped into the organisation's timezone. |
| Types, Locations, CrossRefs | Lookups and labels | Aircraft types, bases and the cross-reference tables that give everything else its names. Medical, flight-review and registration dates become tracked renewals. |
How it goes
Send a backup, check the result, switch when ready.
Nothing here needs anyone technical on your side beyond getting the backup out. The parts that take judgement are ours.
Get a backup out of MyFBO
You need a backup of your MyFBO database — the ordinary file their support can produce for you. That is the one part only you can do, because only you can ask for your own data.
Send it to us
We take it from there: your aircraft, instructors, students, the whole dispatch and receipt history, maintenance intervals, time clock and renewal dates. Depending on how many years you are carrying, a first pass takes anywhere from minutes to a couple of hours.
Check it against MyFBO
This is the step worth taking seriously, and it is yours. Open the fleet. Open a student who has been flying with you for a decade. Open last month’s receipts and compare the totals against MyFBO. If something does not line up, tell us and we will find out why before you go any further.
Keep both running until you are ready
Carry on dispatching in MyFBO. We bring everything across again each night, so the two stay in step while your staff get comfortable — bookings that moved, moved; dispatches that closed, closed. When the team stops reaching for the old system, you are already migrated. There is no cutover weekend.
Sharp edges
Six things MyFBO stored in a way you would not expect.
Each of these quietly corrupts a careless import — wrong times, wrong money, hours counted twice. They are handled. They are listed because whoever moves your records should be able to tell you what they were.
Wall clock in, real instants out
MyFBO writes local wall-clock times with no zone attached. The importer converts them from the zone you name into UTC, so a 14:30 lesson is still 14:30 on the board — and stays right when the clocks change.
Cents and hundredths
Money is stored in cents, and hours and quantities at a hundred times their value. Both are unwound on the way in, so a 1.3-hour flight at 160 arrives as 1.3 and 160.00, not 130 and 16000.
Payments are one item type
MyFBO records prepay-account bookkeeping alongside real payments, in the same table. Only actual payments become payments here; the bookkeeping rows are read but never double-counted into your A/R.
Tach maintenance, hobbs fleet
Items tracked against tach time are converted to hobbs-equivalents so one calculation drives every due and overdue badge, with the original tach figure preserved in the notes.
Duplicate dispatches are folded
MyFBO archives can carry the same flight twice. The importer dedupes on a stable key and reports how many it folded, rather than quietly inflating your hours.
A guard against a bad mapping
If a run would create history for more than 5% of the flights already there, it stops before writing anything — that is nearly always a mapping that failed to line up, not a genuinely newer backup.
Comes across
Everything the backup holds
- Aircraft, instructors, simulators and classrooms, with rates and current meters
- Student and renter records, certificates, medicals, ratings and comments
- The full dispatch archive — flights, hobbs and tach, and the receipts they produced
- Receipt lines, payments and the balances that fall out of them
- Upcoming bookings, kept in step on every run
- Maintenance intervals and current due points
- Time clock history and renewal due dates
Worth knowing
And three things to plan for
- Files attached inside MyFBO — a database backup does not contain them, so documents are uploaded once into the Documents register
- Stored card details. Payments are recorded against receipts here, so there is nothing to carry across
- MyFBO logins. The import creates the one admin account you name; everyone else gets credentials issued in AviFBO
See your own records in it first.
A trial run tells you more than any demo: your fleet, your students, your fifteen years, on a board you can click around in — before you commit to anything. If something does not line up, that is worth finding out now.