Guide

ERP implementation: steps, timeline and pitfalls

Most ERP projects don’t fail because of the software. They fail because of how the rollout was planned. Here’s how to do it properly.

Buy the wrong ERP and you have an expensive, unused license. Buy the right ERP and implement it badly, and you have an expensive, unused system anyway — plus a staff that now distrusts anything labeled “new software.” The implementation is where ERP projects actually succeed or fail. This guide covers the real steps, a realistic timeline, and the pitfalls that derail projects before they ever reach go-live.

What “ERP implementation” actually covers

Buying ERP software is a purchase. Implementing it is a project — configuring the system around how your business actually works, moving your existing data into it, testing that it behaves correctly, training the people who’ll use it daily, and supporting them once it’s live. Vendors sell the software. Implementation is the part that determines whether that software ever becomes useful.

The implementation stages

1. Discovery and scoping

Before any configuration starts, someone needs to document how your business actually operates today: the workflows, the approval chains, the reports people rely on, the exceptions to the “normal” process. Skipping this stage is the single most common cause of ERP projects that technically launch but don’t fit how the business works.

2. System design and configuration

This is where the ERP gets configured to match the scoped workflows — modules enabled, approval rules set, user roles defined, custom fields added where your business genuinely needs something the out-of-the-box system doesn’t have.

3. Data migration

Existing data — customers, inventory, historical transactions, supplier records — has to move from old systems (often a mix of spreadsheets and legacy software) into the new one. This sounds mechanical. It rarely is: old data is messy, duplicated, and inconsistently formatted, and cleaning it up properly takes real time.

4. Testing

Before anyone’s daily work depends on the system, it needs to be tested against real scenarios — not just “does the button work,” but “does a real order, with a real discount and a real backorder, flow through correctly end to end.”

5. Training

The people who’ll use the system daily need real training on their specific workflows, not a generic walkthrough of every module. Under-investing here is one of the fastest ways to get a system that’s technically live but practically ignored, with staff quietly reverting to spreadsheets.

6. Go-live

The cutover from old systems to new. Usually phased by department or module rather than switching everything at once, so problems surface in a contained way instead of breaking the whole business simultaneously.

7. Post-launch support

The weeks immediately after go-live are when real usage surfaces issues that testing didn’t catch. A support plan for this period — someone available to fix problems fast — matters as much as the launch itself.

A realistic timeline

Business size / complexityRealistic timeline
Small business, single location, standard processes2–4 months
Mid-size business, multiple departments or locations4–8 months
Larger or more complex operation, heavy customization8–14+ months

Vendors sometimes quote the lower end of these ranges to win the deal. Treat any ERP timeline under two months with real skepticism — proper discovery and data migration alone rarely fit in that window.

Common pitfalls

Who should run the implementation

Large ERP vendors often hand implementation to a separate certified partner, which can mean the team who sold you the software isn’t the team building it — a common source of miscommunication. A build-and-implement team that scopes, builds and supports the same system end to end has fewer handoffs for things to get lost in.

Budgeting for implementation, not just the license

The software license or subscription is usually the smaller number. Discovery, configuration, data migration and training are where real implementation budget goes, and they’re the costs businesses most often underestimate when comparing quotes. A cheap license attached to a rushed implementation tends to cost more in the end — in lost staff time, bad data, and a second project to fix the first one.

Questions to ask before you start

An implementation partner who answers these clearly, before the contract is signed, is a reasonable proxy for how the actual project will go.

How Floral Gray approaches ERP implementation

We scope the workflow before we configure anything, handle data migration as a dedicated stage rather than an afterthought, and stay involved through go-live and the weeks after — the same team from discovery to support. See our ERP development services, or book a free consultation to talk through your current setup.

Keep reading