16. Guides

Export Transactions and Data

Create a clean export when you need a backup, an external copy, or a safer checkpoint before making larger changes.

Use this guide when you want a safe copy or need to move data out of Common Cents.

Before you start #

Know whether you need a full backup, a transaction export, or both.

What you will do #

Open the export flow, choose the right export for the job, save it somewhere intentional, and then confirm you can identify it later if you need to restore or review it.

1. Decide what kind of output you actually need #

Start by naming the real goal.

Usually it is one of these:

a safety checkpoint before a risky change
a new working .cents file branch
a CSV for reporting or external analysis
a filtered transaction export instead of a whole-file export

If you choose the goal first, the right export action usually becomes obvious.

2. Use Create Backup when the goal is a safe return point #

Use Create Backup when you want a .cents checkpoint but want to keep working in the current file.

This is the safest move before:

a large import
bulk cleanup
structural edits to payees, categories, or labels
any change where you might want to roll back by reopening the older file

3. Use Save As when the goal is a new working file #

Use Save As when you want a differently named .cents file to become your active document.

That is the right choice when:

you are branching into a new version of the budget
the current session is an imported copy that now needs a real file name
you intentionally want to leave the original file untouched and keep working in the new one

4. Use the whole-file CSV exports when you need data outside Common Cents #

Most export actions live in Settings > File / Export.

Choose the CSV type based on what you actually need:

Export All Transactions CSV for the broad reporting export
Export Transactions Import CSV for an import-ready transaction export
Export Budget CSV for monthly budget-input data
Export Planning CSV for the broader month-by-category planning view

Do not default to the biggest export just because it sounds safer. Pick the one that matches the downstream use.

5. Use filtered exports when the current transaction search is the real scope #

If you already narrowed the All Transactions page to a specific subset, use the filtered export actions there instead of exporting the whole file and cleaning it later.

The filtered transaction options are:

Export Filtered CSV
Export Filtered Import CSV

This is the better path when your current filters already define the exact dataset you want.

6. Save exported files with names and locations you will recognize later #

Whatever export you choose, save it somewhere intentional and name it clearly enough that future-you can tell what it is.

This matters most when you create several exports near the same time, such as:

backup plus CSV before an import
monthly reporting exports
multiple test exports while cleaning up a mapping

7. Do a quick confirmation pass before moving on #

Before you leave the export workflow, make sure you can answer these questions:

do I know where the file was saved?
can I tell whether this is a backup, a Save As branch, or a CSV export?
does the export type match what I actually need next?

That quick check is what keeps a good export habit from turning into folder clutter.

Quick chooser #

Use this shortcut when you are unsure which action belongs to the job:

use Create Backup for a safe return point
use Save As for a new active .cents file
use Export All Transactions CSV for broad transaction reporting
use Export Transactions Import CSV for re-import-friendly transaction data
use Export Budget CSV for budget inputs only
use Export Planning CSV for broader planning output
use filtered exports when the Transactions page already shows the exact subset you want