Migrating off Peachtree (Sage 50) in Cambodia: complete guide

What is Peachtree and why are Cambodia firms still on it?

Peachtree was rebranded as Sage 50 Accounting in 2013 but remains widely called Peachtree in Cambodia. Most users who installed it did so before the rebrand, and the software's KH install base has not meaningfully turned over since. Peachtree/Sage 50 is a Windows-desktop accounting package with a flat-file proprietary database (PTB format), a double-entry accounting engine, and a reasonably functional chart-of-accounts structure. At its peak in Cambodia, it was the system of choice for mid-size businesses that found QuickBooks too simple and saw no local alternative to a custom ERP.

Firms stayed on Peachtree for the same reason most businesses stay on legacy software: it works, the accounting team knows it, and switching is disruptive. Monthly closes happen. Invoices go out. The chart of accounts is mapped. The disruption cost of change has always felt higher than the cost of staying, until now. Three forces have changed that calculation: Cambodia's CamInvoice rollout (which Peachtree cannot meet), Sage's rolling obsolescence policy (only the current release is supported, so Sage 50 2024 lost program and tax updates, e-filing, and bank feeds on 4 March 2026), and the growing mismatch between Peachtree's USD-centric accounting model and Cambodia's KHR/USD reality. Sage says the U.S. edition "is designed to function with a currency of US dollars only", while the monthly return to GDT is reported in KHR.

What does Peachtree migration look like in Cambodia?

Peachtree migrations are meaningfully harder than QuickBooks migrations. The difference comes down to data extraction. QuickBooks provides structured IIF exports and a reasonably clean API (for QBO). Peachtree stores its company data in proprietary PTB flat files that have no documented public schema. Extraction requires either: using Peachtree's built-in export to CSV/XLS (which covers a subset of data and is not comprehensive), installing a third-party ODBC driver that reads the PTB files, or, in older installations where even those tools fail, reverse-engineering the data from printed reports and re-entering it manually.

• QuickBooks migration: typically 1–2 weeks for data extraction and COA mapping.
• Peachtree migration: typically 3–5 weeks for data extraction, format conversion, and COA mapping.
• Peachtree running on Windows XP or 7: extraction is complicated by the OS dependency; the machine may need to stay live during migration or data must be exported before the machine is retired.
• Peachtree versions prior to 2010: PTB format varies by version. Older installations may require a version-specific reader or a vendor engagement with Sage, so establish which reader supports your PTB version before anyone quotes the extraction.
• Companies with 10+ years of Peachtree history: historical data volume is typically higher than QuickBooks because Peachtree discourages archiving. Expect larger extraction payloads and longer validation cycles.

The practical implication: budget more time for extraction than you think you need. We have encountered Peachtree installations where the extraction phase alone took 4 weeks because the PTB files were partially corrupted and required repair before data could be read. Discovery is mandatory before quoting a Peachtree migration; the data state is too variable to estimate blind.

Where can you migrate to?

The right destination depends on business size, entity count, GDT compliance requirements, and whether accounting-only scope is sufficient or whether ERP functionality (inventory, manufacturing, CRM) is also in scope. If that trade-off is still open, our ERP in Cambodia guide works through it. For Cambodian businesses migrating off Peachtree, the realistic options are:

• A system built for your business: the route we take, and the only one on this list we deliver. The ledgers we build use a structured chart with account groups, tax mappings and currency assignments, with a KHR journal and a USD journal each linked to the correct bank account. The system keeps the books in KHR at the official rate and produces the monthly return figures and the sales and purchase lists, ready for your accountant to file through GDT's E-Filing. It carries no per-user licence and extends into a full ERP if the business grows into inventory, manufacturing or payroll. Best for: businesses that want the books shaped to how they operate. For a very small business (under 5 staff, USD-only, no government contracts, below the VAT threshold) a packaged tool is a reasonable choice, and we will say so. The scope is on our accounting system migration page.
• Odoo: a packaged open-source ERP. We do not implement or resell it.
• SAP Business One: mid-market choice for businesses with $5M+ revenue, 50+ staff, or complex inventory. More expensive to implement and operate: $15K–$50K+ for a Cambodia deployment is a range we have not benchmarked recently, so get current quotes from Cambodian SAP partners. Better out-of-box reporting; check how much Cambodian tax setup it ships.
• Acumatica: cloud ERP with strong multi-currency support and flexible licensing (resource-based, not per-user). Less common in Cambodia but growing. Check how much Cambodian tax setup it ships. Better for businesses with multiple international entities.
• Zoho Books: simpler accounting-only tool. Good for SMBs with under 5 users and USD-only operations. Limited KH localization. Lower implementation cost ($2K–$5K) but less headroom for growth.
• Xero: cloud accounting, clean UI, strong bank reconciliation. No KH chart-of-accounts localization. Multi-currency is a top-tier feature. Xero says it supports more than 160 currencies, but we could not find KHR confirmed in a published list, so check with Xero before committing. Best for: USD-only businesses with international accounting team familiar with Xero.
• Microsoft Dynamics 365 Business Central: enterprise-grade, full ERP. Requires Microsoft partner for implementation. High cost: $25K–$100K+ for a Cambodia deployment is an indicative range only, so get current quotes from Cambodian Microsoft partners. Suitable for large enterprises with existing Microsoft infrastructure.

