ERP cutover guideAustralian small business

How Much Downtime Should You Expect When Switching ERP Systems?

ERP cutover downtime is usually a weekend plus a few slower days. See typical downtime by business type, parallel running and the best dates to switch.

Last reviewed: 5 November 2026

Connected small business ERP workflows for orders, invoices and reporting

Quick answer: ERP cutover downtime for most Australian SMBs is one weekend of frozen transactions, followed by two to five days of slower work while staff settle in. With good planning, nobody stops trading. Downtime runs longer when stock counts, open orders or payroll must be rebuilt, so warehouses and manufacturers should allow one to three days.

This is for owners, finance leads and operations managers who are about to move off MYOB, Xero, an old ERP or a pile of spreadsheets and want a straight answer on how long the business will be disrupted. If you're still choosing a platform or partner, start with our guide to moving ERP systems in Australia, then come back here for the go-live detail.

Why does switching ERP systems cause downtime at all?

ERP cutover downtime happens because two systems can't both be the source of truth at once. Cutover is the short window where you stop entering transactions in the old system, move the final balances and open items across, check they reconcile, and switch everyone to the new one.

Most of the data (customers, products, suppliers, history) moves weeks earlier. What's left for cutover weekend is the moving part: closing stock, open sales and purchase orders, unpaid invoices, bank balances and year-to-date payroll. Those numbers change every hour you trade, which is why they get frozen.

The downtime people remember is rarely the weekend. It's the first week, when a picker can't find a screen or an invoice template looks wrong. That part is a training and testing problem, and it's the part you can control.

How long will our business actually be down, by business type?

ERP go-live downtime depends far more on what you hold and ship than on headcount. The table below is a planning guide based on typical SMB projects, not a guarantee.

Business typeTypical transaction freezeSlower period after go-liveWhat drives it
Professional services (no stock)Half a day to 1 day2 to 3 daysOpen invoices, WIP and timesheets
Retail or ecommerceOvernight to 1 day3 to 5 daysStock levels, Shopify or POS sync
Wholesale and distribution1 to 2 days1 to 2 weeksStocktake, open orders, pricing rules
Manufacturing2 to 3 days2 to 3 weeksWork in progress, bills of materials, costing
Multi-entity groups1 to 2 days per entity1 to 2 weeksIntercompany balances, consolidation

Take a 35-person Melbourne wholesaler moving from Xero and spreadsheets to an ERP. A realistic plan is a final stocktake on Friday afternoon, orders taken on paper or in a holding list on Saturday morning, opening balances loaded and checked on Saturday, and a test pick and invoice on Sunday. Monday trades in the new system with the partner on site. [ADD STAT: optional, Zynex average cutover hours for a wholesale client, if Amit wants a figure here]

Should we run the old and new systems side by side?

ERP parallel running means entering every transaction in both systems for a period and reconciling daily. It sounds safe. For most SMBs it isn't worth it.

Double entry doubles the workload at the exact moment staff are learning a new system, and small differences between the two systems create reconciliation noise that hides real errors. We usually recommend parallel running only for payroll for one cycle, or for a single high-risk area like manufacturing costing. A cleaner option is a short "shadow" period: the new system is live, and finance runs a few key reports from the old one for a week to confirm the numbers line up.

What you do need is a documented back-out plan. Decide in advance what would trigger going back, who makes the call, and how transactions entered in the new system would be re-keyed. You'll almost certainly never use it, but having it makes the go or no-go decision calmer.

When is the least disruptive time for an Australian business to switch?

The best ERP cutover date in Australia is the start of a month that isn't a BAS month and isn't near 30 June. Cutting over at a period end means you load clean closing balances and avoid splitting one month across two systems.

  • Avoid the BAS crunch. Quarterly BAS is generally due on the 28th of the month after each quarter (28 October, 28 February, 28 April and 28 July), per the ATO's BAS due dates. Don't go live while finance is preparing one.
  • Plan payroll carefully. If payroll moves too, the ATO's guidance on changing your payroll solution explains when you must notify it about transferred year-to-date amounts, and that STP finalisation for each ABN, branch and payroll ID combination is due by 14 July. A 1 July payroll switch avoids most of that.
  • Respect your peak season. A retailer shouldn't go live in November or December. A builder probably shouldn't go live in the last fortnight before the Christmas shutdown.
  • Pick a quiet weekend with no public holiday on the Monday, so your partner and super-users are all available on day one.

What should be on our ERP cutover checklist?

An ERP cutover checklist is a dated, owner-assigned list of every step between "stop trading in the old system" and "first real invoice in the new one". These are the items that most often decide whether downtime is one weekend or one week.

  • Sign off user acceptance testing at least two weeks before go-live, including day-one reports.
  • Run at least one full mock cutover with real data and time it.
  • Set a master data freeze: no new products, customers or suppliers in the old system in the final week.
  • Agree department cut-off times (last shipment, last receipt, last invoice, last payment run).
  • Complete a stocktake as close to cutover as possible.
  • Load and reconcile opening balances: trial balance, debtors, creditors, stock value and bank.
  • Test integrations (bank feeds, Shopify, EDI, payroll) with live credentials.
  • Confirm a go or no-go decision point, the back-out plan and who has authority to call it.
  • Book on-site or hyper-care support for the first one to two weeks.
  • Keep read-only access to the old system for audit and history.

When can you handle cutover yourself, and when should you bring in help?

You can run cutover in-house if you're a services business with no stock, one entity, payroll staying put, and a vendor-guided setup like Xero to a cloud ERP with a standard import. Plenty of small firms do this over a weekend with good notes.

Bring in an experienced partner if you hold stock in more than one location, manufacture, run several entities, move payroll, or rely on integrations that take orders. Those are the cutovers that go wrong quietly: the system is live, but stock is off by a few per cent and nobody notices for three weeks. Zynex Technologies is a Melbourne-based consultancy that plans and runs ERP cutovers for Odoo implementations and SAP Business One projects, as well as Zoho and ERPNext, and we'd rather spend an extra day on a mock cutover than a week fixing balances.

Plan your next steps with Zynex Technologies

Planning a go-live and want a second opinion?

If you're worried the switch will stop dispatch, payroll or month-end, book a call with our Melbourne team. We'll look at your current systems and tell you how long your cutover should really take and where it's likely to slip.

Book a call