ForeFlight logbook CSV workflow

ForeFlight logbook CSV import, export, and mapping

Moving logbook records should not lock you into one app. Import a ForeFlight logbook CSV export into TopLog, review the mapped records, and export TopLog entries in a CSV layout you can review against ForeFlight's import template when you need to move records back.

TopLog is not affiliated with or endorsed by ForeFlight. Review all imported and exported records before relying on them.

TopLog web logbook showing export controls and flight records

Two-way records

Use TopLog without giving up your ForeFlight records

TopLog is useful when you want AI-assisted paper logbook capture, a web logbook, and exports you control. ForeFlight may still be part of your workflow. CSV import and export keeps that choice open.

Import

Bring a ForeFlight CSV into TopLog

Upload the spreadsheet, map the columns, preview parsed rows, and load the reviewed entries into your TopLog account.

Review

Check the important columns

Confirm dates, route, aircraft, role time, night, instrument, landings, comments, and totals before treating the import as your working record.

Export

Create a CSV for the import template

When you need to move back, export TopLog entries in a layout you can review against ForeFlight's import template.

Switching workflow

A practical ForeFlight-to-TopLog migration

Treat the move like a logbook audit: preserve the source file, import in a controlled batch, review the parsed rows, and export a fresh backup when you are done.

1

Export your ForeFlight logbook CSV

Start with the spreadsheet export from ForeFlight on the Web. Keep the original file unchanged so you always have the source copy.

2

Import the CSV into TopLog

Use TopLog's spreadsheet import to map the flight table into TopLog fields such as date, aircraft ID, route, role time, night, cross-country, instrument, landings, and comments.

3

Review the mapped records

Check field mappings, aircraft type, role time, night time, totals, and any fields ForeFlight stores in packed or app-specific columns.

4

Export when you need to move back

TopLog can export your reviewed entries as a CSV arranged around ForeFlight's import-template columns, so your data is not trapped in one place.

From ForeFlight

How to export your ForeFlight logbook CSV

ForeFlight's support docs describe CSV export from ForeFlight on the Web. Use that export as the source file for TopLog import, and keep an untouched copy before you start mapping fields.

  1. 1Log in to ForeFlight on the Web.
  2. 2Open Logbook from the left menu.
  3. 3Choose the Export tab.
  4. 4Use the Export button to download a CSV copy of the logbook.
  5. 5Save the original export somewhere safe before editing or importing it anywhere else.

Back to ForeFlight

How to prepare a reviewed CSV for ForeFlight

When records need to go back, treat the TopLog export as a file to verify, not a blind sync. ForeFlight imports CSV or TSV files from the Logbook Import tab and warns pilots to avoid duplicate entries.

  1. 1Export a TopLog CSV arranged for ForeFlight's import template.
  2. 2Log in to ForeFlight on the Web and open Logbook.
  3. 3Open the Import tab.
  4. 4Upload the CSV or TSV file.
  5. 5Review ForeFlight's import preview before importing the records.

Fields

ForeFlight fields to check during import

The exact result depends on the file you export and the columns you choose to map. These are the groups pilots should review before saving imported records.

Core flight details

  • Date
  • Aircraft ID
  • From
  • To
  • Route
  • Pilot comments

Time columns

  • PIC
  • SIC
  • Dual received
  • Night
  • Cross-country
  • Instrument

Counts and checks

  • Day landings
  • Night landings
  • Simulated flight
  • Totals
  • Unmapped columns

Column mapping

ForeFlight CSV fields to review in TopLog

Do not judge a migration by whether the row count matches. Check the fields that drive totals, currency, and application numbers.

ForeFlight export field

ForeFlight Date

TopLog field

Date

Review note

Check mixed date formats before importing older records.

ForeFlight export field

AircraftID

TopLog field

Aircraft registration / identifier

Review note

Fill aircraft type if the flight row does not include it.

ForeFlight export field

From / To / Route

TopLog field

Departure, arrival, route

Review note

Look for multi-leg routes and airport code spelling differences.

ForeFlight export field

TotalTime

TopLog field

Total time

Review note

Reconcile decimals and page or app totals after the import.

ForeFlight export field

PIC / SIC / Dual

TopLog field

Crew role time

Review note

Confirm split time columns before using totals for applications.

ForeFlight export field

Night / XC / Instrument

TopLog field

Condition and currency fields

Review note

Check any field you rely on for currency or experience summaries.

ForeFlight export field

DayLandings / NightLandings

TopLog field

Landing counts

Review note

Compare day/night split columns for training and currency records.

ForeFlight export field

Comments / Remarks

TopLog field

Pilot comments

Review note

Make sure training notes, approaches, and endorsements survive cleanup.

Review notes

What to watch for before you rely on migrated records

CSV files are a practical way to move records, but they are not a substitute for review. Keep the source export and reconcile the fields that matter to your currency, applications, or interviews.

Review aircraft type

ForeFlight's flights table identifies aircraft by AircraftID. If aircraft type is not present in the flight rows, review or fill it during import.

Check app-specific columns

Some ForeFlight fields use packed detail columns or values that need review. Import the important fields first, then reconcile against your source export.

Keep both backups

Keep your ForeFlight export, your TopLog records, and a fresh TopLog export. That gives you a cleaner rollback path if a mapping needs correction.

Try the workflow with a small batch first

Import a few representative rows, check the mapped fields, then scale up once the workflow matches your records. That is faster than debugging a full-logbook import after the fact.

Compare digital logbook options

Questions pilots usually ask

Can I import a ForeFlight logbook into TopLog?

Yes. Export your ForeFlight logbook as a spreadsheet or CSV, then use TopLog's spreadsheet import to map and review the flight rows before saving them.

Can I export TopLog entries for ForeFlight?

Yes. TopLog can export a CSV arranged for review against ForeFlight's import template. Review the exported file and ForeFlight's import preview before relying on the moved records.

Is this an official ForeFlight integration?

No. TopLog is not affiliated with or endorsed by ForeFlight. The workflow uses CSV files that pilots review during import and export.

Should I delete my original ForeFlight export after importing?

No. Keep the original export as your source backup until you have reviewed the imported records and reconciled the totals you care about.