What decides whether a migration goes well is whether your balances agree with your old system on the day you switch, and whether you can show your auditor why. The software is the easy part.
They put up with it because moving looks worse. That calculation is usually made without anyone naming what the current arrangement actually costs.
These are the six we hear most often on a first call. If more than two of them are familiar, the question is not whether to move but when.
The business event and its accounting consequence are the same record here, so there is nothing to reconcile between systems that should have agreed in the first place.
Open the account, the customer, the supplier, the asset or the item and read the posted lines behind the balance, each linked to the document that produced it.
Entities stay separate where the law needs them separate and roll up where you need the group, with intercompany eliminations applied rather than remembered.
A posted document cannot be amended. The correction is a linked reversing entry and both sides stay visible, which is the version an auditor can follow.
Stock movements write to the ledger as they happen rather than in a month-end journal, so the two are the same set of records seen from two angles.
Statutory returns are built from posted transactions and exported in the format the Bureau expects. You still file them.
Nothing depends on Boongon until your own finance team has read the trial load and said they believe it. Going live is the second time the balances are checked, not the first.
We publish no duration here. It depends on how many entities you run and what condition the data is in, and a number on this page would become a promise before anyone had looked at your books.
Seven steps. The first and the last are the same check.
The import shows you the rows that would be created and the rows that would be rejected, with the reason, before a single record is committed.
Customer import · preview
1,284 rows
Nothing is written until you accept this preview
The run
A rejected row names what is wrong with it, so the fix happens in your file rather than in the ledger
Customers, suppliers, items, employees, invoices, orders, credit notes, payments, receipts, journals, fixed assets, projects, stock movements and more. Column names are matched for you, and where a heading matches nothing, the assistant proposes a mapping you approve.
There is no live connection to Xero, QuickBooks, Sage or anything else. Data moves by export and import. If your plan depends on a two-way sync with the system you are leaving, say so on the first call, because it is not something Boongon does.
A migration is finished when these agree, not when the data has finished loading. They are run against the trial load and again after cutover.
Every account, both systems, same date.
Aged receivables agree in total and customer by customer.
Aged payables agree in total and supplier by supplier.
Each account reconciles to the same statement balance.
Stock valuation agrees with the control account.
Output and input VAT agree with the last filed return.
A page like this usually shows what customers gained in their first year. Boongon is early and has none to quote, so rather than borrow a number or invent one, the proof here is the reconciliation itself. When we have results a customer is willing to stand behind, they will appear with their name on them.
Opening stock and work in progress take longer than the ledger does, because they are the figures nobody has had to defend in a while. Plan for them first rather than discovering them in the last week.
These come up on nearly every first call, so they are answered here rather than three meetings in.
For a period, yes, and that is deliberate. A trial load happens in a separate environment while your current system stays live, so nothing depends on the new one until the balances agree and you have said so.
You decide how much comes across. Most groups bring opening balances, open receivables and payables, stock, and one or two prior periods for comparison. Bringing ten years of detail is possible and usually not worth the time it costs.
No. There is no live connection to Xero, QuickBooks, Sage or anything else. Data moves by export and import, across 33 record types, with the columns matched for you and a dry run before anything is written.
Then you are not live yet. The trial load produces a downloadable list of the rows that were rejected and why, so the gap is a list of specific records rather than a difference you have to hunt.
We do not publish a number, because it depends on how many entities you run and what condition the data is in, and a figure on this page would become a promise. You get a schedule during scoping, against your actual situation.
You know your data and we know the system, so it is shared. What we will not do is take a folder of spreadsheets away and hand back a finished system you have not checked.
The fastest way to find out whether this is a three-week move or a three-month one is to look at your actual data together. Bring a trial balance and a list of your entities.
Moving off another system? The awkward questions are the useful ones — ask away.