Whichever you choose, a person still files the monthly return through GDT's E-Filing. Nothing files it for you.

Project shape and timeline

A Peachtree migration for a single-entity Cambodia SMB runs 10–15 weeks. The extra time versus a QuickBooks migration is almost entirely in the data extraction and validation phases. Everything from COA mapping onward is comparable.

1. Discovery (1 week): assess the Peachtree installation state, identify the PTB file version, run a test extraction to validate data quality, agree on cut-off date. Go/no-go gate: can the data be extracted cleanly or does it need remediation?
2. Data extraction and remediation (2–3 weeks): extract all extractable data via Peachtree CSV export and/or ODBC driver. Validate completeness against printed trial balance and AR/AP ageing reports. Remediate gaps: missing records, format inconsistencies, encoding issues.
3. COA mapping (1–2 weeks): map every Peachtree account to its equivalent in the new system's chart of accounts. Peachtree account numbering often has non-standard structures built up over years of ad-hoc customisation; expect more mapping decisions than a QuickBooks migration.
4. New system setup (2–3 weeks): Cambodian chart of accounts, tax codes, multi-currency configuration and bank journals, with the books kept in KHR at the official rate.
5. Data migration (1–2 weeks): load opening balances, open AR/AP, fixed-asset register, customer and vendor master. TINs must be populated before migration completes.
6. Parallel run (2–3 weeks): both systems through one full month-end. Reconcile to riel and cent.
7. Cutover (1 week): close Peachtree as active system. Archive data with documented access procedure. The new system produces the monthly return figures for the first period after cutover, and your accountant files them through E-Filing as before.

The return figures are not a job for the last week. The new system must produce the monthly return figures for the first period after cutover, so the tax codes and KHR handling go in during the setup phase and the figures are checked during the parallel run. See our accounting system solutions for the full scope, and our QuickBooks migration guide for the easier case this guide keeps comparing against.

Cost

A Peachtree migration for a single-entity Cambodia SMB typically runs $5,000–$12,000. The higher range versus QuickBooks reflects the additional extraction complexity. Data in poor shape (partially corrupted PTB files, 10+ years of unarchived history, or heavy ad-hoc customisation) pushes toward the top of the range. Clean, recent, well-maintained Peachtree installations with under 3 years of active history sit toward the bottom.

• Discovery sprint: $500 (deducted from project fee if you proceed). Discovery is non-negotiable for Peachtree; data state is too variable to skip.
• Migration build: $4,500–$11,500 depending on data state and scope.

Specific Peachtree data gotchas

Beyond the extraction complexity, Peachtree has several specific data and configuration patterns that create problems during migration. These are predictable if you know to look for them.

