What is included
What an ERP implementation actually covers
Configuration is the smallest part of the job and the least likely thing to go wrong. The effort, and the risk, sit in the data, the integrations and getting people to use the system once it is live.
01 — ConfigureConfiguration & solution design
Your chart of accounts, entity structure, approval rules, document layouts and reporting, built in standard functionality first. Custom development is the last resort rather than the opening move, because every customisation is something you pay to carry through each upgrade.
- › Chart of accounts and entity structure
- › Approval workflows and user roles
- › VAT, corporate tax and e-invoicing setup
- › Document, form and report layouts
- › Standard first, customisation justified in writing
Compare the platforms →02 — MigrateData migration & cleansing
At minimum: chart of accounts, customers, suppliers, items, opening balances, open invoices and open purchase orders. Historical transactions are optional and carry a cost, so most businesses migrate balances plus one or two years. Cleaning this data is usually the longest single task in the project.
- › Master data extraction and de-duplication
- › Opening balances reconciled to your ledger
- › Open invoices and purchase orders carried over
- › Two rehearsal loads before the real one
- › Signed off by finance before cutover
Where this happens →03 — ConnectIntegration & custom development
Where the ERP has to talk to something else — a bank, a payroll platform, your website, a site application or equipment on the floor — we build and test the interface rather than leaving it as a monthly manual export somebody has to remember.
- › Bank, payroll and tax platform interfaces
- › E-commerce and website integration
- › Custom modules where the standard genuinely does not fit
- › API work documented and handed over
- › Every interface tested at real volumes
Custom development →04 — Go liveTraining, cutover & hypercare
Role-based training on your own data, a parallel run where the risk warrants one, then cutover with consultants available. We stay close through the first month-end, which is the point at which an implementation is genuinely tested for the first time.
- › Role-based sessions, not a single system tour
- › Training on your data, not a demo set
- › Cutover plan with a rollback position
- › Thirty days of hypercare after go-live
- › Handover into a support contract
Support & AMC →