The ERP Due Diligence Checklist: 15 Questions Before You Switch

Switching ERP systems is one of the highest-risk decisions a manufacturing company can make. The average ERP implementation takes 14 to 21 months, costs 2 to 5 times the initial software license, and carries a 50 to 75 percent risk of schedule overrun according to Panorama Consulting's 2025 ERP Report^[1]. Yet for many Nordic manufacturers facing vendor consolidation, rising costs, or compliance gaps, switching is becoming unavoidable.

This checklist is designed for CIOs, CFOs, and operations directors evaluating ERP alternatives. It covers the areas that most commonly derail transitions when overlooked during due diligence.

Data & Migration (Questions 1-4)

1. Can you export ALL data in open, documented formats?

This means full transactional history, master data, custom fields, document attachments, and audit logs. "We can provide a CSV export" is not sufficient. Demand a complete data dictionary and sample exports during the evaluation phase, not after signing.

2. What is the vendor's data retention policy post-contract?

Some vendors delete customer data 30 days after contract termination. Others charge extraction fees. Negotiate a minimum 180-day retention period and free data export in your contract terms.

3. How will custom business logic transfer?

Every mature ERP installation contains years of accumulated business rules: pricing logic, approval workflows, inventory algorithms. These often exist only in the ERP's proprietary scripting language. Catalogue all customizations before starting vendor evaluation. A typical mid-sized manufacturer has 50 to 200 custom business rules that must be rebuilt or replaced.

4. What is the parallel running requirement?

Plan for 3 to 6 months of parallel operation where both old and new systems run simultaneously. This is expensive but essential. Budget for double licensing costs during this period and ensure both systems can receive the same transaction data for reconciliation.

Compliance & Regulatory (Questions 5-8)

5. Does the new ERP support CSRD/ESRS data collection natively?

By 2026, most Nordic manufacturers need integrated sustainability data collection. An ERP that requires a third-party bolt-on for CSRD reporting adds cost, complexity, and data integrity risk. Ask for a live demonstration of ESRS data flows, not a roadmap slide.

6. Where is data stored, and under which jurisdiction?

GDPR requires clear data processing agreements. The European Data Act (Regulation 2023/2854)^[2] adds new data portability rights. Verify that production data stays within the EU and that the vendor has Data Processing Agreements compliant with GDPR Article 28^[3].

7. How does the ERP handle carbon accounting?

With ETS Phase 4 and CBAM now operational, carbon data is becoming as critical as financial data. The ERP should track energy consumption, emission factors, and Scope 1/2/3 emissions at the transaction level, not as a quarterly batch process.

8. Can the system produce regulatory reports for all operating countries?

Nordic manufacturers typically operate across Finland, Sweden, Norway, and Denmark, each with distinct tax reporting, Intrastat requirements, and labour regulations. Verify localization support for every country you operate in, including VAT return formats and statutory reporting.

Technology & Integration (Questions 9-12)

9. Does the ERP expose documented REST/GraphQL APIs?

Proprietary integration methods lock you in. Modern ERPs must provide well-documented, versioned APIs with OAuth 2.0 authentication. Test API performance during evaluation: response times, rate limits, and data volume handling.

10. Is the ERP compatible with AI agent protocols (MCP)?

The Model Context Protocol (MCP)^[4] is becoming the standard for AI-to-enterprise-system communication. An ERP that supports MCP can be augmented with AI agents for compliance automation, predictive maintenance, and intelligent procurement without custom development.

11. What is the deployment model?

Cloud-only, on-premise, or hybrid? For regulated industries, hybrid models that keep sensitive data on-premise while leveraging cloud for non-critical workloads often provide the best balance. Verify you can choose your cloud region and provider.

12. How are updates and patches delivered?

Mandatory forced updates that break customizations are a leading source of ERP frustration. Understand the update cycle, testing period, and rollback capabilities. Best practice: vendor provides a staging environment where updates can be tested before production deployment.

Commercial & Strategic (Questions 13-15)

13. What is the true total cost of ownership over 5 years?

Include: licenses, implementation consulting, data migration, training, customization, integration development, annual maintenance, and infrastructure costs. A common trap is low initial licensing with high professional services and annual escalation clauses. Demand a fixed-price TCO model.

14. What is the vendor's financial stability and ownership structure?

If you are switching because your current vendor was acquired, avoid landing in the same situation. Check the new vendor's ownership, funding history, and profitability. PE-backed vendors with high leverage ratios may face their own ownership changes within 3 to 5 years.

15. What are the contractual exit terms from day one?

Negotiate exit terms before you sign, not when you want to leave. Include: data export format and timeline, transition assistance period, maximum termination fees, and intellectual property rights for customizations developed during the contract.

References

[1] Panorama Consulting Group, 2025 ERP Report — survey of 200+ ERP implementations covering timeline, cost overruns, and success rates.
[2] European Parliament and Council, Regulation (EU) 2023/2854 (European Data Act), OJ L, 22.12.2023 — data portability and cloud switching rights.
[3] European Parliament and Council, Regulation (EU) 2016/679 (GDPR), Article 28 — requirements for data processing agreements with processors.
[4] Anthropic, Model Context Protocol Specification, 2024 — open standard for AI-to-enterprise system integration via JSON-RPC 2.0.

Next step: Use this checklist as a scoring framework during your ERP evaluation. DWS IQ provides a vendor-independent compliance and automation layer that works across ERP systems, reducing your dependency on any single vendor. Learn more at dws10.com.