Business Central Migration & Support
for Perth, Melbourne, Sydney and Brisbane businesses.
Moving to Dynamics 365 Business Central from MYOB, Xero, Dynamics NAV, GP or Greentree. We handle the data, the integrations and the reporting, and we will tell you first whether the move is actually the right call.
- Independent Not a Microsoft reseller
- 18+ yrs Building business software
- Fixed Price scopes, no surprises
- AU-wide Perth-based, servicing Australia
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
Half the businesses asking about Business Central do not need it
An ERP migration is one of the more expensive things a mid-sized business can undertake, and it is frequently sold as the answer to a problem that is really an integration problem. If your accounting package is fine and the pain is that it does not talk to your job system, joining them costs a fraction of replacing them.
Business Central genuinely earns its place when you have outgrown what an accounting package can do: real inventory, multi-entity consolidation, manufacturing, project costing. We do not sell the licences, so we have no reason to push you either way.
What a migration actually involves
Moving the balances is the easy part. The rest is the project.
Opening balances take a day. What takes the project is the history you want to keep, the integrations that pointed at the old system, the reports built on tables that no longer exist, and the customisations nobody has looked at in years.
What has to move
- Your current system
- Open transactions
- Historical data
- Integrations
- Reports and customisations
One verified migration
Data extracted, mapped and validated against the source. Integrations rebuilt on supported APIs. Reporting reproduced and reconciled. Both systems run side by side until the numbers agree.
See how a project runsWhat you get
- Opening balances that reconcile on day one, not after adjustment
- History you can still search rather than an archive nobody opens
- Integrations and reporting working before the old system is switched off
Your Business Central migration, end to end
Three stages. Scoped and fixed-price before anything starts, and your current system keeps running until the numbers reconcile.
-
Week 0
Assess and scope
What you run now, what connects to it, how much history matters and what the customisations actually do. You get a written scope, a fixed price, and an honest view on whether to proceed at all.
-
Weeks 1-N
Migrate and parallel run
Data extracted, mapped and loaded. Integrations rebuilt. Reports reproduced. Both systems run together until the trial balance, the aged receivables and the stock position all agree.
-
Cutover
Go live and hand over
Cutover on a window you choose. Thirty days of support, monitoring on from day one, and the code, documentation and credentials handed over in your name.
The five moves into Business Central we are asked for
Each starts from a different place and none of them is a straight import.
From MYOB
Usually driven by inventory or multi-entity needs. The chart of accounts rarely maps cleanly, and payroll needs a separate decision.
From Xero
Often triggered by manufacturing or project costing. Xero is excellent within its scope, so the honest question is whether you have genuinely outgrown it.
From Dynamics NAV
Microsoft calls it a successor; treat it as a migration. Most customisations do not carry across and reports need rebuilding.
From Dynamics GP
A different data model and a long customisation history. The audit of what is still used usually pays for itself.
From Greentree or another ERP
Extraction is the hard part, not loading. Older ERPs guard their data, and getting a clean, validated set out is most of the work.
How the move usually goes
The data went across. Everything around it did not.
- Balances migrated but the reports were never rebuilt
- Integrations pointed at the old system and quietly stopped
- History was archived to a spreadsheet nobody can search
- Customisations were rebuilt before anyone asked if they were still used
How it should go
Nothing is switched off until its replacement reconciles
- Reporting reproduced and checked against the old system first
- Integrations rebuilt on supported APIs and documented
- A deliberate decision on history, with the cost of each option shown
- Every customisation assessed: keep, rebuild, or retire
Scoped and quoted before you commit. You own the code, the documentation and the credentials at the end of it.
Get a fixed-price scopeBusiness Central questions, answered plainly
Is Business Central the right step up from MYOB or Xero?
Sometimes, and often not. If the problem is that your accounting package cannot handle inventory, multi-entity consolidation, manufacturing or project costing, then a real ERP is the answer. If the problem is that three systems do not talk to each other, an integration costs a fraction of an ERP migration and solves it. We will tell you which one you have before you commit to either.
What is the difference between Business Central and Wiise?
Wiise is built on Business Central. It is the same Microsoft platform underneath, localised for Australian payroll, tax and banking, and sold with local support. The migration work is largely the same either way. The decision is about how much localisation and hand-holding you want, and what you are prepared to pay for it.
We are on Dynamics NAV or GP. Is this an upgrade or a migration?
Microsoft positions it as the successor, but treat it as a migration. The data model differs, most customisations do not carry across, and reports usually need rebuilding. Calling it an upgrade is how projects get under-scoped.
What happens to our customisations?
They get catalogued first: what is still used, what has become standard in Business Central since it was written, and what can be retired. Retiring is frequently the cheapest and best outcome, and it is the decision nobody wants to make without evidence.
How much history comes across?
As much as you need, and the answer should be a decision rather than a default. Open transactions and balances always. Full history is a choice between migrating it, keeping the old system read-only, or archiving it somewhere searchable. Each has a cost and we will lay them out.
Do you implement Business Central?
No, and we will say so early. Licensing and implementation sit with a Microsoft partner. We do the work around it: extracting and validating the data, rebuilding the integrations, reproducing the reporting, and building whatever the platform does not cover. Being independent of the licence sale is the point.
Sending your details…
You can stay on this page while we send it.
Tell us what you are running now
What system you are on, what connects to it, and what is driving the move. We will come back with a straight answer, including if that answer is not to migrate.
Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.
