ERP Audit: How to Evaluate Your Current System Before Migration

Changing ERP systems is a transformational project: according to the 2024 Panorama Consulting Group report, one-third of ERP projects exceed their initial budget, and the median implementation cost reaches $450,000. In this context, investing three to five person-days in an internal audit before consulting any vendor is not an expense—it’s insurance against a poorly calibrated choice whose price will be measured in hundreds of thousands of dollars.

Yet most companies skip this step. They jump directly from “our ERP no longer meets our needs” to “which vendor should we choose?”, leaving the diagnosis to the future integrator, who has an obvious economic interest in maximizing the project scope.

This guide proposes a structured audit methodology across seven dimensions, with a reproducible scoring grid that you can share with your executive management to objectify the decision.

Why Audit Before Migration (Not After Choosing the Vendor)

The most frequent mistake is starting the replacement process by selecting a vendor. At this stage, confirmation bias is inevitable: each commercial demonstration will be interpreted through the lens of current dissatisfaction, without a clear vision of what works, what is genuinely missing, and what stems from a configuration problem rather than a product limitation.

An audit conducted internally, before any external consultation, produces three immediate benefits:

1. It objectifies the diagnosis. Rather than impressions (“the system is slow,” “accounting complains”), you have metrics: duplicate rate in customer records, number of Excel workarounds identified, monthly closing time compared to industry benchmarks.

2. It reduces over-dimensioning risk. Companies that precisely understand their gaps buy what they need, not what a salesperson recommends. According to a RubinBrown/KPC Team study, organizations that performed ROI analysis before implementation achieve their objectives 83% of the time.

3. It strengthens the business case. A CEO more readily accepts mobilizing a budget of $300,000 to $800,000 when the proposal is based on verifiable internal figures, not vendor slides.

The cost of an internal audit is minimal compared to the project it prepares. For a mid-sized company of 200 to 500 employees, count on three to five person-days split between IT, management control, and two or three business key users. If you lack internal expertise, a specialized consultancy will charge between $15,000 and $40,000 for a complete diagnosis, deliverables included.

The 7 Dimensions of a Complete ERP Audit

An ERP audit is not a financial audit. It’s a multi-dimensional X-ray of the information system that evaluates what the tool does, how it does it, what it costs, and how it’s perceived by daily users.

1. Functional Coverage: What the ERP Does vs What It Should Do

The objective is to create a four-quadrant matrix:

• Functions used and satisfactory: the foundation to preserve in any future system.
• Available but underused functions: before migrating, verify if better configuration wouldn’t suffice.
• Missing functions: genuine uncovered needs that justify a change.
• Functions bypassed by Excel: the most revealing signal. Each parallel spreadsheet is an indicator of functional gap or insufficient adoption.

Method: Meet with each business department (finance, purchasing, production, sales, HR) for two hours. Ask them to list their five most critical processes and evaluate the ERP coverage for each on a scale of 1 (entirely manual/Excel) to 5 (entirely in the ERP, no workarounds).

2. Master Data Quality (MDM)

Data migration is the poor relation of most ERP projects, and it’s often what causes schedule slippage. According to the 2024 Panorama Consulting report, data issues rank among the top factors for deadline overruns.

Metrics to measure:

Indicator	Acceptable threshold	How to measure
Customer duplicate rate	< 3%	SQL query on company name + registration number
Supplier record completeness	> 90% of mandatory fields	Export + count empty fields
Product data freshness	< 12 months since last update	Last_modified date field
Inter-module consistency	0 discrepancy accounting/inventory	Automated reconciliation

A duplicate rate exceeding 10% in customer records is an alarm signal: migrating this data as-is amounts to reproducing chaos in a new system.

3. Technical Performance and Application Debt

This dimension evaluates the technical health of the current installation:

