Business Central Implementation: Two Approaches, One Proven Process
Fixed price or phased. The method stays the same.
ERP Werx implements Microsoft Dynamics 365 Business Central in two ways: a fixed-price implementation for small and mid-sized businesses, and a phased implementation for larger or more complex organisations. Both follow the same nine-phase method, from planning and kick-off to go-live, so nothing important gets skipped.
Which approach is right for you? If your requirements are clear and mostly standard, a fixed-price implementation gives you a known cost and a direct path to go-live. If you have multiple entities, complex operations or heavy integration, a phased implementation gives each stage the depth it needs. We’ll confirm which fits before you commit.
No sales deck. No juniors. We’ll tell you which approach fits, including when the answer isn’t us.
40 years in business. Business Central specialists since 1997. We fix what others can’t.
On this page Compare approaches The nine phases Keeping it on track Why ERP Werx FAQs
Fixed-price or phased: which Business Central implementation fits?
Same Microsoft platform, same senior team, same nine phases. The difference is scale.
| At a glance | Fixed-price implementation | Phased implementation |
|---|---|---|
| Best for | Small and mid-sized businesses with clear, mostly standard requirements | Larger organisations with complex processes, multiple entities or heavy integration |
| Scope | Agreed up front with written acceptance criteria | Defined through detailed analysis and a solution blueprint |
| Price | Fixed for the agreed scope | Set out in a written proposal once requirements are understood |
| Method | Nine phases, planning to go-live | Nine phases, delivered in stages |
| Training and support | Included in the proposal | Planned for each stage and role |
The nine phases of a Business Central implementation
Every project follows the same proven method. The depth of each phase scales with your business.
Project planning and kick-off
We agree goals, scope, timeline, roles and governance, so both teams know who does what before work starts.
Analysis: requirements gathering
We map how your business really works, including processes, exceptions, approvals, reports and integrations.
Design: solution blueprint (fit/gap)
We compare your requirements with standard Business Central and document what fits, what needs configuring and what needs building.
Development
We build only the gaps the blueprint justifies, such as extensions, integrations and reports. Standard first keeps future updates simple.
System configuration
We set up Business Central to match the blueprint: chart of accounts, posting setup, dimensions, workflows, approvals and user permissions.
Data migration
Master data and opening balances are cleansed, mapped, loaded and reconciled, with trial runs before the final cut-over.
Training and review
Role-based training on your own processes and data, so people practise real tasks before go-live.
Solution and user acceptance testing
Your team tests end-to-end scenarios against agreed acceptance criteria. Testing doubles as a rehearsal for go-live.
Go-live transition
Final cut-over, hands-on support as you go live, then post go-live support while the business settles in.
How we keep a Business Central implementation on track
Where implementations usually go wrong:
- Skipping analysis to save time, then paying for it in rework.
- Customising what standard Business Central already does.
- Migrating messy data and hoping to clean it up later.
- Squeezing training into the final week.
- Testing without real business scenarios.
- Support that disappears after go-live.
What we do instead
- Analysis before design, and design before build.
- Standard Business Central first, with extensions only where the blueprint justifies them.
- Trial data migrations, reconciled before cut-over.
- Role-based training on your own processes.
- User acceptance testing against agreed criteria.
- The people who built it support you after go-live.
Our promise: When Business Central gets difficult, we’ll tell you the truth and help you find a way through.
Why businesses choose ERP Werx to implement Business Central
40 years in business, so we fix what others can’t.
Exclusive focus on Business Central
No distractions, just expertise. If a partner needs to juggle products, you become the experiment.
Fixed-price implementations
Agreed scope, clear milestones and a price you know before you start. If they won’t fix the price, they won’t own the outcome.
Most experienced partner
Founded in 1986, we became the first certified NAV partner in Asia-Pacific in 1997.
Local senior team
Based in Melbourne and Sydney. Our entire team, including senior management, is technically experienced in Business Central.
Funding options
We’re Microsoft ECIF-certified, and project funding is available on most fixed-price models. Ask when we scope.
Project rescue specialists
Already burned by a partner? We regularly take over projects that are late, over budget or quietly broken.
Already live or mid-project, and it’s not working?
Don’t restart blind. We contain the risk first, and only re-implement when the evidence says that’s the cheapest safe path.
Explore Business Central RescueBusiness Central implementation FAQs
What is the Business Central implementation process?
A Business Central implementation follows nine phases: project planning and kick-off, analysis (requirements gathering), design (a solution blueprint with a fit/gap analysis), development, system configuration, data migration, training and review, solution and user acceptance testing, and go-live transition. ERP Werx uses the same method for every project and scales the depth of each phase to the size of the business.
What’s the difference between a fixed-price and a phased Business Central implementation?
A fixed-price implementation suits small and mid-sized businesses with clear, mostly standard requirements: the scope, acceptance criteria and price are agreed before work starts. A phased implementation suits larger or more complex organisations: it follows the same nine phases with deeper analysis and staged delivery, and is priced in a written proposal once requirements are understood.
How long does a Business Central implementation take?
It depends on your scope, data, integrations and how quickly decisions are made. A fixed-price implementation has clear milestones to go-live agreed in the proposal, while a phased implementation is planned in stages. ERP Werx gives you a realistic timeline once your requirements are understood, not before.
How much does a Business Central implementation cost in Australia?
Implementation cost depends on users, processes, data migration, integrations and training. With a fixed-price implementation, ERP Werx confirms fit and scope first, then fixes the price, so you know the cost before you start. Licences are separate and priced per user, per month — see current pricing on our Business Central page. Microsoft ECIF funding and project finance may help with the upfront cost.
What is a solution blueprint or fit/gap analysis?
A solution blueprint documents how Business Central will run your business. The fit/gap analysis compares your requirements with standard Business Central and shows what fits as is, what needs configuring and what needs building. It keeps development to what’s genuinely needed and makes scope and price clear.
Can we move from Dynamics NAV to Business Central at a fixed price?
Yes. ERP Werx offers fixed-price Business Central implementations for first implementations and legacy replacements, including Dynamics NAV. We’ve worked with NAV since 1997, so we know what to keep, what to retire and what to rebuild the Business Central way.
Is Business Central deployed in the cloud or on-premises?
Most new implementations use Business Central online, Microsoft’s cloud (SaaS) version, which Microsoft hosts and updates. On-premises deployment is still available for businesses with specific hosting requirements. We recommend the right deployment option during planning.
What’s included in a fixed-price Business Central implementation?
The signed proposal sets out the agreed scope, written acceptance criteria and milestones, plus implementation, training and post go-live support. New scope, third-party systems and licences, and delays on the client side are excluded, and any change outside the agreed scope is quoted before work starts.
Can you take over a Business Central implementation that’s gone wrong?
Yes. ERP Werx regularly takes over Business Central projects that are late, over budget or quietly broken. We stabilise what’s already there and recover it, usually without re-implementing. See Business Central Rescue & Recovery.