ERP Implementation: What to Expect (and Why They Fail)
- Eddie Bearnot
The five stages of an ERP implementation
Every implementation moves through the same arc. Knowing the arc up front removes surprises and shows you where attention pays off most.
Stage one, planning and discovery
Your partner learns how the business runs today, order to cash, procure to pay, plan to produce, then sets scope, success measures, timeline, and budget. Depth here prevents most trouble later. A vague start is the seed of a late, over-budget finish, so this stage earns real time.
Stage two, build and configuration
The team shapes SAP Business One to your workflows, chart of accounts, item masters, bills of materials, warehouses, pricing, and approvals. Good partners configure to fit and add customization only where the value is real, because every custom feature adds cost to test, maintain, and upgrade later.
Stage three, data migration and testing
You and your partner extract, clean, map, and load master data and open transactions, then test the system against real scenarios end to end. Most hidden risk lives in the data. Duplicate customers, inconsistent part numbers, and stale records erode trust in the numbers from day one, so clean data early. Testing is the rehearsal, and a system proven on real orders before go-live is a system people trust after.
Stage four, go-live
Final data loads complete, operations move to SAP Business One, and the first weeks run under intensive support. A deliberate cutover plan with a fallback keeps go-live a planned event, not a scramble. Whether you switch everything at once or phase the rollout by site or module depends on your operation and your appetite for risk.
Stage five, optimization and growth
After the system settles, attention shifts to getting more from the platform, sharper reports, added automation, and extension to new sites as the business grows. A good implementation is the start of the return, not the end of the project. Many clients add capabilities in year two and beyond, warehouse automation, deeper reporting, or a connected storefront, on the same stable foundation.
One decision to make early, cloud or on-premise
Deployment shapes cost, timeline, and IT effort, so settle the direction during planning rather than mid-build. Cloud suits lean teams wanting predictable operating cost. On-premise suits specific control and data-residency needs. For a full comparison, see our cloud versus on-premise guides for finance leaders and IT leaders.
Who does what during an implementation
An implementation is a shared effort. Setting the split up front prevents gaps and keeps momentum:
- You name an executive sponsor and a project lead empowered to decide
- Your team documents processes and validates the configuration
- Your team owns data cleansing calls, with the partner doing the heavy lifting
- Your partner configures, migrates, tests, trains, and runs the cutover
- Both sides agree scope, timeline, and success measures before the build
Clear ownership keeps a project moving. Gaps in ownership are where timelines slip.
How to know you are ready to begin
A project starts well when the groundwork is in place. Before kickoff, confirm you have:
- An executive sponsor with authority and time for the project
- A clear reason for the change the whole team understands
- A first read on data quality, and who owns the cleanup
- Agreement on scope and what go-live must deliver
Readiness is not perfection. A short, honest gap check before you start is worth more than any assurance made mid-project.
Why some ERP implementations fail
The stages are predictable, and so are the failure modes. Implementations rarely fail on the software. They fail for reasons within your control, vague scope, poor data quality, no executive sponsor, thin training, a rushed cutover, or a partner chosen on price alone. We cover the patterns and the fixes in depth in Why ERP Implementations Fail (and How to Get Yours Right). The short lesson, treat the human and planning work as seriously as the technical work, and most failure risk drops away.
How we run implementations at Third Wave
We understand the stakes. A stalled project drains your team, your budget, and your confidence. Our team has guided mid-market manufacturers and distributors through ERP implementations for 23+ years, across 500+ implementations, with a 100% go-live record and 98.7% client retention. As an SAP Gold Partner, we run a disciplined, phased method built around your operations, and we stay beside you from planning through hypercare. Getting started is straightforward:
- Take the ERP assessment or book a consultation
- Get a tailored plan and timeline built around your operations
- Go live with our team beside you, and grow from there
What a poor implementation costs
Skip the method, and the bill arrives later. You pay again to correct a rushed configuration. You run two systems for months while a delayed go-live drags on. You watch a capable team return to spreadsheets because the new system never fit their work. The implementation shapes years of operations, so the plan deserves the weight the decision carries.
What good looks like a year in
Picture the business twelve months after a clean go-live. Your team works from one source of truth, the reports arrive in real time, and you trust the numbers. Adding a site or a product line is a planned step, not a scramble. Finance closes faster, operations sees true inventory, and leadership decides on current data. The system runs quietly in the background while you run the company.
The gains compound. Onboarding a new hire takes days rather than weeks, because the process lives in the system. Month-end arrives without dread. The business you pictured at signing is the business you run.
Frequently Asked Questions
What is an ERP implementation?
An ERP implementation is the process of configuring a new system, migrating your data, testing, training your team, and going live. For a mid-market manufacturer on SAP Business One, the work runs five stages across about three to six months.
How long does an ERP implementation take?
About three to six months for most mid-market manufacturers and distributors. Scope, data condition, and the number of sites move the date more than the software. Our How Long Does an ERP Implementation Take? (And What It Costs) breaks the schedule down phase by phase.
Why do ERP implementations fail?
Most failures come from planning and people, vague scope, poor data, no executive sponsor, thin training, or a rushed go-live. Each cause is preventable. Our guide on Why ERP Implementations Fail (and How to Get Yours Right) covers the patterns and the fixes.
What is an ERP go-live?
Go-live is the moment the business begins operating on the new system. A calm go-live follows testing and training and runs under hypercare, a stretch of intensive support to settle operations quickly. Our ERP Go-Live: What to Expect (and How to Avoid a Rough Launch) covers the run-up and the day.
Do we need to stop operating during the project?
No. A well-planned implementation runs alongside live operations, and a phased cutover keeps production and fulfillment moving with minimal disruption.
Scope your implementation
See what your project looks like before you commit to a date or a budget. Take our ERP assessment to gauge readiness, or book a consultation to map a plan built around your operations.