ERP Implementation Guide: Step by Step for Indonesian Companies

ERP (Enterprise Resource Planning) implementation is often cited as one of the riskiest technology projects a company can take on. Data shows that 55–75% of ERP projects experience cost overruns or schedule delays, and some even end in outright failure.

But that's not because ERP itself is bad. Failures almost always stem from things that could have been anticipated: insufficient preparation, unrealistic expectations, neglected change management, or poor vendor selection.

This guide covers how to run an ERP implementation the right way — from initial preparation to a stable production system.

Why Does ERP Implementation Often Fail?

Before discussing how to do it right, it's important to understand where failures typically occur:

1. Unclear Scope

"Full ERP implementation" without a clear definition of which modules, which business processes are in scope, and how much customization is needed is a recipe for uncontrolled scope creep.

2. Half-Hearted Management Commitment

ERP changes how people work. Without full support from the C-suite — people willing to make quick decisions and overcome resistance — the project gets stuck at the middle-management level.

3. Data That Isn't Ready

Moving dirty data into a new system only pollutes the new system. Data migration is a commonly underestimated challenge — it can consume 20–30% of total implementation effort.

4. Underestimating Training Needs

Software can be perfect, but if users don't know how to use it, the system won't be effective. Rushed or one-time training is a common cause of poor adoption.

5. Excessive Customization

"I need a system that matches exactly how we currently work" sounds reasonable but is often dangerous. Excessive customization makes upgrades difficult, increases maintenance costs, and eliminates the benefit of the best practices already built into the ERP.

Phase 0: Preparation Before Selecting a Vendor (2–4 Weeks)

Many companies contact ERP vendors before doing internal preparation. This is a major mistake. Without proper preparation, you can't evaluate vendors objectively.

Form an Internal Implementation Team

This team is key to project success. Ideally it consists of:

• Project sponsor: A C-level executive with the authority to make decisions and resolve conflicts
• Internal project manager: Someone who can be dedicated fully (or mostly) to this project
• Subject matter experts (SMEs): Representatives from every department that will use the ERP
• IT representative: If there's an internal IT team

Document Current Business Processes

Before choosing a new system, understand the existing one. Map every business process that will fall within the ERP's scope:

• Who performs it (role/position)
• What is done (step-by-step activities)
• What documents or data are created/used
• Which points are the most time-consuming or error-prone
• What needs to be improved

This documentation becomes the basis for requirement specifications and helps you evaluate whether a vendor truly understands your needs.

Define a Clear Scope

Decide: which modules will be implemented in the first phase? A successful phased implementation is far better than a massive one that fails.

Common module sequencing for phased implementation:

1. Phase 1: Finance & Accounting + Purchasing
2. Phase 2: Inventory & Warehouse Management
3. Phase 3: Sales & CRM
4. Phase 4: HR & Payroll
5. Phase 5: Manufacturing (if applicable)

Set Success Metrics

How will you know the implementation succeeded? Define specific, measurable metrics:

• "Financial report generation time reduced from 5 days to 1 day"
• "Purchase order approval process reduced from 3 days to 1 day"
• "Zero discrepancy between inventory data and physical stock"

These metrics become the benchmark for post-go-live evaluation.

Phase 1: Vendor Selection (4–8 Weeks)

Choosing an ERP vendor isn't just about picking software — it's choosing a long-term partner. Mistakes at this stage are hard to fix later.

Create a Detailed Request for Proposal (RFP)

A good RFP contains:

• Company and industry profile
• Implementation scope (modules and processes included)
• Data volume (daily transaction count, number of SKUs, number of employees)
• Technical requirements (integration with existing systems, hardware needs)
• Expected timeline
• Evaluation criteria and their respective weightings
• Preferred proposal format

Evaluate at Least 3–4 Vendors

Important evaluation criteria:

• Functional fit: How well does the software meet your business needs without excessive customization? (heavily weighted)
• Industry experience: A vendor who has implemented in your industry understands your business nuances
• Total cost of ownership: License + implementation + training + maintenance + upgrade costs over 5 years
• Scalability: Can the system grow along with your business?
• References: Ask for contacts of existing clients you can speak with directly — not testimonials written by the vendor
• Local support: How fast is the response when there's an issue? Is there a team in Indonesia?

Proof of Concept (POC) for Shortlisted Vendors

For the top 2–3 vendors, ask for a demonstration using your business's real data and scenarios, not a generic demo. This reveals a lot that isn't visible in a presentation.

Phase 2: Design and Configuration (8–16 Weeks)

Once a vendor is selected, the longest and most critical phase begins.

Kick-off and Project Charter

A formal document that defines:

• The final agreed scope (any changes go through a formal change request)
• A timeline with clear milestones
• Team structure on both sides (vendor and your company)
• An escalation mechanism for issues
• Acceptance criteria for each deliverable

Business Process Reengineering (BPR) Workshop

This is a session where your team and the vendor's consultants sit together to map out how business processes will run in the new system. Key questions for each process:

• Can the current process follow ERP best practices without customization?
• If not, is it better to adapt the business process or customize the system?
• What triggers each transaction?
• How will the approval flow work?
• What reports are needed and who needs them?

