Ten stages, and at each one what you provide and what we provide. We publish no durations here, because none have been agreed with you yet and a number on this page would become a promise.
How long an implementation takes depends on how many entities you run, how clean the data is, and how quickly decisions get made on your side. We will give you a schedule during scoping, against your situation. Anything printed here would be a guess dressed up as a commitment.
Your opening balances are agreed against the system you are leaving, line by line, before a single transaction is posted in Boongon. If the two do not agree, the migration does not proceed — you are told which accounts differ and by how much.
Some stages overlap in practice. None of them are skipped.
We walk your actual processes, not a questionnaire. Which entities exist, which currencies, where approvals sit today, and which of your current systems has the version of the truth everyone believes.
You provide Access to the people who run each process, and a list of the systems in play.
We provide A written summary of how your processes map onto Boongon, including where they do not.
The approval rules, the chart of accounts, the entity structure and who may see which company. This is the part that determines whether the controls hold later.
You provide Your delegation of authority, and a decision on who approves what.
We provide A control design you sign off before anything is configured.
The design is built in a sandbox environment, separate from anything live. Chart of accounts, tax setup, approval rules, document templates, users and permissions.
You provide Review and correction as it takes shape.
We provide A configured sandbox you can open and use.
Opening balances, customers, suppliers, products, open orders and open items. Imported from CSV, JSON or Excel with a guided mapping, and reconciled against what you sent.
You provide Extracts from your current system, and someone who can answer questions about the data.
We provide A mapping, a trial import, and a reconciliation you can check line by line.
What connects, and what does not. Boongon has no public write API and no outbound webhooks today, so integration means import, export and the read-only connector. We say so early rather than late.
You provide The list of systems that must exchange data, and how often.
We provide An honest assessment of what is possible now and what would have to wait.
Your processes run end to end in the sandbox against your own migrated data, including the ones that fail. A purchase that breaches its budget, an invoice outside tolerance, an approval that has to be refused.
You provide The scenarios that matter to you, including the awkward ones.
We provide A test pass against those scenarios, and the fixes it produces.
Training by role against your own configuration, not a generic tour. Approvers learn the approval screen; the finance team learns the close.
You provide Time from the people who will use it.
We provide Role-based sessions and written guidance for your setup.
A dated plan for the switch: final balances, the last transactions in the old system, the first in Boongon, and what happens if something is wrong on the day.
You provide A decision on the cutover date and a freeze on the old system.
We provide The plan, the final migration and a rollback position.
Close attention through the first period end, which is when the questions actually arrive.
You provide Early sight of anything that looks wrong.
We provide Support through the first close.
Reviewing what was deferred, tightening rules that turned out to be too loose or too strict, and revisiting anything the roadmap has since delivered.
You provide A periodic review.
We provide The changes it produces.
Detect, map, validate, preview, then apply. The preview is the point: you see what would be written, and what would be rejected, before anything is.
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
These are the ones that change an implementation plan most, and the ones we would rather answer before a contract than during one.
Migration effort is driven almost entirely by this. A clean chart of accounts and reliable open items make it straightforward. Years of workarounds do not.
Including dormant ones, branches treated as separate books, and the entity somebody set up for a single contract. They all have to be decided on.
Tell us early. Without a public write API, some integrations are import and export rather than live, and that changes the design.
The core is not tied to one country, but statutory localisation is built region by region. Ask about yours and we will tell you honestly where it sits.
A scoping conversation is more useful than a proposal. Bring your entity structure and your worst process, and we will tell you what a rollout would actually involve.
Anything you want to ask about Boongon? A real person reads these.