ERP Implementation Cost and Timeline

Article LavisTech · · 2 min read

Quick answer

A focused custom ERP slice — one site, one core workflow, live — is often three to six months. A fuller system with stock, jobs, accounts and reporting is nine months to well over a year, usually in phases. Package implementations are not automatically faster: data migration, training and the gap between “configured” and “how we actually work” eat the calendar either way.

Part of our guide to What Is Custom ERP?.

Where the months go

PhaseWhat is happeningTypical span
DiscoveryProcess, data, integrations, definition of the first live slice2 to 6 weeks
First sliceBuild, migrate a usable data set, train the people who will actually use it8 to 16 weeks
Parallel runOld and new side by side until the numbers match2 to 6 weeks
Next modulesAccounts, production, branches — one at a timeOngoing

The phase that gets skipped is parallel run. Skipping it is how you go live on a Monday and discover on Thursday that stock was never right.

Costs that are not the software

  • Cleaning and migrating data. Always larger than the first conversation implied.
  • Staff time. Someone from the business has to sit with the build. If they cannot, the system will encode guesses.
  • Integrations — Tally, banks, e-commerce, weighing scales, whatever is actually in the room.
  • Training and a written operating procedure. Software without that becomes optional in a month.

Licence fees on a package are visible. These items are not, and they appear on custom and package projects alike. See custom versus SAP versus Odoo before you compare two quotes that are not measuring the same thing.

For the broader “what are we even building” question, start at what custom ERP is.

Related knowledge

How LavisTech can help

← All ERP & Business Systems pages

Want this built properly?

We design and build these systems for growing businesses. Tell us the problem and we will scope it honestly.

Start a Conversation