Services
Choosing and moving to new aviation software
From requirements and the request for proposal (RFP) to cutover, with your flight history kept and your operation flying throughout.
For Federal Aviation Administration (FAA) Part 135 and 121 operators and Canadian Aviation Regulations (CAR) 704 and 705 operators replacing a flight operations, maintenance or finance system.
Replacing a flight operations or finance system is one of the riskiest projects an operator takes on. Vendors demo well, the old system holds years of history, and every connection built on it has to move too. We run it from requirements to cutover.
A demo tells you little about the fields you will need on a Friday night. So we start with the people who will use the system, dispatch, maintenance, crew and finance, and turn what they need into an RFP vendors answer line by line. The recommendation is scored, and you can take it to the owners.
Read the data clause before you sign. Most software-as-a-service (SaaS) contracts grant the vendor a perpetual licence to your data, and on one RFP we ran, the incumbent wanted ten thousand dollars to hand back the operator's own flight history. We negotiate that before the contract, and we move the history somewhere you own.
What we do
Requirements, RFP and recommendation
Requirements from dispatch, maintenance, crew and finance, an RFP vendors answer line by line, and a scored recommendation you can take to the owners.
Data migration
History moved out of the old system, checked against the source, and kept somewhere you own.
Connections on the new platform
Charter marketplaces, maintenance tracking, flight planning and security filings reconnected to the new system.
How AI does the work
Requirements from real conversations
We interview each department and use AI to turn the notes into a requirements list nobody has to retype, then check it with the people who said it.
RFP answers scored line by line
Vendor responses run to hundreds of lines. AI reads every one against the requirements and flags where an answer is vague or conditional, so the engineer's time goes to the answers that matter.
Migration scripts checked against the source
Moving years of flights, quotes and crew records means mapping fields between two schemas. AI writes the migration and the checks that compare every record with the old system before cutover.
Integrations rebuilt in weeks
A dozen connections on a new platform used to be the slow part of a migration. With AI writing the connectors, they are rebuilt in weeks and tested before the old system is switched off.
How it works
- 1We interview each department, run the RFP, and score each vendor against what they need.
- 2We plan the cutover so the operation keeps flying while data and connections move.
- 3Old history stays searchable after the old system is switched off.
Where we have done it
Planet Nine Private Air
We ran their vendor selection through to a recommendation, then implemented the new flight operations platform with about a dozen integrations, including Avinode, CAMP and ForeFlight.
Flight history kept
Planet Nine's flight history back to 2018 now sits in a data mart they own, so replacing the old system did not mean losing it.
Great North Airlines
Their books moved from QuickBooks to Business Central.
Questions operators ask
What does the selection include?
Requirements from dispatch, maintenance, crew and finance, a request for proposal (RFP) that vendors answer line by line, and a scored recommendation you can take to the owners.
Which systems have you selected or migrated?
A flight operations platform with about a dozen connections, including Avinode, CAMP and ForeFlight, at Planet Nine Private Air. Accounting from QuickBooks to Business Central at Great North Airlines. Microsoft 365 tenant moves for several operators.
Are you tied to a vendor?
No. We are vendor agnostic on purpose. We are paid to run the selection and the move, not by the vendor you choose, and we will point you to the right product when buying is the better answer.
Will we lose our history?
No. Planet Nine's flight history back to 2018 sits in a data mart they own, so replacing the old system did not mean losing it. We move history out, check it against the source, and keep it searchable after the old system is off.
How do you keep the operation flying during cutover?
The new system runs beside the old one until the data and the connections are proven. Cutover is scheduled around your flying, one department at a time where it can be, and the old system stays readable until you no longer need it.
Which connections move to the new system?
Charter marketplaces, maintenance tracking, flight planning and security filings. For Planet Nine that was about a dozen integrations, including Avinode, CAMP and ForeFlight.
Could we build instead of buying?
Sometimes. The selection includes that option honestly: buy when the vendor brings data or integrations you cannot replicate, build when the software is simple, expensive, and hands you nothing unique in return. Plenty of the time buying is right.
How long does a selection take?
It depends on how many departments are involved, and we scope it on the first call. Implementation depends on the platform, and we plan it with the vendor before you sign.