Importing from another logbook

You don’t start from zero. Jetlog reads several common export formats and walks you through matching them to your logbook. It always stops at a review screen first. Nothing is written until you tap confirm.

Imports live under Settings › Imported Logbook Records. That same screen is also where you import from every source listed below, re-check what came in afterwards, and clean up a previous import. Excel and CSV re-import (round-tripping your own exported file) also works from Export / Import; see Exporting your logbook.

Supported formats

Under Import from File or Scan:

• Digital File: a PDF monthly overview or chronologisch overzicht.
• Excel Workbook: re-import an edited Jetlog .xlsx (only changes are applied).
• CSV Files: re-import edited Jetlog CSV files or a .zip (only changes are applied).
• Scan Pages: a photo or scan of a paper logbook page. See AI logbook scanning.

Under Other Logbook Importers:

• Import from PilotLog: CrewLounge PILOTLOG flight history, downloaded from the web or picked as a file.
• Import from LogTen: a LogTen Flights export (required), plus an optional Address Book export so aircraft and crew come across as real records, not loose text.
• Import from SafeLog, Import from FlightLogger, Import from Flylog, Import from Skylife, Import from CAE RB Logbook: each reads that tool’s own export directly, no manual matching needed.
• KLM / KLC statement PDFs: covered separately in Importing KLM/KLC statements and rosters.

How the import works

1. Export your existing logbook from its source app (where relevant; PilotLog can download directly inside Jetlog).
2. Go to Settings › Imported Logbook Records and pick the matching importer.
3. 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.
4. Aircraft and crew that don’t exist yet in your logbook are created as you import; ones that do are matched, not duplicated.

Checking an import afterwards

• Managing and re-checking imports. Go to Settings › Imported Logbook Records › Previously Imported Records to browse everything you’ve imported, grouped by year and month. The trash icon top right (Clean Previous Imports) deletes every previously imported entry (and any aircraft/people that only exist because of it) in one go. There’s no per-import undo beyond that, so use it only if you want to start the import over.
• “You have no role set on this flight” (or “…on this simulator session”). PilotLog, LogTen, CrewLounge, and the other importers flag any row where they can’t tell what role you flew in (captain, first officer, and so on). The flagged row sits in the review screen; open it and tap Set Role to pick your role for that flight before confirming. This is common after a PilotLog or LogTen import where a blank or ambiguous crew slot couldn’t be resolved automatically.

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.