Import & export
Svodly works with standard formats — CSV, JSON and XLSX. Load your history from a bank, export data to Excel, move a book to another device without the cloud — all through ordinary files.
Importing transactions
If you are moving from a spreadsheet or a bank statement, the import will immediately pick up the columns by their Russian and English headers and suggest a mapping.
Supported formats
- CSV — comma, semicolon or tab as the separator. The encoding is detected automatically (UTF-8, Windows-1251, OEM-866).
- XLSX — an Excel file, the first sheet. Headers in the first row.
- JSON — the Svodly format: an export from this same app, the full contents of a book. Importing replaces the current book, it does not merge with it.
Steps
- Open Import in the sidebar.
- Drag a file into the window or tap “Choose file”.
- Check the column mapping: date, amount, category, counterparty, note. Svodly fills in the mapping itself, but you can change everything.
- Choose the destination account — where the imported transactions should go.
- Review the preview — the first 20 rows turn into transaction cards. If something is off — go back and change the mapping.
- Confirm the import.
The mapping is saved on the device for each source. The next time you import a statement from the same bank, the settings will be picked up automatically.
Undo an import
Each import is saved as a separate batch with an entry in the log. If something went wrong — open the log in the import window and tap “Undo”. All the transactions from this batch are deleted in one action, and the account balance returns to its state before the import.
You can also undo older batches — for example, change your mind a week later. Undoing does not touch other transactions added manually between the import and the undo.
Duplicates
If the file contains transactions that are already in Svodly (you imported a statement twice in a row) — the app recognizes them and marks them in the preview. You can skip the duplicates or confirm them — the choice is yours.
A duplicate is determined by a match of date, amount, account and description. If two transactions simply have the same amount on different days, those are separate records and are not considered a duplicate.
Moving from another bookkeeping app
Moving from another app — ZenMoney, CoinKeeper, 1Money, Elba or a regular Excel spreadsheet? For popular apps there are step-by-step guides for moving your history without loss — see the “Migrating from other apps” section.
Import without bank parsers
Svodly does not yet have built-in parsers for specific banks. Any statement first needs to be saved as CSV or Excel from the bank’s app, after which the import works without trouble. Most banks offer an export “as is”; Svodly parses the column mapping automatically.
Exporting data
Export is useful in two scenarios: a backup (save the state of a book to a file) and an export for analysis (open in Excel or hand to an accountant).
Export formats
- JSON — the full book with all entities: accounts, transactions, categories, counterparties, budgets. Suitable for a backup and for moving between devices.
- CSV — a flat list of transactions in the encoding you need. Suitable for analysis in Excel or Google Sheets.
- XLSX — an Excel table with three sheets: transactions, accounts, categories.
Full book or a selection
You can export the whole book or the result of the current filtering:
- Full book — Settings → Export. Choose a format and save the file.
- Selection — on the Transactions tab apply filters (period, category, account), then the Export selection button.
A regular JSON backup is a simple way to play it safe. The file is small (tens of KB for a typical book over a year), and you can put it next to your photo archive or upload it to any cloud of your own by hand.
Moving a book between devices without the cloud
The simplest way to move is through a JSON file:
- On the old device: Settings → Export → JSON.
- Send the file to the new device (a messenger, AirDrop, a flash drive).
- On the new device: Import → JSON, choose the file.
Importing a JSON file replaces the contents of the current book. If the book already has transactions — they will disappear. If you need to merge two books — use CSV import: it adds transactions rather than overwriting them.
Where to go next
- Sync — if there are a lot of moves between devices.
- Shared access — if a book is kept by several people.
- Security — where the book file lives and who can see it.