You don’t start from zero. Jetlog reads several common export formats and walks you through matching columns and fields. It always stops at a review screen first: nothing is written until you tap confirm.
Supported formats
- LogTen Pro: including the address book, so aircraft and crew come across as real records, not loose text.
- CrewLounge PILOTLOG: flight history import.
- CSV: a generic column-mapped import; works with almost any spreadsheet-based logbook.
-
Excel (
.xlsx): same mapped-import path as CSV, native spreadsheet format. - KLM / KLC statement PDFs: covered in Importing KLM/KLC statements and rosters.
If your current logbook is SafeLog, FlightLogger, Flylog, or RB Logbook/CAE, export to CSV or Excel first. Native import isn’t built for those tools yet, but the CSV/Excel path plus column-mapping covers the same ground for most entries.
How the import works
- Export your existing logbook to one of the formats above.
- Pick the file in Jetlog (Settings → Import).
- Map columns if you used CSV/Excel: tell Jetlog which column is date, which is route, which is block time, and so on. LogTen Pro and CrewLounge PilotLog imports map themselves automatically.
- Review before you save. Every imported flight lands on a review screen first (dates, routes, aircraft, and crew all shown as they’ll be saved). Fix anything that looks wrong, deselect rows you don’t want, then confirm.
- Aircraft and crew that don’t exist yet in your logbook are created as you import; ones that do are matched, not duplicated.
After importing
Once a flight is in, it behaves exactly like one you typed by hand: edit it, sign it, include it in reports, or fix a batch of them at once with the bulk editor. New flights fill themselves in automatically from there; see How automatic flight tracking works for coverage. Imports are for the flights that came before.
For paper logbook pages instead of an export, see AI logbook scanning.
