Moving your data into Flowtly
Most of what a company brings when it switches is history: clients, contracts, invoices already issued, costs already booked, bank statements. This page lists what Flowtly loads in bulk, how a load is checked before it writes anything, and what you still set up by hand.
What loads in bulk
Each of these takes a whole register or spreadsheet in one go, not one record at a time.
- Clients and their contacts, matched on the ID each one has in your current system, so a second run updates them instead of creating duplicates.
- Contracts, linked to the clients loaded before them, and the instalment plans that belong to them.
- Invoices you have already issued, with their original numbers. They arrive as issued: nothing is emailed to the client again and, for Polish entities, nothing is sent to KSeF again.
- Supplier invoices from a register, without uploading every PDF, each placed in the month the cost belongs to.
- Bank history from MT940 statement files. Importing the same statement twice does not create duplicate rows.
- Assets and equipment, with their categories, locations and attributes such as area or floor, and file-less records of guarantees and insurance policies.
- A year's staffing plan from your allocation sheet.
- For Polish entities, sales invoices already in KSeF, imported automatically from a date you choose.
Every load is checked before it writes
- A dry run comes first. It reports, row by row, what would be created, updated or skipped, and writes nothing.
- A load can be run again. Rows are matched on your own references, such as an invoice number or a client ID, so a run that stopped halfway is simply repeated.
- An invoice register can carry its own total. If the rows do not add up to it, the whole batch is refused before anything is written.
- A row that cannot be matched, such as a supplier tax ID Flowtly does not know, is reported instead of guessed.
Who runs the load
You can run the loads yourself from a connected AI assistant through Flowtly's MCP server, pointing it at your own export files. As part of implementation, our team can run them with you. Talk to us about what you are moving from before you start.
Where costs come from, and what KSeF does not replace
For Polish entities, supplier invoices sent through KSeF arrive in Flowtly's incoming invoices. Other supplier invoices are uploaded or loaded from a register, and bank lines come from your bank connection or statement files. KSeF does not replace your accounting system: your accountant keeps the books in Comarch Optima or another program, and Flowtly hands them ready-to-import files.
What you set up by hand
- People. Each colleague is added and invited one at a time, in Flowtly or by asking a connected assistant.
- Opening leave balances and carry-over, entered per person.
- Approval rules and permission groups, which reflect how your company works rather than what your old system held.
- Your accounting ledger. Flowtly exports files to the Polish programs Comarch Optima, enova365, Symfonia and Wapro; it does not import their books.
Roll out one module at a time
An administrator can switch modules such as leave, bookings, budgets or invoicing off for the whole organisation and on again when the team is ready, so you can start with one area and add the next one later. Switching a module off does not change the price: you are billed per account on your plan.
Plan your move with us
Tell us what you are moving from and we will go through your exports with you. Or start a 14-day trial and run a dry load into it first.