> For the complete documentation index, see [llms.txt](https://support.waderaviation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.waderaviation.com/onboarding/importing-your-previous-logbooks.md).

# Importing Your Previous Logbooks

Transfer your complete flight history from other logbook apps or airline systems into Wader.

Bring your complete flight history into Wader from another logbook app or from your airline's crew system.

{% hint style="success" icon="gift" %}
**Importing from another logbook app is FREE.** Moving your logbook from another digital logbook app (such as LogTen, ForeFlight, CrewLounge or OffBlock) costs nothing, on any plan.

Importing from an **airline crew system** or from the **Wader spreadsheet template** is part of **Wader PRO**. These sources show a PRO tag in the source list.
{% endhint %}

## How the import works

1. **Open Import.**
   * **In the app:** open the **Logbook** tab, tap the **☰ menu** at the top right and choose **Import hours**. The **Import logbook** screen opens.
   * **On the web:** open the [web app](https://logbook.waderaviation.com/import) and select **Import** in the side menu.
2. **Choose your source.** Search for your logbook app or your airline.
3. **Follow the export steps** shown for that source. The steps live in the app, so they are always up to date for every source we support.
4. **Upload your file** and tap **Submit import request**. Files can be up to 20 MB. Your file is processed **automatically**, and you are notified by email when it is done.

{% hint style="info" %}
**Airline not supported yet?** Search for it in the source list anyway. If we cannot import it yet, you can request it from there, and our team will check what your crew system can export.
{% endhint %}

### Sending your file by email

You can also forward your file to **\[airline]@wader.pro** from the email address on your Wader account:

* You can use the airline's IATA code, ICAO code or name, and the system identifies it. For example: <ad@wader.pro>, <azu@wader.pro> or <azul@wader.pro>.
* If your airline uses AIMS / eCrew, you can also send it to <aims@wader.pro>.
* To send from your work email, add it as a secondary email in your [profile](https://logbook.waderaviation.com/profile).

### Good to know

* **Importing again updates.** A flight that is already in your logbook is updated, not duplicated. See [Fixing or Updating an Import](/importing-your-data/updating-your-records-via-import.md).

***

## Standard Spreadsheet

If your logbook app or airline is not in the source list, you can copy your records into our spreadsheet template and import that file. Importing the template is part of **Wader PRO**.

Download the template and follow the field specifications here: [Standard Spreadsheet](/importing-your-data/from-another-logbook.md#standard-spreadsheet).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.waderaviation.com/onboarding/importing-your-previous-logbooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.