• Class and department codes: Peachtree uses 'classes' for cost-centre reporting. How each Peachtree class is carried into the new system must be decided explicitly before migration. Businesses that relied heavily on Peachtree class reporting will need those reports rebuilt in the new system.
• Custom report dependency: Peachtree installations often have extensive customised reports built up over years. These reports cannot be exported or converted; they must be rebuilt in the new system or in an external BI tool. List all critical reports used by the finance team and scope each one before the migration starts. Rebuilding 20 custom reports is a material deliverable, not a footnote.
• Bank reconciliation history: Peachtree's bank reconciliation records are not carried across. Bank reconciliation history stays in Peachtree. For the new system, import bank statements from the cut-off date forward and reconcile from that point. Historical bank reconciliation must be accessed in Peachtree.
• Fixed-asset depreciation history: as with QuickBooks, Peachtree's fixed-asset module (if used) stores depreciation history in its own format, which does not load directly into a new register. Rebuild the asset register in the new system from the depreciation schedule: original cost, acquisition date, method, accumulated depreciation to cut-off. If fixed assets were tracked in a separate Excel schedule outside Peachtree, that schedule is actually easier to work with than Peachtree's internal format.
• Inventory valuation methods: Peachtree supports FIFO, LIFO, and Average Cost inventory valuation. If the Peachtree installation used LIFO (seen in older installations with heritage from US accounting practices), moving off it is a valuation method change, with all the tax and compliance implications that entails. LIFO is not permitted under IFRS, and Cambodia reports under CIFRS, so a LIFO-based Peachtree file is a finding to raise with your auditor, not just a migration detail.
• Encoding issues for Khmer data: Peachtree Desktop on older Windows installations stores text in Windows-1252 (ANSI) encoding. Any Khmer characters in product names, customer names, or address fields are stored incorrectly in this encoding. When extracted and loaded into the new system, garbled characters appear. Run an encoding audit during extraction, not after migration, and remediate affected records before loading.
• Peachtree multi-company: some Cambodia businesses ran multiple companies in Peachtree as separate Peachtree company files (separate PTB files). Each company file is a separate migration project. Do not underestimate the effort when multiple entities are in scope.

Read the second column down and the shape of the job appears: the current position carries, the history mostly does not. Opening balances, open invoices and the master records load in the data migration phase, while bank reconciliation history, custom reports and historical reports stay in Peachtree or have to be rebuilt in the new system. Which of these rows bites hardest is not something the table can tell you in advance, which is why the guide puts discovery first: discovery is mandatory before quoting a Peachtree migration; the data state is too variable to estimate blind.

When to migrate vs stay

Migrate now if: CamInvoice is in scope for your business (government contracts); your Peachtree installation is showing instability (corruption, performance issues, Windows OS compatibility problems); you have grown past 5 accounting users and the per-seat workflow is creating bottlenecks; or a GDT audit has surfaced discrepancies that trace back to Peachtree's rounding or WHT code limitations. Defer if: your business is USD-only, below the VAT registration trigger, and Peachtree is stable with no near-term compliance trigger. No CamInvoice B2B mandate date has been published, so there is no deadline to count back from; decide on the business case rather than on a rumoured date. If your Peachtree installation is on Windows 7 or an older OS, the hardware dependency is the more urgent forcing function: an OS failure with no recovery path is a worse disruption than a planned migration.

FAQ

Can we access Peachtree data after migration?

Yes. Keep the Peachtree installation on an archived machine or VM for historical reference. Cambodia's ten-year retention rule means you need it for a decade from when the records were created, not a handful of years. Document the archive location and access credentials before migration closes. Do not rely on being able to reinstall Peachtree from old media; the installer may not activate on modern hardware without a Sage licence renewal.

What is the Sage 50 support status in Cambodia?

The product is not discontinued: the current release is Sage 50 Accounting 2026 and Sage still sells it. What bites in Cambodia is the obsolescence policy, under which only the current version is supported. An installation two or three versions behind has already lost program and tax updates, tax forms, e-filing, bank feeds, and payment processing. Local resellers still market it as 'Sage 50 (formerly Peachtree)' in Phnom Penh and are the primary support channel; if yours is no longer active you are running an unsupported installation with no path to updates, which alone is a reason to migrate before a critical bug surfaces.

Do we lose our historical reports?

Historical reports stay in Peachtree as long as the software is accessible. Export all critical historical reports (trial balances, P&L, balance sheet, AR/AP ageing) in PDF and Excel before migration closes; do not rely solely on the archived software for historical report access. Software licence expiry or hardware failure can make the Peachtree archive inaccessible.

How long does training take on the new system?

Budget 2–5 days of structured training per accounting user, plus 30 days of supported live use. Accountants who have used Peachtree for many years are changing habits as well as software, so do not cut this to a one-hour walkthrough.

Can we migrate Peachtree payroll?

Peachtree payroll (if in use) can move to the new system. Payroll migration requires mapping Peachtree pay codes to the new system's pay rules and verifying that Cambodian Tax on Salary calculations match. Treat it as a separate deliverable, not bundled into the core accounting migration.

What about ABA, Wing or Bakong bank feeds?

Plan to reconcile bank statements in the new system from the cut-off date forward. A direct connection to a bank is separate integration work, scoped through our API integration practice.

Is the migration disruptive to daily operations?

A well-run migration with adequate parallel-run time should not disrupt daily operations. The parallel-run phase (both systems open simultaneously) is the most operationally demanding: accounting staff are double-posting for one month-end cycle. Communicate this clearly before the migration starts and ensure accounting capacity is not constrained during that period.