• Response times: measure display time for most-used screens (order entry, inventory check, invoice editing). Beyond three seconds, productivity drops.
• Installed version vs latest available version: an ERP two major versions behind accumulates debt that makes updating as costly as migration.
• Volume of specific developments: count the number of active customizations. Beyond 20% custom code relative to standard, maintainability and version upgrades become problematic.
• Recurring incidents: analyze support tickets from the last 12 months. Repeated incidents on the same modules signal structural technical debt.

4. Integrations and Inter-Application Flows

Few ERPs operate in isolation. Map all inbound and outbound flows:

• CRM to ERP: customer synchronization, quotes, orders.
• ERP to accounting/BI: journal entry exports, reporting flows.
• Banking to ERP: statements, reconciliation, SEPA transfers.
• WMS/logistics: inventory movements, delivery notes.
• Supplier/customer EDI: orders, shipping notices, invoices.

For each flow, document: frequency (real-time, daily batch, manual), volume, format (REST API, flat file, EDI, copy-paste), and error rate. Manual or semi-manual flows are priority candidates for automation in the future system.

5. Regulatory Compliance

The regulatory framework evolves rapidly, and the ERP must keep pace:

• Accounting records file: does your ERP generate compliant accounting records with one click, or does it require manual reprocessing?
• Electronic invoicing: upcoming reforms will require specific formats (e.g., Factur-X/Peppol for B2B). Is your ERP ready?
• GDPR: personal data purge capability, right to be forgotten, treatment registry.
• Reliable audit trail: modification traceability for accounting entries, required by tax administration.
• CSRD/ESG: if your company is subject to sustainability reporting, verify the ERP’s ability to collect and consolidate extra-financial data.

Assign each requirement a status: compliant, partially compliant (workaround in place), non-compliant. Any regulatory non-compliance is a strong argument for justifying the investment.

6. Recurring Costs and Current TCO

Before comparing the cost of a new system, you must know the real cost of the existing one. TCO (Total Cost of Ownership) includes often underestimated items:

• Annual licenses and maintenance: the most visible item, rarely the highest.
• Infrastructure: on-premise hosting (servers, backups, OS updates) or cloud subscription.
• Internal support: how many IT FTEs are mobilized to maintain the ERP daily?
• Specific developments: annual cost of maintaining and evolving customizations.
• Non-quality cost: time lost in re-entries, inventory errors, billing delays. This item is hardest to quantify but often the highest.

7. User Satisfaction and Adoption

A technically functional but user-rejected ERP is a failure. This dimension measures actual adoption:

• Internal NPS: ask users one question, “On a scale of 0 to 10, would you recommend this ERP to a colleague from another company?” A score below 20 indicates a serious adoption problem.
• Bypass rate: how many critical business processes go through Excel, email, or third-party tools rather than the ERP?
• Connection rate: what percentage of active licenses corresponds to users who actually log in at least once a week?
• Field feedback: beyond numbers, collect frustrations and satisfaction points. Field users identify problems that IT doesn’t see.

The survey can be as simple as a ten-question online form, sent to all active users. Plan one week for collection and target a response rate of at least 40%.

Scoring Grid: Rating Your ERP on 100 Points

Once the seven dimensions are audited, consolidate results in a weighted scoring grid. Here’s a model you can adapt to your context:

Dimension	Weight	Score /100	Weighted score
1. Functional coverage	20%	__	__
2. Master data quality	15%	__	__
3. Technical performance	15%	__	__
4. Integrations and flows	10%	__	__
5. Regulatory compliance	15%	__	__
6. Current TCO	10%	__	__
7. User satisfaction	15%	__	__
Total	100%		__ /100

Results Interpretation

• Score above 65/100: the current ERP is still viable. Focus efforts on optimization: better configuration, user training, data cleanup. Migration would probably be premature and disproportionate.
• Score between 40 and 65/100: warning zone. Some dimensions are failing, but the system remains operational. Evaluate if a major update or targeted optimization project could suffice. If regulatory or technical dimensions are in the red, migration becomes a priority.
• Score below 40/100: urgent migration. The system accumulates technical, regulatory, and organizational debt. Each month of delay increases operational risk and future migration cost.

