ERP implementation
ERP implementation that people actually use
What makes an implementation succeed
An ERP implementation is a business change project with software in it. The technical set-up matters, but projects succeed or fail on clear processes, clean data, enough time from the right people, and training that matches the work each person does.
That is why we start with process-led design and keep configuration as simple as the business allows. Every customisation is a long-term cost, so each one has to earn its place.
Implementation phases
- 01
Discovery and design
Confirm scope, map the future processes, and agree the design: entities, chart of accounts, item structure, workflows, approvals, reports and integrations. - 02
Configuration and build
Set up the system to the agreed design, build print formats and reports, and develop only what configuration cannot do. - 03
Data migration
Extract, clean and map master data and open transactions, load them in trial runs, and reconcile each load back to the source. - 04
Integration
Connect e-commerce, CRM, payroll, banking and other systems. See ERP integration. - 05
Testing
Users test end-to-end scenarios with real examples: a full order, a purchase, a stock adjustment, a month end. Issues are logged, fixed and retested. - 06
Training
Role-based training on the processes each person runs, with short written guides they can refer back to. - 07
Go-live
A cut-over plan with checkpoints, final data loads, a go or no-go decision, and a fallback if something critical fails. - 08
Support and improvement
Close support in the first weeks, then ongoing support, upgrades and a list of improvements for the next phase.
Data migration, done carefully
Decide what moves
Clean at the source
Trial loads
Sign-off
What you can expect from us
- A written scope with assumptions and exclusions for each phase
- A single project lead who knows your business
- Regular progress updates and a visible issue log
- Configuration documented so you are not dependent on us
- Your data, accounts and system access owned by you
- Honest advice when a request would add cost without value
Which systems we implement
Our deepest experience is with ERPNext, the open-source ERP, which we configure for Australian GST and BAS reporting and integrate with Australian payroll, banking and e-commerce. For other platforms, we can lead the process and data workstreams, build integrations, and manage the vendor or partner on your behalf.
Still choosing? Start with ERP selection or read about what drives ERP cost.
FAQ
Frequently asked questions
How long does an ERP implementation take?
It depends on scope: modules, entities, integrations, data quality and how much time your team can give. A focused first phase for a small business is much shorter than a multi-entity rollout. We give a timeline after discovery, with the assumptions behind it.
What are the phases of an ERP implementation?
Discovery and design, configuration, data migration, integration, testing, training, go-live, and support. We run them with sign-offs between phases so scope and quality stay under control.
How much of our team's time will it need?
More than most people expect. Process owners need to attend design workshops, help clean data, test scenarios and attend training. We agree the time commitment up front and plan around busy periods such as end of financial year.
Can you take over a stalled implementation?
Often, yes. We start with a short review of the design, configuration, data and open issues, then recommend whether to fix and continue, simplify, or re-plan. We are candid if the system itself is the problem.
What happens after go-live?
We provide close support in the first weeks, then ongoing support for questions, fixes, upgrades and improvements. Many clients also use our managed IT services so the devices, accounts and network around the ERP are looked after too.
Talk to us about your ERP or IT
Tell us where things stand and what is getting in the way. We will tell you plainly whether and how we can help.