How to Back Up and Move Your Aurelio Finance Data

How to Back Up and Move Your Aurelio Finance Data

Aurelio Finance keeps your entire financial life in one small file: backend/data.db, sitting inside the app’s folder on your computer. That simplicity is a gift when it comes to backups and moving machines. There is no export dance, no cloud sync to untangle, no account migration. You copy a file, and you are done. This guide shows you how to back up your data properly, how to move it to a new computer, and the mistakes that turn a two-minute job into a data-loss story.

Know Exactly What to Back Up

Everything Aurelio Finance knows about you lives in backend/data.db, a SQLite database file inside the project folder. Your accounts, transactions, investments, cash flow history, savings goals, and settings are all in there. The rest of the project folder is code, which you can always re-download from GitHub.

So the backup target is simple:

  • The file: backend/data.db inside your Aurelio Finance project folder.
  • Optionally, the whole folder: backing up the entire project directory also works and captures any local configuration alongside the database. It is larger but foolproof.
  • What you do not need to back up: installed dependencies (Node modules, Python packages). Those get reinstalled from scratch on any new setup.

Before copying, stop the app. Copying a database file while the app is actively writing to it can produce a corrupted backup. Close the terminal running the start script, wait a few seconds, then copy.

Set Up a Backup Routine That Actually Happens

A backup you do manually “when you remember” is a backup you will not have when you need it. Pick one of these approaches based on how much you trust your future self:

  1. Manual copy (minimum viable). Once a week, with the app stopped, copy data.db to an external drive or a folder that syncs to your cloud storage. Rename the copy with the date, like data-2026-10-20.db, so you keep history instead of overwriting last week’s good copy with this week’s problem.
  2. Cloud-synced folder (easy and automatic). Keep a dated copy of data.db in Dropbox, Google Drive, OneDrive, or iCloud Drive. Copy the file there on a schedule; the sync handles the off-machine part. Note: do not point the app itself at a cloud-synced live database file. Copy the file out, then let the cloud service sync the copy. Live databases and file-sync services can fight over locks and corrupt the working file.
  3. Scheduled script (set and forget). A tiny scheduled task (Task Scheduler on Windows, cron on macOS/Linux) that stops nothing, copies data.db to a backup folder with a timestamp, and keeps the last 30 copies. This is the most reliable option and takes ten minutes to set up once.

Whatever you choose, follow the 3-2-1 spirit: at least one backup on a different device or service than the computer running the app. A backup on the same drive that just died is not a backup. An external USB drive plus a cloud copy covers you against both drive failure and theft.

How to Restore From a Backup

Restoring is the reverse of backing up, and you should practice it once before you ever need it for real:

  1. Stop Aurelio Finance completely.
  2. Find your backup copy of data.db. If you keep dated copies, pick the most recent one from before the problem started.
  3. Rename the current backend/data.db to something like data-broken.db instead of deleting it. If the restore goes wrong, you still have the original.
  4. Copy your backup into backend/ and make sure it is named exactly data.db.
  5. Start the app normally and confirm your accounts, transactions, and investments look right.

The app also saves its own safety copy next to data.db before updates that change the database format. That automatic copy protects against bad migrations, but it lives on the same drive, so it does not replace your own off-machine backups. Think of it as a seatbelt and your backups as the insurance policy.

Moving to a New Computer, Step by Step

Moving Aurelio Finance to a new machine is refreshingly boring. Because there is no account and no cloud, “migration” just means getting the code running on the new computer and bringing your database file along.

On the old computer:

  1. Stop the app.
  2. Copy backend/data.db to a USB drive, external disk, or cloud storage. Verify the copy by checking its file size matches the original.
  3. If you use the AI advisor, note your OpenRouter settings so you can re-enter them. Your API key lives in the app’s configuration, so have it handy (or generate a fresh key on OpenRouter, which is cleaner).

On the new computer:

  1. Install the prerequisites: Git, Node.js 22+, and uv. Verify with git --version, node --version, and uv --version.
  2. Clone a fresh copy of the project from GitHub (github.com/LosaLosSantos/aurelio-finance) and run the install steps from the README.
  3. Start the app once with the start script and open http://localhost:8000 to confirm the fresh install works before touching your data.
  4. Stop the app, then copy your data.db into the new backend/ folder, replacing the fresh empty database.
  5. Start the app again. Your accounts, history, and goals should appear exactly as they were on the old machine.
  6. If you use the AI advisor, re-enter your OpenRouter key in the settings.

Keep the old computer’s data intact until you have confirmed everything works on the new one. Only wipe or repurpose the old machine after you have opened the app on the new machine and verified your balances and history.

Moving Between Operating Systems

Switching from Windows to macOS, or Linux to Windows, changes the start script but not the data. The database file is platform-independent: a data.db created on Windows opens fine on macOS and Linux.

What changes:

  • The start command. Windows uses .\start.ps1 (watch the PowerShell execution policy), while macOS and Linux use ./start.sh. Demo mode flags differ slightly too: --demo vs -Demo.
  • Prerequisite installation. Each OS installs Git, Node.js, and uv differently, but the version requirements are the same everywhere.
  • File paths. Where you clone the project folder is up to you; just remember where backend/data.db ended up so your backup routine can find it again.

Update your backup routine for the new machine’s paths and scheduling tools as part of the move. A backup script pointing at the old computer’s folder structure silently backs up nothing.

Mistakes That Lose Data (and How to Avoid Them)

Almost every data-loss story with local-first apps comes from the same short list:

  • Copying while the app runs. Stop the app first. A database being written mid-copy can back up in a corrupted state that only reveals itself at restore time.
  • Overwriting the only good copy. Always use dated filenames for backups (data-2026-10-20.db) instead of a single data-backup.db that gets overwritten. If corruption creeps in silently, you want last month’s copy, not last hour’s copy of the corrupted file.
  • Backing up to the same drive. Ransomware, theft, and drive failure all take the backup with the original. Off-machine means off-machine.
  • Never testing a restore. Do a practice restore into a scratch copy of the project folder once. It takes five minutes and converts your backup from a hope into a verified plan.
  • Deleting the old machine too early. Confirm the new setup fully, then wait a week of normal use before wiping the old computer. Patience is free; data recovery is not.
  • Mixing demo and real data. If you explored in demo mode on the new machine, make sure you are restoring your real data.db into a normal (non-demo) setup, and do not mistake demo sample data for your records.

How Often Should You Back Up?

Match the frequency to how often your data changes:

  • Daily (automated): ideal if you log transactions every day. A scheduled script makes this effortless.
  • Weekly (manual or automated): fine for most people who update investments and check cash flow on weekends.
  • Before every update: always copy data.db before running git pull or any update, even though the app saves its own pre-migration copy. Belt and suspenders.
  • Before any move or reinstall: non-negotiable. Copy first, verify the copy, then proceed.

The file is small, typically well under a few megabytes, so frequent backups cost you nothing in storage. There is no reason to back up rarely.

Conclusion

Backing up and moving Aurelio Finance is as simple as its storage model: one file, backend/data.db, holds everything. Stop the app, copy the file somewhere safe on a schedule, keep dated copies off the same machine, and practice a restore once. Moving computers means a fresh clone, a fresh install of the prerequisites, and dropping your data.db into the new backend/ folder. No accounts to migrate, no cloud to untangle, no export formats to convert. Local-first puts the responsibility on you, but it also makes the job genuinely easy.

Read next:

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top