What does a cloud migration actually cost in Australia?

Much less than the published numbers suggest for a small business. Figures of twenty thousand dollars and upwards describe enterprise consulting projects. A ten-person business moving email, files and one application is a scoped project measured in days of work, and the price is driven by how many systems move and how awkward each one is.

The first thing to do with any figure you find is ask who it was written for. Search this question and you will meet Australian articles quoting around twenty-one thousand dollars for small business and international ones starting at forty. Those describe engagements involving application re-architecture, dedicated project management and organisational change programmes for organisations with hundreds of staff. Applying them to a small business is like pricing a house extension from a commercial construction index, and the main effect is to frighten people out of a sensible decision.

What actually drives the price is legible once you name it. How many systems move, since email and files are well-trodden while a line-of-business database with an on-premise dependency is real work. How awkward each is: a modern application with a supported hosted version is straightforward, and one whose vendor last certified a platform a decade ago is not. How much data has to move, which interacts with your connection speed. How many integrations need reconfiguring and verifying, which is usually the largest hidden pool of effort. And how much of the work you buy versus absorb internally.

Then the costs quotes routinely omit, and each has caught businesses out. Running two environments in parallel during the transition, because the old system stays until the new one is proven, which is correct practice and does mean paying twice for a period. Reconfiguring every connected system: the scanner, the accounting integration, the enquiry form, the practice or job-management software. Staff time, both in the disruption and in the questions afterwards. Decommissioning the old kit properly, including secure data destruction and documenting it. And the ongoing cloud bill itself, which is not the migration cost but is the number that will still be there next year.

That last point deserves its own warning, because it is where budgets actually go wrong. Badly designed cloud is expensive cloud, and the classic error is a straight lift of a server into a virtual machine left running at full size twenty-four hours a day. The infrastructure is elastic; a copied server is not, so you pay for peak capacity permanently. A design that sizes to the workload, uses managed services where they fit and shuts down what does not need to run costs materially less every month, forever, and that difference dwarfs any argument about the one-off migration fee.

For comparing quotes, insist on the same five things from everyone: exactly which systems are in scope, which integrations will be migrated and individually verified, what the cutover plan and rollback path are, what the estimated monthly running cost will be afterwards, and what happens if it takes longer than planned. A provider who answers all five in writing is quoting the job you are trying to buy. One quoting a single number for a cloud migration is quoting a phrase.

One structural saving is worth knowing about before you budget, because it is routinely missed. Both major providers discount heavily for committed usage, so an environment you expect to run for years can be reserved rather than paid at on-demand rates, and the difference is substantial. It is a decision to make deliberately once the design has settled and the sizing is known, rather than at sign-up, but it belongs in the five-year comparison rather than being discovered a year later by someone reading the invoice.

The honest caveat is that the cheapest migration quote is frequently the most expensive outcome, and the mechanism is predictable. Corners get cut at exactly the points that are invisible until later: integrations moved but not tested, no failover on the connection, no rollback path, and infrastructure sized by copying rather than designing. The first two show up on the first Monday, the third when something goes wrong, and the fourth every month on the bill. Ask what is excluded as carefully as you read what is included. If you want yours scoped against a written plan rather than a headline number, call 1800 456 567.