ERP Implementation: Timeline and Real Costs

What ERP Is — and What It Is Not

ERP (Enterprise Resource Planning) software integrates your core business processes — finance, HR, procurement, supply chain, sales, and operations — into a single system with a shared database. The value is not the software itself. The value is having one source of truth across your organisation: your finance team sees the same data as your operations team, your sales team sees inventory in real time, and management reporting pulls from a single consistent dataset rather than five different spreadsheets.

What ERP is not: a silver bullet, a quick win, or something that improves by being switched on. The software is a framework. The value depends entirely on how well you design and configure it to reflect your actual business processes — and on whether your team adopts it properly.

The Three Implementation Paths: Cloud, On-Premise, and Custom

Cloud ERP (Microsoft Dynamics 365, SAP S/4HANA Cloud, Oracle Fusion) means the software runs on the vendor's infrastructure, updates automatically, and is paid for by subscription. Implementation costs are lower because you are not managing infrastructure, but the software imposes its own processes — which may or may not match yours. On-premise ERP means you host and manage the software yourself, giving you full control but significant infrastructure cost and internal IT overhead.

This model is increasingly rare for new implementations. Custom ERP means building a bespoke system tailored exactly to your processes. Cost and timeline are highest, but so is fit.

The right choice depends on how standard your processes are: if your operations are similar to your industry peers, cloud ERP is almost always the right starting point.

What a Realistic ERP Implementation Timeline Looks Like

A mid-market cloud ERP implementation — for a business of 100–500 employees — typically takes six to twelve months from project kick-off to go-live. Discovery and process design takes four to eight weeks: mapping your current processes, identifying gaps, and designing how the ERP will reflect your business. Configuration and customisation takes eight to sixteen weeks: setting up the system, building any required custom modules, and integrating with existing systems.

Testing takes four to eight weeks: user acceptance testing, data validation, and stress testing. Go-live preparation — data migration, training, and cutover planning — takes two to four weeks. The most common timeline failure is underestimating the process design phase and skipping adequate testing.

Where the Budget Goes — and Where It Blows Up

Software licensing is typically 20–35% of total ERP cost. Implementation services — consultancy, configuration, and custom development — account for 40–60%. Data migration is frequently underestimated and can represent 15–25% of total project cost: cleaning, transforming, and validating historical data from legacy systems is time-consuming and technically complex.

Training and change management is the most commonly cut budget line, representing 10–15% of a well-run project. This is where implementations fail: a perfectly configured system that nobody uses correctly delivers no value. The budget typically blows up in three areas: scope creep during configuration (every 'small' customisation request adds cost), data migration complexity (legacy data is almost always messier than expected), and go-live issues that require emergency consultancy at premium rates.

The Five Reasons ERP Projects Fail

Insufficient executive sponsorship: ERP touches every department, and cross-functional decisions require authority. Without a C-level champion who can resolve conflicts and enforce adoption, implementations stall on departmental disagreements. Skipping process redesign: ERP is not a technology project, it is a business process project.

Companies that configure the ERP around their existing (often broken) processes miss the opportunity to fix them, and end up with an expensive system that automates the wrong things. Underestimating data migration: migrating data from legacy systems requires skilled technical resources, significant validation work, and time. Budgeting for it as an afterthought is one of the most common causes of go-live delays.

Under-investing in training: users who do not understand the system revert to spreadsheets. Resistance is not obstinacy — it is the predictable result of inadequate preparation. Poor change management: employees need to understand why the change is happening, what is expected of them, and what support is available.

This requires proactive communication, not a training session the week before go-live.

Microsoft Dynamics 365 vs SAP vs Custom ERP: A Practical Guide

Microsoft Dynamics 365 is the strongest choice for businesses already using the Microsoft ecosystem (Office 365, Teams, Azure, Power Platform). Its integration with Power BI, Power Automate, and the rest of the Microsoft stack is genuinely differentiated. It is particularly strong for professional services, distribution, and manufacturing.

SAP is the market leader for very large enterprises with complex, global operations. Its depth and breadth are unmatched — but it comes with corresponding implementation complexity and cost. For mid-market businesses, SAP is often over-engineered.

Custom ERP is justified when your processes are genuinely unique, when off-the-shelf systems would require so much customisation that you lose the support and upgrade benefits, or when you are in a niche industry not well served by major vendors. The decision should be driven by a process fit assessment, not by vendor relationships or brand preference.