Skip to content

Backing up, moving, and taking your data

Export a backup you control, move your budget, or download the forecast for further work.

On this page

Your data remains yours. Ebbe lets you download the whole budget as a readable JSON backup, export your account data, or take the forecast into a spreadsheet without a fee or a special request.

The four downloads

Your budgetSettings → Budget → Export JSON. One file with the budget’s settings, every category, every recurring and one-off item, the tag settings and every balance reading. This is the backup, and it is the file to keep.

Your accountAccount → Profile → Export all my data. The same budget, plus your address, when you signed up, and your preferences. This is the Article 20 export. Password hashes and session records are not included.

The forecast, as a spreadsheet — one row per month with income, spending, net, balance and whether the month is below your buffer.

Every payment, as a spreadsheet — one row per individual payment with its date, name, category, direction, amount, whether it was an estimate, and whether it came from a recurring or a one-off item.

The two spreadsheets are what to open in Excel or LibreOffice. The two JSON files are what to keep.

Importing

Settings → Budget → Import, in the red-bordered block.

Import replaces the whole budget. It is not a merge: what is in the file becomes what is in the budget, and what was there before is gone. There is a confirmation, and it is worth reading.

It accepts both JSON exports: the budget export and the full account export. When you import an account export, Ebbe uses only its budget data. Your email address and password do not change.

Identifiers from the file are replaced with fresh ones, so importing the same file twice gives you the same budget twice over, not a duplicate mess inside one.

Moving your budget

  1. Export the budget from the old Ebbe service.
  2. Create an account on the new service.
  3. Import the file.
  4. Check the forecast matches, then delete the old account.

Nothing in the file is tied to a particular address or account, so the same file can be imported wherever Ebbe is available.

Backing up regularly

There is no automatic backup for you to configure, and no cloud copy — that is the other side of an application that does not want your bank details.

Download the budget JSON every few months and put it wherever your other important files live. It is small, it is plain text, and it is the whole thing.

The operator may also back up the database, but that does not replace a copy you control. If you need to know what is covered, ask rather than assume; the application cannot answer that for you.

What tokens cannot do

The two exports are reachable with a personal access token, so a script can fetch a backup on a schedule. Import is not, and neither is emptying the budget: the interface asks for a confirmation before each of those, and a token has nobody to ask. See tokens and scopes.