ERP implementation in Thailand, delivered in testable phases

Vendor-neutral ERP rollouts — selection, fit-gap analysis, phased go-live, change management, integration with legacy systems.

Note: We implement ERPs but do not resell licences. Vendor-neutral — we recommend the system that fits, not the one with the biggest commission.

Short answer for ERP buyers

iReadCustomer starts ERP implementation with a fit-gap and selects the platform around the real process, not a reseller commission. A typical project is 25–50 man-days at THB 7,000 per man-day, or THB 175,000–350,000, excluding licences and migration work whose data quality has not been assessed.

Scope and planning model last checked: 10 July 2026

ERP implementation from fit-gap to handover

Each phase has its own deliverable and acceptance gate, so the team can stop, adjust or reorder modules before risk spreads across the programme.

1. Process map and fit-gap
Map sales, purchasing, stock, production, accounting and spreadsheet handoffs; separate true requirements from habits inherited from the old system.
2. Platform and data ownership decision
Compare Odoo, Zoho, the existing stack or custom work on fit, licences, integrations and maintainability—not commission.
3. Prototype the risky flows
Test high-impact uncertainty first: inventory costing, BOM, tax, approval permissions and Thai documents.
4. Migrate and reconcile data
Run mapping and dry imports, log rejected rows, and reconcile masters, opening balances, stock and open documents before cutover.
5. UAT, training and parallel run
Real users test normal and failure cases, train by role, and run in parallel when data or operational downtime risk remains high.
6. Phased go-live and handover
Cut over module by module with rollback criteria, an issue log, admin guide, integration map, backup/restore procedure and post-live backlog.

How ERP implementation pricing is built

This is a budgeting model using our published THB 7,000 per man-day rate, not a market statistic or fixed quote. A project selects only the required workstreams and locks the estimate for each approved phase in writing.

Workstream	Estimated effort	Cost model	Assumption
Process map + fit-gap	4–7 man-days	THB 28,000–49,000	Decision-makers and process owners are available
Core module configuration	10–20 man-days	THB 70,000–140,000	Standard flows are the baseline
Data migration	+5–10 man-days	+THB 35,000–70,000	Source files and a reconciliation owner exist
Integrations / custom workflow	6–15 man-days	THB 42,000–105,000	External APIs and sandboxes are available
UAT, training and go-live	5–8 man-days	THB 35,000–56,000	Role-based group training with super users

Pricing boundary: A typical engagement is 25–50 man-days (THB 175,000–350,000); do not automatically sum every row. Licences, cloud, travel, barcode hardware, e-tax providers and post-agreement support remain separate.

Recurring costs kept separate from implementation

ERP licences or subscriptions and paid add-on modules
Cloud, database, backups, monitoring and document storage
E-tax, payment, SMS/LINE and third-party API services
Support, patches, upgrade testing and post-handover changes

Boundaries confirmed before quotation

We implement and integrate ERP systems; we do not resell licences or prescribe a platform before fit-gap.
The customer’s qualified accounting/tax owner validates statutory treatment and outputs.
Dirty data and requirements added after sign-off are separate change requests, not hidden inside the first estimate.
Calendar time depends on data, approvals, APIs and UAT availability; man-days are not an automatic delivery-time SLA.

Acceptance criteria that belong in the agreement

Inventory quantities and value, opening balances and open documents reconcile to the approved source.
Every role has tested permissions and critical approvals retain an audit trail.
UAT covers happy paths, rejection, duplicates, timeouts and correction of bad data.
Integrations have retry behaviour, an error queue, an owner and a reconciliation procedure.
The handover includes cutover and rollback criteria, admin guide, data dictionary and customer-owned account/credential register.

ERP implementation questions

How much does ERP implementation cost in Thailand?

Our planning range for a typical project is 25–50 man-days at THB 7,000 per man-day, or THB 175,000–350,000. Data migration commonly adds 5–10 man-days; licences, cloud and third-party services are separate after fit-gap.

Do we have to choose Odoo?

No. We compare Odoo, Zoho, the current stack and custom work on workflow fit, licences, integration, maintainability and upgrade cost. We do not resell vendor licences.

Can we migrate from spreadsheets?

Yes, with named data owners, mapping, cleansing, dry runs and reconciliation before go-live. Row count alone is not enough to price migration because duplicates and inconsistent identifiers drive much of the work.

How do you reduce ERP implementation risk?

Use phased go-live, prototype risky workflows first, rehearse migration, require real-user UAT, define rollback criteria and retain the old system read-only or in parallel where risk justifies it.

Construction ERP →BOQ, project purchasing, subcontractors, retention and job cost Rental ERP →Availability, contracts/deposits, returns, damage and utilisation Odoo implementation and customisation →Odoo scope for stock, manufacturing, Thai tax and integrations Send a process map for fit-gap scoping →Start with the real workflows and risk before selecting software

Parent service: AI Digital Transformation →Talk to us

In other regions

ERP Implementation in Bangkok

Other offerings for Thailand

Research Guides See the full rate card →

ERP implementation in Thailand, delivered in testable phases

Short answer for ERP buyers

ERP implementation from fit-gap to handover

1. Process map and fit-gap

2. Platform and data ownership decision

3. Prototype the risky flows

4. Migrate and reconcile data

5. UAT, training and parallel run

6. Phased go-live and handover