The proposed weighting is a starting point. Adapt it to your sector: a company subject to strong regulatory obligations (pharmaceuticals, agribusiness) will increase the compliance dimension weight; a trading company with complex logistics flows will strengthen the integrations dimension.

Deliverables of a Successful ERP Audit

An audit that doesn’t produce actionable documents is an academic exercise. Here are the four expected deliverables:

1. Diagnostic report: synthesis of seven dimensions, with completed scoring grid, factual findings, and user feedback. This document is addressed to executive management and must be understandable without technical jargon.

2. Application mapping: visual diagram of the current IT ecosystem, with ERP at center, satellite systems (CRM, BI, WMS, banking), and flows connecting them. Indicate for each flow its degree of automation and error rate.

3. Risk matrix: identified risks classified by probability and impact (technical debt, regulatory non-compliance, skill loss on the tool, vendor support end). This matrix directly feeds the go/no-go decision.

4. Quantified business case: migration cost estimate (low/high range), compared to current TCO projected over 5 years, with ROI calculation on three scenarios (optimistic, median, pessimistic). This document triggers (or not) the project.

Who Should Lead the Audit: Internal vs External Consultancy

Both approaches have their merits, and the choice depends on your organization’s IT maturity.

Internal Audit

Advantages: detailed knowledge of business processes, limited cost (three to five person-days), immediate ownership of results by teams. Internal audit works well when IT has a senior functional profile capable of stepping back from the system they manage daily.

Limitations: risk of bias (IT audits its own scope), lack of sector benchmarks, difficulty challenging established practices. A user who has bypassed the ERP for five years no longer sees it as a bypass.

External Consultancy

Advantages: fresh perspective, proven methodology, sector benchmarks, ability to challenge both sides (IT and business). The consultancy produces an independent diagnosis that carries more weight with executive management.

Limitations: cost ($15,000 to $40,000 for a mid-sized company, depending on scope), context appropriation time, risk of biased recommendation if the consultancy is also an integrator.

Our recommendation: start with a light internal audit (the scoring grid above) to objectify the situation. If the score is in the warning zone (40-65) and the migration decision isn’t obvious, call on an external consultancy for a second opinion. Verify that the chosen consultancy isn’t also a reseller or integrator of an ERP vendor: their independence is the condition of their added value.

Five Common Mistakes to Avoid During the Audit

1. Auditing only IT. Field users—accountants, buyers, warehouse workers, salespeople—hold the most valuable information on workarounds and frustrations. An audit that doesn’t include at least five business interviews is incomplete.

2. Confusing dissatisfaction with need for migration. An ERP can be unpopular due to insufficient training or inappropriate configuration, not because it’s obsolete. The audit must distinguish between the two.

3. Ignoring data quality. Enthusiasm for a new tool makes one forget that data will migrate with its defects. According to the 2024 Panorama Consulting report, data quality problems are among the top factors for project deadline overruns.

4. Not quantifying the cost of inaction. The audit shouldn’t just measure current ERP gaps; it must estimate what the status quo costs: non-compliance penalties, hours lost in re-entry, missed business opportunities due to lack of integrated CRM.

5. Conducting the audit with a vendor already in mind. If the conclusion is already written, the audit is a validation exercise, not a diagnosis. Keep vendor selection for the next step.

From Audit to Requirements Specification

The audit isn’t an end in itself. It directly feeds the ERP requirements specification, which will structure your consultation. Specifically:

• The missing functions identified in dimension 1 become the functional requirements of the specification.
• The data problems identified in dimension 2 size the data migration project.
• The integrations mapped in dimension 4 define the interfaces to plan.
• The current TCO calculated in dimension 6 serves as baseline to compare vendor offers.
• The business case produced as deliverable sets the budget envelope and ROI criteria.

To deepen specification writing, consult our guide on effective ERP requirements specification. And to understand ERP cost mechanisms beyond license price, read our total cost of ownership analysis.

Download our ERP evaluation grid to benchmark three vendors side by side on 30 criteria and 100 points, a direct complement to the audit grid presented in this article.