ERP Data Migration

ERP Opening Balances and Cut-over: The Migration Step Most Projects Underestimate

Star Bit Solutions9 min read

ERP opening balances decide whether your first month in a new system starts clean or starts with a suspense account. This guide covers the cut-over date, the freeze, the stock count, open items, validation and a way back.

A cut-over line between an old and a new system, with balances, open items and a stock count crossing it, a freeze chip and a rollback arrow
Scroll

Key takeaways

  • Load anything that will be paid, chased or matched as an open item; everything else needs only a balance.
  • Cut over on the first day of a financial year or VAT period, and plan for final balances to arrive weeks later.
  • Count stock at cut-over, load it at agreed costs and book its value once, through the count or the opening entry.
  • Load receivables and payables through clearing accounts, and do not go live until every clearing account is at zero.
  • Write the rollback plan before go-live, and use parallel running only where it earns its cost, such as payroll.

Most enterprise resource planning (ERP) projects spend months on configuration and a weekend on the cut-over. That weekend is when the numbers move from the old system to the new one, and it is where avoidable problems surface: a receivable that will not match, stock valued twice, a suspense account nobody can explain three months later.

Getting ERP opening balances right is less about software than about timing, sequence and evidence. This guide sets out how we plan the cut-over on StarBiz and Odoo projects: what to load as balances and what as open items, how to choose the date, what to freeze, how to count stock, how to prove the numbers and what to do if go-live has to be reversed.

Balances versus Open Items

An opening balance is one figure per account: the bank balance, the cost of fixed assets, accrued expenses, share capital. An open item is a document still in progress: an unpaid invoice, a supplier bill, an advance, a check that has not cleared. The new system needs both, in different forms.

The test is simple. If anyone will need to settle, chase, match or age it after go-live, load it as an open item. If not, a balance is enough.

AreaLoad asDetail neededProve it with
Bank and cashBalance, plus uncleared itemsStatement balance, unpresented checksBank reconciliation at cut-over
ReceivablesOpen items per customerNumber, dates, amount due, currencyAging by customer
PayablesOpen items per supplierNumber, dates, amount due, currencyAging by supplier
StockQuantities at agreed costProduct, location, lot, unit costCount sheets and valuation
Fixed assetsAsset registerCost, depreciation to date, remaining lifeRegister against the ledger
Value added tax (VAT)Balances on VAT accountsPeriods already filedLast return and VAT ledgers
Everything elseBalance per accountAccount mappingTrial balance comparison

Fixed assets deserve a note. Load each asset with its cost, acquisition date, depreciation to date and remaining life, so the new system continues the schedule instead of restarting it, and later disposals calculate the right gain or loss.

Choosing the Cut-over Date

There is no perfect date, only better and worse ones. In order of preference: the first day of a financial year, the first day of a VAT period, then the first day of a month. A mid-month cut-over splits everything, because a VAT return, a payroll run and a month-end close all draw on two systems.

Check the date against these constraints before you commit:

  • VAT: a split period makes the reconciliation step in our UAE VAT return workflow harder, because each box needs figures from both systems.
  • Payroll: start at the beginning of a pay cycle, with leave balances and end-of-service accruals carried across.
  • Audit: if the year-end audit is close, finishing the year in the old system keeps the auditors' evidence in one place.
  • Operations: avoid peak weeks, public holidays and the weeks when key people are away.
  • Stock: pick a day when the warehouse can stop for the count.

Then accept that final balances arrive late. The old system still has to close its last period, with accruals, depreciation, currency revaluation and audit adjustments, and that can take weeks. Plan two passes: provisional balances at go-live so operations can start, then a true-up entry in the new system, dated with the opening entry, once the old books are final.

The Freeze Period

The freeze is a short window, usually a few days either side of the cut-over, when the data behind the opening balances must stop changing. Without it, you load a moving target.

  • New customers, suppliers and products go through a change log, not straight into the old system.
  • No back-dated entries in the old system after the cut-off, unless finance approves and logs them.
  • Receipts and deliveries finish before the stock count starts.
  • Configuration in the new system is frozen too, apart from agreed fixes.

Give the freeze log an owner. Every exception is either re-entered in the new system or deliberately left in the old one, never both. Tell customers and suppliers in advance if invoice numbers, statements or payment details will change.

Have a question about this guide? Ask the engineers who wrote it.

The Stock Count at Cut-over

Stock is often the largest figure in the opening balance sheet and the hardest to get right, because it carries quantity, location, lot, cost and value at once. A procedure that works:

  1. Stop movements: finish receipts and deliveries, and pause picking.
  2. Count by location with blind count sheets, so counters do not see expected quantities.
  3. Recount any difference above a tolerance agreed in advance.
  4. Post the count in the old system, so its closing stock equals the count.
  5. Agree each product's unit cost with finance.
  6. Load quantities by product, location and lot at those costs.
  7. Check that quantity times cost equals the stock value in the opening trial balance.

Then settle the edge cases: goods in transit, goods received but not invoiced, consignment stock and goods held for customers. Each needs a decision on which side of the cut-over it falls, and whether it sits in stock, in payables or in neither. If the new system values stock automatically, loading the count may post its value to the ledger, so book the value once, through the count or through the opening entry, never both.

