Migrating from Alzex Finance
Alzex Finance (also known as “Personal Finance” and “Family Budget”) keeps a detailed transaction history with a deep category tree and multi-currency support — and you can move all of it into Svodly. Export the archive to CSV or Excel and import it: transactions, accounts, categories and counterparties will come across automatically, and the balances will compute themselves.
What gets moved
| From Alzex Finance | Into Svodly |
|---|---|
| Transactions (income, expenses) | Yes — date, amount, category, description |
| Transfers between accounts | Yes — linked into a pair |
| Currency exchange | Yes — as a transfer between accounts of different currencies |
| Accounts and their currency | Yes — created from the export |
| Categories — a deep tree | Yes — nesting is preserved; very deep branches are collapsed with a warning |
| Counterparties (payers / payees) | Yes — created from the “Payee” field |
| Tags | Yes — appended to the transaction description as a “#tag” suffix |
| Debts | No — tracked manually |
| Scheduled transactions | No — set up again |
| Attachments (receipts, photos) | No — they stay in Alzex |
Step 1. Export from Alzex Finance
- Open Alzex Finance on your computer (Windows, macOS or Linux) — a full export is easier in the desktop version.
- Go to File → Export (in the mobile versions — Settings → Export data).
- Choose the CSV or Excel (XLSX) format and save a file with all the transactions for the period you need.
In the export each transaction contains the date, type, account (two accounts for transfers), category with its full path, amount, currency, description, payee and tags — that’s enough for Svodly to reconstruct the accounts, categories and transfers.
Step 2. Import into Svodly
- Open Import in the sidebar (desktop or web version).
- Drag the exported file into the window — Svodly detects the Alzex format automatically.
- If auto-detection didn’t work, on the “Which app are you moving from?” step choose Alzex Finance.
- Check the column mapping — it’s filled in from the headers automatically.
- Choose the destination account for rows without an explicit account (if there are any) and review the preview.
- Confirm the import.
More on the import step, the mapping and the preview — in the “Import & export” section.
Mapping specifics
A deep category tree. Alzex allows categories of any depth (“Food \ Groceries \ Stores \ Lenta”). Svodly supports a nested tree and moves the hierarchy. If a branch is deeper than the UI can currently draw, the top segment goes into the parent category (“Food”), and the rest is glued together into a leaf with a readable path (“Groceries / Stores / Lenta”). Svodly shows a single combined warning about this in the import window.
Multi-currency accounts. In Svodly an account is kept in a single currency. If one Alzex account in the export has transactions in several currencies, Svodly splits them into one account per currency — there will be a warning about this too.
Tags. Svodly does not keep separate tags, so Alzex tags are moved into the
transaction description as a suffix #tag1 #tag2 — search and filtering by description
text keep working, so labels aren’t lost.
What won’t come across
- Debts. Alzex’s debt-tracking module has no direct equivalent in Svodly — such rows are skipped. Enter the outstanding debt balances by hand.
- Scheduled (planned) transactions. Svodly doesn’t move Alzex’s future records — set up recurring payments and budgets again.
- Attached receipt photos and attachments. They stay in Alzex.
Undo, if something went wrong
An import is saved as a separate batch. If you’re not happy with the result — open the log in the import window and tap “Undo”: all the transactions from this batch are deleted and the balances return to their state before the import. You can safely try again after fixing the source file.
Frequently asked questions
Alzex offers CSV and Excel — which should I choose?
Either format works. CSV is more reliable for large archives and is smaller; Excel is handy for opening and eyeballing before the import. Svodly understands both, including a Russian-language export (UTF-8 BOM, “;” separator).
In Alzex I have a category tree 4–5 levels deep. What happens to it?
Svodly supports a nested category tree and moves the hierarchy. Very deep branches that go beyond what the current UI supports are collapsed into a leaf with a readable path like “Groceries / Stores / Lenta” under a top-level category — Svodly warns you about this in the import window.
Will transfers between accounts be moved?
Yes. In an Alzex export a transfer has both accounts filled in (source and destination) — Svodly will link such rows into a single transfer. Currency exchange is moved as a transfer between accounts of different currencies, preserving both amounts and the rate.
What happens to Alzex tags?
Tags are appended to the transaction description as a “#tag” suffix — Svodly does not keep separate tags. Search and filtering by description text keep working, so labels aren’t lost.
Will debts and scheduled transactions from Alzex come across?
No. Alzex’s debts module and scheduled transactions don’t yet have a direct equivalent in Svodly — such rows are skipped with a warning. Outstanding debt balances and recurring payments can be set up by hand after the import.
Will the history for all years be preserved?
Yes. As many transactions are imported as there are in the exported file — there is no limit on the period in Svodly.
Where to go next
- Accounts — how accounts and transfers work in Svodly.
- Categories & counterparties — tidy things up after the import.
- Recurring transactions — set up planned payments again.
- Sync — pull the moved book to your phone.