> For the complete documentation index, see [llms.txt](https://tribalfs.gitbook.io/accountant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tribalfs.gitbook.io/accountant/your-data/importing.md).

# Importing

Bring your records from Bluecoins, Spendee or Monefy.

**What you'll do:** move your records into Accountant from another app.

All imports are in **Settings › Data and backups**.

## What you can import

| Option                                              | File                                       | Notes                                                                |
| --------------------------------------------------- | ------------------------------------------ | -------------------------------------------------------------------- |
| **Migrate from Bluecoins** (*Experimental*)         | A Bluecoins backup file (`.fydb`)          | Photos aren't included in Bluecoins backups, so they aren't imported |
| **Migrate from Spendee or Monefy** (*Experimental*) | A CSV file exported from Spendee or Monefy | Expenses, income and wallets                                         |

## Import step by step

1. Tap the import option and choose the file.
2. Wait while the app shows **Reading file…**.
3. Check the preview, **This file contains:**, which lists what will be imported. The preview also says how many of the file's accounts and categories are **already in your ledger**. Those are reused, matched by name, instead of being added twice.
4. Decide on **Clear existing data first**:
   * **On:** *"Your current records will be deleted. The accounts and categories the app starts with stay, without opening balances or budgets."*
   * **Off:** *"Imported records will be added to your current ones."*
5. Tap **Import**.

If demo data is present, the preview may say *"Sample data will be removed."*

{% hint style="info" %}
**You can undo an import.** A copy of your ledger is saved before every import. To go back, tap **Settings › Undo last import** and then **Restore**. Anything you changed after the import is lost, and the app restarts.

If sync is on, you can undo only until the import syncs with Google Drive; after that, undoing would leave your other devices out of step.
{% endhint %}

## Currency must match

Bluecoins, Spendee and Monefy files have a main currency. If it differs from your **reporting currency**, the app tells you to change your main currency first. Change it in **Settings › Reporting currency** (easiest on a fresh ledger), then import again.

## If an import fails

* *"This file isn't a Bluecoins backup."* or *"This file isn't a Spendee or Monefy CSV export."* Check you chose the right file. For other apps, see below.
* If a Bluecoins, Spendee or Monefy import runs into problems, the app may offer **Share error log** so you can email us the details.

## Moving from another app?

Tap **Request import support** (*"Moving from another app? Send us a sample export so we can add an importer for it"*).

1. Export a file from the app you use now, **using dummy data only, not your real records**. For best results, include a mix of accounts, currencies, categories and transaction types.
2. Tap **Choose file** and pick it.
3. Enter the **App you're moving from**, and optionally notes such as the app version or export option you used.
4. Confirm **This file contains dummy data only** and tap **Send**.

Your email app opens with the file attached, plus your device model, Android version and app language. Nothing is sent until you send the email.


---

# 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://tribalfs.gitbook.io/accountant/your-data/importing.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.