# Why ERP Implementations Fail in Indonesian Businesses — And How to Avoid It > An honest look at the most common ERP failure patterns in Indonesian SMEs — poor change management, under-resourcing, and customization creep — with practical advice to prevent them. URL: https://www.matthewswong.com/en/blog/why-erp-fails-indonesian-businesses/ - Author: Matthews Wong (https://www.matthewswong.com/en/about/) - Published: 2025-06-10 - Updated: 2026-10-13 - Category: ERP Indonesia's SME sector is in the middle of a quiet digital transformation. Many businesses that ran on spreadsheets and WhatsApp groups for years are now evaluating or actively implementing custom ERP systems. Yet ERP projects keep disappointing: Gartner predicts that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals. Having built custom ERP systems as a freelance consultant — covering HR management, accounts payable with multi-level approval, and accounts receivable with automated reminders — I've seen firsthand what works and what doesn't. This post is an honest diagnosis of the most common failure patterns in the Indonesian business context, and a practical guide to avoiding them. ## The Four Root Causes of ERP Failure In my experience, most ERP failures trace back to four recurring problems: poor change management, under-resourcing the project, customization creep, and inadequate training. These aren't unique to Indonesia, but the local business culture and SME constraints amplify each one in specific ways. ### Poor Change Management: The Human Problem In my experience, technology is the smaller part of an ERP project — most of the work is people and process. When a business adopts an ERP system, it forces people to change how they do their jobs every single day. Department heads who are not involved in the selection process will resist the system. Staff who built their careers on knowing 'which Excel file to open' suddenly feel their expertise is being erased. In Indonesian businesses, there's often a strong hierarchical culture — if the senior manager doesn't visibly champion the system, the team won't adopt it. The fix is executive sponsorship that goes beyond writing a memo: the CEO or director should use the system themselves, visibly, in the first month. ### Under-Resourcing: The Budget Trap Many Indonesian SMEs budget for the software development cost but forget to budget for implementation — data migration, staff training, parallel running, and internal project management. A custom ERP project is not 'done' when the last feature is deployed; it's done when the last user is productive on it. The split I plan around for a medium-sized implementation is roughly 40% development, 20% data migration and testing, 20% training and change management, and 20% hypercare support after go-live. Cutting any of these is how projects end up with a 'working' system nobody uses. > Appoint an internal ERP champion per department — not just a project coordinator. This person owns adoption for their team, runs internal training sessions, and is the first point of contact for questions. Without department-level champions, the implementation team becomes the only support resource, which doesn't scale. ## Customization Creep and Scope Management Another failure mode I see constantly is what I call 'customization creep' — the ERP system starts simple, then every department adds 'just one more requirement' until the budget runs out long before completion and the core system is never actually delivered. This is particularly common in Indonesian businesses where decision-making is often consensus-driven and it's culturally difficult to say no to a senior stakeholder's feature request. ### Using Feature Flags for Phased Rollout The most effective mitigation is a formally scoped Phase 1 — a core, hardened, production-ready system that covers the highest-value processes — followed by a structured roadmap for Phase 2 and beyond. Use feature flags in your codebase to enable modules per department as they become ready, rather than trying to go live with everything at once. ## Data Migration: The Hidden Crisis Every ERP implementation has a data migration problem — historical data sitting in Excel files, WhatsApp messages, and email attachments that needs to be cleaned, validated, and loaded into the new system. In the projects I have worked on, data migration has consistently taken two to three times longer than estimated. Indonesian SMEs often have years of Excel files with merged cells, inconsistent date formats, duplicate customer codes, and missing required fields. Don't let the migration happen at the last minute — start the data audit on day one of the project. > **Go-Live Risk Warning** > Never go live on a Monday. If your ERP go-live coincides with month-end closing or payroll processing, you're combining maximum business risk with maximum system stress. Schedule go-live for mid-month, mid-week, with a full hypercare team on standby. Also have a tested rollback plan ready — know exactly what steps you'll take if the system fails in the first 48 hours. ## Training That Actually Works Generic training manuals don't work. Users need training on the specific scenarios their department actually encounters — how to submit a leave request, how to approve a payment voucher, how to reconcile an AR statement. Record short screen-capture videos (3–5 minutes each) for each workflow and put them in a company wiki. Supplement this with monthly 'ERP clinics' — 30-minute open Q&A sessions where the implementation team answers questions live. ## The Realistic Timeline for Indonesian SME ERP Projects For a medium-sized Indonesian SME (50–200 employees) implementing a custom ERP covering HR leave, AP, and AR: plan for 6–9 months from kick-off to stable production. Month 1–2: requirements gathering and data audit. Month 3–5: core development and UAT. Month 6: parallel running (old system + ERP simultaneously). Month 7: hard cutover and hypercare. Month 8–9: Phase 2 planning and non-critical feature development. ## Sources & Further Reading - Panorama Consulting — The 2026 ERP Report — https://www.panorama-consulting.com/resource-center/erp-report/ - Gartner — What IT Leaders Must Do to Avoid Disappointing ERP Initiatives — https://www.gartner.com/en/information-technology/insights/what-it-leaders-must-do-to-avoid-disappointing-erp-initiatives - Ahmad and Pinedo Cuenca — Critical Success Factors for ERP Implementation in SMEs, Robotics and Computer-Integrated Manufacturing (2013) — https://doi.org/10.1016/j.rcim.2012.04.019 > **Key takeaway:** In my experience, ERP projects in Indonesian SMEs mostly fail for non-technical reasons: weak change management, a budget that covers only development, customization creep and data migration left too late. Gartner expects more than 70% of recently implemented ERP initiatives to fall short of their original business goals by 2027, and every one of these causes can be settled before any code is written. ## Source links - https://www.panorama-consulting.com/resource-center/erp-report/ - https://www.gartner.com/en/information-technology/insights/what-it-leaders-must-do-to-avoid-disappointing-erp-initiatives - https://doi.org/10.1016/j.rcim.2012.04.019 ## FAQ ### What are the most common reasons ERP implementations fail in Indonesian businesses? Gartner predicts that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals, so disappointing results are common everywhere. In Matthews Wong's experience, the four root causes are poor change management, under-resourcing the project, customization creep, and inadequate training. In the Indonesian context, a strong hierarchical culture and SME budget constraints amplify each of these problems. ### How should an Indonesian SME realistically budget for an ERP project? The split Matthews Wong plans around allocates roughly 40% to development, 20% to data migration and testing, 20% to training and change management, and 20% to hypercare support after go-live. Many SMEs only budget for software development and neglect the implementation costs, which is one of the main reasons projects end up with a working system that nobody uses. ### What is customization creep and how can it be prevented? Customization creep happens when each department adds 'just one more requirement' until the budget runs out long before completion and the core system is never delivered. The most effective mitigation is a formally scoped Phase 1 that covers only the highest-value processes, followed by a structured roadmap for later phases. Using feature flags in the codebase lets teams enable modules per department as they become ready, rather than attempting a full simultaneous go-live. ### Why does data migration always take longer than expected, and what can teams do about it? In the projects Matthews Wong has worked on, data migration has taken two to three times longer than estimated, because Indonesian SMEs often have years of Excel files with merged cells, inconsistent date formats, duplicate customer codes, and missing required fields. The fix is to start the data audit on day one of the project rather than leaving migration to the last minute. ### What is the realistic timeline for a custom ERP project in an Indonesian SME? For a medium-sized Indonesian SME with 50–200 employees, a custom ERP covering HR leave, accounts payable, and accounts receivable should be planned over 6–9 months. The schedule runs from requirements gathering and data audit in months 1–2, through core development and UAT in months 3–5, parallel running in month 6, hard cutover and hypercare in month 7, and Phase 2 planning in months 8–9. --- - HTML version: https://www.matthewswong.com/en/blog/why-erp-fails-indonesian-businesses/ - Bahasa Indonesia: https://www.matthewswong.com/id/blog/why-erp-fails-indonesian-businesses/ - Site index for agents: https://www.matthewswong.com/llms.txt - Sitemap: https://www.matthewswong.com/sitemap.xml - API description (OpenAPI): https://www.matthewswong.com/openapi.json