Receivables and Payables at Document Level

A receivable balance tells you the total, but it does not let anyone collect it. Load every open customer invoice and supplier bill as its own document, with the partner, original number, invoice date, due date, amount still due and currency. Watch the special cases:

  • Part-paid invoices: load the amount still due, and keep the original total in the reference.
  • Advances and unallocated receipts: load them as credits on the partner, ready to apply later.
  • Unused credit notes: load them as credit notes, not negative invoices.
  • Foreign currency: load the original currency amount and the rate used in the old books, so revaluation starts from the right base.
  • Post-dated checks: common in the UAE, they need a decision on whether they sit in receivables, in a separate account or in a check register.
  • Retentions: load them as separate items with their own due dates.

Load these documents against clearing accounts, and in the opening trial balance replace the receivable and payable lines with the same clearing accounts. Do not charge VAT again: the VAT on these documents was recorded in the old system and arrives through the VAT balances.

A Worked Example: Proving the Receivable

The old trial balance shows receivables of AED 250,000. Its aging report lists open invoices of AED 262,000 and unapplied customer credits of AED 12,000. In the new system:

  1. The opening entry debits AED 250,000 to the receivable clearing account instead of receivables.
  2. The open invoices debit receivables by AED 262,000 and credit the clearing account by the same amount.
  3. The credits debit the clearing account by AED 12,000 and credit receivables.

The clearing account ends at zero, and receivables show AED 250,000, now split by customer and invoice. If the clearing account shows a balance instead, such as AED 3,000, something was missed, perhaps a credit note, and you find out before go-live rather than at the first month-end.

Validating ERP Opening Balances

Validation is a finance sign-off with evidence, not a glance at the trial balance. Build a reconciliation pack and have the finance lead sign each line:

  • The new trial balance matches the old one at cut-over, account by account, after mapping.
  • Receivable and payable aging matches in total and partner by partner.
  • Every clearing account is at zero.
  • Stock quantities match the count, and stock value matches the stock accounts.
  • Bank balances match the statements, with uncleared items listed.
  • The fixed asset register matches the cost and accumulated depreciation accounts.
  • VAT balances match the old VAT ledgers and the last return filed.
  • Sample transactions work: a statement prints correctly, an invoice can be paid and a bill can be matched.

Then lock the opening period so nobody posts into it by mistake. StarBiz has fiscal-year locks and period closing controls, and Odoo has lock dates, described in its year-end closing documentation.

Tip: write a cut-over runbook listing every step in order, with its owner, expected duration and check. Use it for each rehearsal on a copy of the new system, and on the day, tick it off line by line.

A Rollback Plan You Hope Never to Use

Every cut-over needs a way back, written down before go-live. A rollback plan is not pessimism. It is what lets the steering group approve go-live with confidence.

  1. Go or no-go criteria: validation passed, key users trained, integrations tested and support cover booked.
  2. A decision point: a named person, a time and the checks that must pass by then.
  3. The old system kept intact: closed for posting, but able to reopen if needed.
  4. A log of everything entered in the new system after go-live, so it can be re-keyed in the old one.
  5. Messages ready for staff, customers and banks.

Agree where the point of no return lies. It usually arrives when invoices with new numbers have reached customers, or payments have run from the new system. After that, problems are fixed forward, which is why hypercare, the period of close support straight after go-live, matters.

Parallel Running: Pros and Cons

Parallel running means entering the same transactions in both systems for a period and comparing the results. It sounds like the safest option, and for some processes it is.

It helps whenIt hurts when
Errors hit people directly, as in payrollTeams have no spare time for double entry
A complex calculation, such as costing, must be provenProcesses change, so results cannot be compared
Auditors, lenders or a parent company ask for evidenceIt drags on, and users keep trusting the old system

A middle path often works better: run payroll or one critical process in parallel for a cycle, and rely on rehearsals, the validation pack and the rollback plan for everything else.

How Star Bit Solutions Can Help

Cut-over is part of every implementation we run. On StarBiz, our AI-driven ERP, the migrate and train phase covers cleaned master data, opening balances, role-based training and user acceptance testing, followed by a supported cut-over and hypercare. On Odoo Enterprise or Community, our OdooStar team handles extraction, cleansing and mapping, reconciled opening balances and, where it earns its cost, a parallel run.

Moving from Tally? Our Tally to Odoo migration plan applies these steps to one source system. For anything else, send us your current system, preferred go-live month and year-end through the contact page or on +971 55 973 4524, and an engineer will outline a cut-over plan.

Star Bit Solutions logo
Written by the Star Bit Solutions team

Star Bit Solutions is a software company in Ajman, UAE, founded in 2014. We implement and customize Odoo Enterprise and Odoo Community, and build StarBiz (AI-driven ERP), StarHub (life super app), StarBot (conversational AI), StarLearn (adaptive learning) and StarSense (AI and IoT platform). About us

OdooStar by Star Bit Solutions

Start the New System on Numbers That Already Match.

Tell us your current system and target go-live month. We will plan the cut-over, load the opening balances and prove them with your finance team.

Not Sure Which Solution Fits?

Tell us about your business and we will recommend the right starting point, free of charge.