# Switching Accounting Software in the UAE: A Migration Checklist > Most businesses delay changing systems because migration sounds frightening. It is mostly sequencing — here is the order that keeps your VAT position intact. - URL: https://www.pyalm.com/blog/switching-accounting-software-uae-migration-guide - Author: Fadhil Abdulla - Category: Pyalm Books - Published: 2026-08-01 - Updated: 2026-08-01 --- Businesses stay on software that no longer fits for one reason above all others: moving sounds risky. It is a manageable project if you do it in the right order, and the right order is mostly about picking a clean break point and carrying balances rather than history. ## Pick the cut-over date first Everything else follows from this. The two sensible options: **The start of a VAT period.** The cleanest choice for a UAE business. One system produces one full return, the next produces the next. No period is split across two systems, and if a return is ever queried you can point at one source. **The start of a financial year.** Cleanest for annual reporting, and the obvious choice if you are also changing accountants. What to avoid is a mid-period switch. Splitting a VAT quarter across two systems means assembling one return from two places — exactly the situation you are trying to leave behind. Give yourself a parallel window: the new system live from the cut-over date, the old system still accessible in read-only form for at least a full year. ## Decide what actually moves The instinct is to migrate everything. Resist it. Most migrations only need: **Master data — move it:** - Customers, with **TRNs**, addresses, payment terms and credit limits - Suppliers, with the same - Products, with cost, price, barcodes, categories and VAT treatment - Chart of accounts, mapped to the new structure **Balances at cut-over — move them:** - Trial balance as at the day before go-live - **Open customer invoices**, individually, with original dates and amounts, so ageing survives - **Open supplier bills**, likewise - Stock on hand by item, with quantity and valuation - Bank balances, and any unreconciled items - VAT position — anything due or recoverable at cut-over **Transaction history — usually leave it:** - Closed invoices, historical journals, prior-year detail You are legally required to retain records, but retention does not mean re-entry. Keep the old system readable, export the history, and start clean. Businesses that insist on importing five years of transactions typically spend most of the project on it and inherit the old system's errors. ## Get the opening balances right This is where migrations actually fail. Two rules: **One, the opening trial balance must balance.** If it does not, stop and find out why before entering a single new transaction. A migration that starts out of balance never quietly comes right. **Two, open invoices go in individually, not as a lump.** A single "receivables AED 340,000" opening entry destroys your ageing, your statements, and your ability to chase anything. Each open invoice needs its own original date and amount so the ageing report is true from day one. [Pyalm Books](https://www.pyalm.com/books) supports opening balances and transaction locking directly, so the cut-over position can be entered, agreed with your accountant, and then locked. ## Check the compliance ground before you move While you are changing systems anyway, confirm the destination handles what you need: - Standard, zero-rated and exempt supplies as distinct treatments — see [zero-rated vs exempt supplies](https://www.pyalm.com/blog/zero-rated-vs-exempt-supplies-uae) - A VAT return produced from the ledger - **Structured e-invoicing** with all mandatory fields, not PDF generation — see [e-invoice vs PDF invoice](https://www.pyalm.com/blog/e-invoice-vs-pdf-invoice) - Bilingual Arabic/English documents if your customers require them - Access for your accountant The [e-invoicing readiness checker](https://www.pyalm.com/free-tools/einvoicing-readiness-checker) is a quick way to sanity-check the destination before you commit. ## A workable sequence 1. **Choose the cut-over date** — start of a VAT period, four to six weeks out 2. **Export master data** from the old system and clean it — dead customers, duplicate products, obsolete accounts 3. **Set up the new system** — chart of accounts, VAT treatments, users and roles 4. **Import master data** and check a sample by hand 5. **Run a test transaction of each type** — credit sale, counter sale, supplier bill, credit note, payment 6. **Freeze the old system** at the cut-over date 7. **Enter opening balances**, confirm the trial balance agrees, and lock the period 8. **Go live**, keeping the old system readable 9. **Reconcile the first month carefully** — bank, stock, receivables 10. **File the first VAT return** from the new system, with your accountant reviewing it ## The one thing not to do Do not run both systems properly for months "to be safe". Double entry into two systems means two versions of the truth and twice the work, and the moment they disagree you have no idea which is right. Cut over cleanly, keep the old one readable, and move on. [Explore Pyalm Books](https://www.pyalm.com/books) | [Take the ERP readiness assessment](https://www.pyalm.com/free-tools/erp-readiness-assessment)