Summ lets you save a snapshot of your account and restore it later. If a sync, bulk edit, or reconciliation session goes wrong, you can roll your account back to a point where everything was correct — no support ticket needed.
Where to find it
Go to the History page in the main navigation. On a paid plan, open the Saved backup tab — the page opens on Change history, which lists recent changes to your transactions. On the free plan your backups are shown straight away.
Creating a backup
On the History page, click Create backup.
Optionally add a description so you can recognise it later, e.g. "Before syncing accounts for 2026".
Click Save backup. You can keep using Summ while the backup runs — progress is shown on screen.
A good habit is to create a backup before big changes: adding a new exchange or wallet, running a hard sync, or making large bulk edits.
What a backup includes
All of your transactions and their categorisations.
Your accounts — wallets, exchange connections, and file imports. To protect your credentials, API keys are not stored in the backup, and neither are the original CSV files.
Your tax settings at the time of the backup.
A snapshot of your portfolio and report figures, so you can compare before restoring.
If an account still exists when you restore, it keeps its current credentials and keeps syncing — nothing to redo. If you removed an account after the backup, restoring brings it back: wallets and CSV imports come back fully working, while exchange connections that use an API key or OAuth come back needing to be reconnected before their next sync — a banner in the app will guide you through this.
Restoring a backup
On the History page, find the backup you want and click Restore.
Review the preview: Summ shows how your tax figures will change and lists the changes made since that backup, which will be reverted.
Confirm the restore. Your reports are recalculated automatically once it completes.
Before every restore, Summ automatically saves a backup of your current state (labelled auto in your backup list). If you change your mind after restoring, you can restore that snapshot to return to where you were.
Common scenarios
A hard sync brought in bad data. You created a backup called "Before Coinbase hard sync", then ran the hard sync and ended up with duplicates. Open History, click Restore on that backup, review the preview of what will be reverted, and confirm. Because your Coinbase connection still exists, it keeps its credentials — you are back exactly where you started.
You deleted a wallet by mistake. Restore your most recent backup. The wallet and all its transactions come back automatically, and because wallet addresses need no credentials, it keeps syncing straight away. The same applies to CSV file imports. A deleted exchange connection also comes back, but you will need to re-enter its API key or reconnect it before its next sync.
Frequently asked questions
What happens if something goes wrong during a restore?
Your current data is safe. A restore runs in three stages: first Summ saves a backup of your current state, then it loads your chosen backup into a separate staging area and validates it, and only after both succeed is your live data replaced. If the safety snapshot or the staging validation fails, the restore stops before ever touching your data.
How do backups interact with locked tax periods?
Transactions inside a locked period are included in your backups, but the lock itself is part of your current settings, not the backup. Two examples:
You create a backup, later lock a tax period, then restore that backup. The lock stays in place and transactions inside the locked period are left untouched — only data after the lock is restored.
You have a locked period, create a backup, remove the lock, then restore. Your transactions come back, but the lock does not — lock the period again if you still need it.
I'm at the backup limit — can I still restore?
Not yet. Every restore first saves an automatic safety snapshot, which needs a free slot. Delete an old backup, then restore.
Can I back up or restore while a sync is running?
No. Wait for the sync to finish, then try again. Only one backup or restore can run at a time.
Can I delete a backup while it's being created or restored?
No — a backup that is in progress, or currently being restored, cannot be deleted. Wait for the operation to finish.
Good to know
Changes since the backup are reverted. Any edits, imports, or syncs made after the backup date will be lost when you restore. Your other saved backups are never affected.
Backup limit. You can keep up to 10 backups, including the automatic pre-restore snapshots. At the limit you must delete an old backup before you can create a new one or restore.
Deleting a backup is permanent. Deleted backups cannot be recovered.
If you have any questions, reach out to our Support Team via the in-app chat. 😇