ERP implementation costs: what mid-size companies actually pay

Where the money actually goes

Most ERP budgets are built around the license quote, and the license is rarely the largest line. Implementation, data migration, integration, and the first year of live use usually cost more than the software itself.

A realistic budget starts by naming every line item before anyone commits to a number. These are the ones that appear on almost every project:

• Licenses or subscription fees, priced per user or per module
• Implementation and configuration, typically 1.5 to 3 times the license cost
• Data migration from the systems being replaced
• Integration with the systems that stay
• Training, and the productivity dip while teams switch over
• Support and change requests in the first year of live use

The line items nobody quotes upfront

The two that surprise buyers most are data quality and the integration boundary. Migration estimates assume the old data is clean. It never is, and the cleanup lands on your team or on a change request.

Integration is where fixed quotes quietly become open ones. The new system has to meet payroll, banking, inventory, and whatever else stays behind, and each of those boundaries has its own owner, its own format, and its own failure modes.

How to hold a quote to its number

Ask every vendor to price the integration boundary separately, in writing, before you compare totals. A quote that leaves integration as an allowance is not a quote, it is an opening position.

We scope that boundary before we price the build. It is slower at the proposal stage and considerably faster everywhere after it.