Golden rule: Wherever possible, adapt your business processes to the ERP, not the other way around. A good ERP already implements proven industry best practices.

Configuration and Customization

Based on the BPR results, the vendor configures the system. Distinguish between:

• Configuration: Settings that can be done without changing code (chart of accounts, approval workflows, report parameters) — this is safe and easy to maintain
• Customization: Code changes for functionality that doesn't exist in the standard system — use only when truly necessary

Data Migration Plan

This is the most commonly underestimated area. The correct data migration steps:

1. Data inventory: List all data that needs to be migrated (master data: customers, suppliers, items; transactions: opening balances, open POs/SOs)
2. Data cleansing: Clean data before migration — duplicates, inconsistent formats, incomplete data
3. Mapping: Map fields from the old system to the new one
4. Trial migration: Run a trial migration to a test system, verify accuracy
5. Sign-off: The business team (not IT) must verify that migrated data is accurate

Phase 3: Testing (4–8 Weeks)

Thorough testing is the difference between a successful go-live and one that turns into a nightmare.

User Acceptance Testing (UAT)

UAT is done by business users — not IT or vendor consultants. Users test the system with real scenarios they face daily:

• End-to-end flow: from purchase order to payment, from sales order to delivery
• Edge cases: what happens if stock goes negative? If a customer's credit limit is exceeded?
• Reports: do the numbers in reports match expectations?

Every defect is documented clearly (reproduction steps, expected vs actual behavior, severity). There's no go-live before all critical and major defects are resolved.

Performance Testing

Simulate production transaction volumes: how many transactions per hour/day at peak time? Is the system still responsive? How long do reports take to load?

Disaster Recovery Testing

Simulate server failure and measure recovery time. Make sure the backup and restore procedure actually works.

Phase 4: Training (2–4 Weeks Before Go-Live)

Effective training isn't just showing which buttons to click.

Train-the-Trainer

Train "super users" or "key users" from each department first — the people who will become the first point of reference for their colleagues after go-live. They need to truly understand the system, not just know how to use it.

End User Training

End user training should:

• Focus on their daily work scenarios, not every system feature
• Use familiar data (not generic dummy data)
• Provide sufficient hands-on practice
• Come with a quick reference guide they can bring back to their desk

Schedule Training Not Too Far From Go-Live

Ideally, training happens 2–3 weeks before go-live. Too early, and users forget. Too close, and there's a risk not all users get trained in time.

Phase 5: Go-Live

This is the most anticipated and most nerve-wracking moment.

Go-Live Strategy

There are three approaches:

Big Bang: All modules go active at once on the same day. Finishes faster, but higher risk. Only suitable if testing is very thorough and the team is very well prepared.

Phased Rollout: Implementation by module or by department, sequentially. Safer because risk is localized, but the process takes longer.

Parallel Run: The old and new systems run simultaneously for 1–2 months, then cut over to the new system. Safest, but the most effort since the team has to do double entry.

For most mid-sized Indonesian businesses, phased rollout is the most pragmatic choice.

Hypercare Period (4–8 Weeks After Go-Live)

This is the critical post-go-live period where the vendor team must remain highly engaged:

• 24/7 system performance monitoring
• Fast response (ideally < 2 hours) for every issue
• Daily check-ins with key users
• Rapid fixes for bugs found in production

Don't consider the project finished on go-live day. The hypercare period is part of the implementation.

Warning Signs of a Troubled Implementation

Recognize these warning signs as early as possible:

• Timeline that keeps shifting without clear reason
• Testing that is rushed or skipped
• A vendor that's hard to reach or slow to respond
• Scope that keeps growing without formal change requests
• Key users not involved in testing
• Migrated data that hasn't been verified by the business team

If you see these signs, escalate to the project sponsor immediately — don't wait for the problem to grow.

ERP Implementation Cost: A Realistic Picture

ERP implementation costs often far exceed the license cost visible in the initial proposal. Cost components to account for:

• Software license (one-time or subscription)
• Implementation and configuration cost
• Customization (per hour or per deliverable)
• Data migration
• Training
• Hardware or cloud infrastructure
• Internal cost: project team time diverted from routine work
• Opportunity cost: operations slowing slightly during the transition
• Annual maintenance and support

General rule: total implementation budget (excluding license) ranges 50–150% of the first-year license cost for a healthy implementation.

Conclusion: Keys to Successful ERP Implementation

From our experience supporting Indonesian companies through ERP implementation, here's what matters most:

1. Genuine top management commitment — not just on paper
2. Clearly defined scope before the project begins
3. Clean data — invest enough time in cleansing before migration
4. Actively involved key users from the BPR phase through UAT
5. Adequate training with enough hands-on time
6. Realistic expectations about timeline and temporary operational disruption

A properly implemented ERP is an investment that pays returns for years. One implemented in a rush or without preparation can become an expensive burden.

Need ERP implementation support or want to discuss a custom ERP system for your business? Contact us — we have experience developing and implementing ERP systems for various industries across Indonesia.