ERP strategy & selection
ERP implementation in the Philippines: a phase-by-phase guide
A practical ERP implementation plan for Philippine companies: phases, roles, timeline drivers, data migration, testing, training, parallel runs and go-live support.
ERP implementations fail less often because of software than because of unclear scope, poor data, weak ownership and rushed go-lives. A disciplined plan, with the business leading and the vendor guiding, turns a risky project into a predictable one. This guide walks through each phase, the roles involved and the decisions that matter most for Philippine companies.
Phases at a glance
| Phase | Main outputs |
|---|---|
| 1. Preparation | Business case, goals, scope, sponsor, team, vendor selected |
| 2. Discovery and design | Current process review, future process design, configuration decisions |
| 3. Data preparation | Cleaned master data, migration plan, opening balances |
| 4. Configuration and build | System configured; integrations and reports built |
| 5. Testing | Scenario tests, user acceptance, payroll and month-end dry runs |
| 6. Training | Role-based training; key users ready to support others |
| 7. Parallel run and go-live | Parallel cutoff or close; go-live decision; cutover |
| 8. Stabilization | Hypercare support, issue resolution, adoption tracking |
| 9. Optimization | Next phase planning, improvements, KPIs |
Phase 1: Preparation
- Define goals and measures (close days, payroll accuracy, stock accuracy, cycle times)
- Appoint an executive sponsor and a full-time or substantial-time project lead from the business
- Name process owners for each area
- Agree scope for the first phase (phased rollout)
Phase 2: Discovery and design
Walk through real processes with the people who do them: a payroll cutoff, a purchase, a branch transfer, a month-end close. Decide future processes and configuration. Document decisions, especially where you will change your process to fit the standard and where you need configuration or development. See requirements as scenarios.
Phase 3: Data preparation
Data is usually the longest task. Clean and validate employees, items, customers, suppliers, chart of accounts and opening balances. Assign an owner for each data set. See ERP data migration.
Phase 4: Configuration and build
Configure companies, branches, users, roles, approval workflows, pay rules, tax tables, item settings and reports. Build integrations only where needed, with error handling.
Phase 5: Testing
| Test | Purpose |
|---|---|
| Unit and configuration tests | Each setting works as designed |
| End-to-end scenario tests | Hire-to-pay, procure-to-pay, order-to-cash, record-to-report |
| User acceptance testing | Business users confirm it works for them |
| Payroll parallel computation | Net pay and statutory amounts match the current process |
| Month-end dry run | Financial reports reconcile |
Phase 6: Training
Train by role (cashier, supervisor, approver, payroll officer, accountant), using your own data and procedures. Develop key users in each department and branch who support others after go-live. See ERP change management.
Phase 7: Parallel run and go-live
For payroll, run at least one full cutoff in parallel. For finance, close one period in both systems where feasible. Hold a go/no-go meeting with clear criteria. Plan cutover: freeze dates, final data loads and communication. See the go-live checklist.
Phase 8 and 9: Stabilization and optimization
Provide intensive support (hypercare) for the first weeks. Track issues, adoption and KPIs. After stabilization, plan the next phase and continuous improvements.
What drives the timeline
- Number of companies, branches and users
- Number of modules in the first phase
- Data quality
- Integration requirements
- Availability of business decision makers
- Customization volume
Roles and responsibilities
| Role | Responsibility |
|---|---|
| Executive sponsor | Priorities, resources, decisions on conflicts |
| Project lead (business) | Day-to-day coordination, decisions within scope |
| Process owners | Process design, testing and sign-off for their area |
| Key users | Detailed testing, training and first-line support |
| Vendor project manager | Plan, methodology, vendor resources |
| Vendor consultants | Configuration, guidance on best practice |
| IT | Infrastructure, security, integrations, access |
Common risks and mitigations
| Risk | Mitigation |
|---|---|
| Key decision makers unavailable | Agree decision rights and meeting schedules at the start |
| Scope creep | Change control with impact on time and cost |
| Dirty data | Start data cleanup in the first weeks; assign owners |
| Weak testing | Script scenarios and require sign-off by process owners |
| Low adoption | Key users, role-based training, removal of old tools |
| Go-live during peak season | Schedule around paydays, holidays and busy periods |
Where Cirquolus fits
A Cirquolus rollout is planned around your modules, companies, branches, users, data migration and training needs, with scope and timeline confirmed before implementation. We recommend testing with your own scenarios and parallel runs before go-live. Start with one module such as payroll or POS and expand across companies and branches. Talk to our team about a realistic plan for your scope.
Frequently asked questions
What are the phases of ERP implementation?
Preparation, discovery and design, data preparation, configuration, testing, training, parallel run and go-live, stabilization and optimization.
How long does an ERP implementation take?
It depends on scope, data quality, integrations and decision speed. Phased rollouts deliver first results sooner.
Why do ERP implementations fail?
Common reasons include unclear scope, poor data, weak business ownership, insufficient training and rushed go-lives without parallel runs.
What is a parallel run?
Running the old and new systems side by side for a period, such as a payroll cutoff or month-end, and comparing results before switching.
Bring this workflow to a Cirquolus demo.
Show us your current process, companies and branches. We will map it to the modules you need and propose a realistic rollout.