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.

Svodly.ru

View

Exporting transactions: on the “Transactions” tab set a filter (here — the “2026” period), open the “Import and export” menu — the arrow-into-tray icon to the right of the filters — and pick “Export”. Then choose a format (CSV, XLSX or JSON) and press “Export”: the file lands in Downloads and contains exactly the transactions the filters show.

Export on the phone: choose a format (CSV, XLSX, JSON) and save through the system dialog.

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. Exports of the supported apps (ZenMoney, 1Money, Elba, Alzex, the template) are parsed on the phone via the migration tiles; import an arbitrary XLSX spreadsheet on a computer or on the web — the transactions reach the phone via the cloud.
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.
Bank statement (1CClientBankExchange) — a kl_to_1c.txt file from your online bank. Recognized automatically — see “Importing a bank statement” below.

Steps

On the Transactions tab open the Import and export menu — the arrow-into-tray icon to the right of the filters — and pick Import. On the phone — the import icon in the Transactions screen header.
Drag a file into the window or tap “Choose a 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.

Importing transactions: on the “Transactions” tab open the “Import and export” menu — the arrow-into-tray icon to the right of the filters — and pick “Import”. Then “Choose a file”: Svodly parses the statement columns itself (date, amount, category, counterparty, description), “Preview →” shows the transactions to come, and “Import 14” adds them as a single batch — the counter in the header goes from 5,346 to 5,360.

Import on the phone: choose a file → check the column mapping → preview → confirmation.

Undo an import

Each import is saved as a separate batch and goes into the log: Settings → General → “Import and export”. The table shows the date, the file name and how many records were loaded.

To undo it, press “×” in the row of that import and confirm “Delete”. All the transactions of that batch are marked deleted in one action, and the account balance returns to its state before the import. Categories and counterparties the import created along the way stay where they are.

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. On the desktop the app takes a book snapshot before the rollback, so you can change your mind afterwards too: an undone row gets a restore-from-backup button in the log.

Undoing an import: “Settings” → the “General” tab → the “Import and export” card. The log holds a row for the loaded file (date, name, record count); the “×” at the end of the row opens the “Delete import data?” confirmation, and after “Delete” all 14 transactions of the batch are removed in one action.

Undoing an import is available on the desktop and web for now

Мобильный

The phone shows the import log (“Settings” → “Import and export” → “History”), but a batch is rolled back from the desktop or the web app — on the same book through the cloud.

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, Alzex Finance 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.

Transactions arrive already labelled: the category and counterparty from the export are put on every row, not merely created in the references. A category from the file outranks your rules, the counterparty's history and the built-in dictionary — you get your own labelling, not one guessed from scratch. If a category in the file does not match the direction of the transaction (an expense category on an income), it is not applied, and the row can still be picked up by the rules. Transfers have no category — only a counterparty.

Importing a bank statement (1C format)

Besides spreadsheets, Svodly accepts a bank statement in the 1CClientBankExchange format (a kl_to_1c.txt file) — a universal Russian standard that almost any bank exports: Sberbank, T‑Bank, Alfa-Bank, VTB and others. In the import wizard, on the “Where are you moving from?” step, pick the “Bank statement · 1C format” tile and choose the file.

Svodly recognizes income and expenses, creates and matches counterparties by INN.
Auto-categorization by your own rules, by counterparty history and by keywords in the payment purpose (rent, taxes and contributions, acquiring, payroll): payments to a familiar recipient land in the same category as before, and typical ones are recognized even on the first import. Your rules take precedence over both history and the built-in dictionary — the fastest way to sort a large statement.
Dedup: re-importing the same document does not duplicate transactions.

The preview shows how many transactions were recognized and how many counterparties are created/matched by INN; you can confirm the import or open the file as a regular CSV/XLSX. Statement import works on desktop, on the web and on the phone — the Windows-1251 encoding from an online bank is read right on the device.

The import wizard (“Where are you moving from?”): among the sources is the “Bank statement · 1C format” tile. Pick it and choose the kl_to_1c.txt file — Svodly recognizes the transactions and matches counterparties by INN.

On the phone: Transactions → import → the “Bank statement · 1C format” tile → choose the kl_to_1c.txt file → preview and confirm.

Ready-made parsers for specific banks (PDF statements from Sber, T‑Bank, Alfa) are not available yet — that's post-v1.0 work. If your bank can't export the 1C format, save the statement as CSV or Excel: 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 Import and export menu (the arrow-into-tray icon to the right of the filters) → Export.

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.