Cloud Migration Mistakes to Avoid and How to Get It Right

A manufacturing business in West Auckland decided to move everything to the cloud over a long weekend. By Tuesday, staff could not open their shared drives, two line-of-business apps refused to talk to each other, and the monthly bill from the provider came in at roughly three times what anyone had budgeted. None of this was bad luck. It was the predictable result of treating migration as a switch you flip rather than a project you plan.

Most cloud migrations for Kiwi SMEs go sideways for the same handful of reasons. The good news is that every one of them is avoidable once you know what to look for.

Why do cloud migrations go wrong?

The failures rarely come from the technology. Microsoft 365, Azure, AWS and Google Workspace are mature platforms that handle far bigger workloads than any New Zealand SME will throw at them. Problems come from the decisions made before, during and after the move.

The common ones look like this:

• Lifting and shifting everything as-is, including apps that should have been retired years ago.
• No clear owner, so the project stalls whenever someone goes on leave.
• Picking a platform because a competitor uses it, not because it suits your workloads.
• Forgetting that staff need time and training to adjust to new ways of working.

A migration touches finance, operations and almost every staff member. Treat it as a business change with an IT component, not an IT job that happens to affect the business.

Mistake one: moving everything without sorting it first

The instinct to move the lot in one go is understandable. It feels efficient. In practice it carries every piece of technical debt you have accumulated straight into your new environment, and you pay to host it.

Before anything moves, build a simple inventory of what you actually run. List each application, who uses it, how often, and whether it still earns its place. You will usually find software nobody has opened in eighteen months, duplicate tools doing the same job, and at least one ageing app the vendor no longer supports.

Sort each item into one of four buckets:

• Retire the things you no longer need.
• Replace old apps with a modern cloud-native equivalent where one exists.
• Rehost the workloads that move cleanly as they are.
• Rebuild the few that need real work to function well in the cloud.

This single exercise often cuts the migration scope by a third and the ongoing bill along with it.

Mistake two: ignoring the real cost

Cloud pricing looks cheap on the brochure and surprises people on the invoice. The headline per-user figure is only part of the picture. Data egress charges, storage tiers, backup, premium support and the licensing for security tools all add up.

The other trap is assuming cloud is automatically cheaper than the server in the cupboard. Sometimes it is, sometimes it is not. A workload that runs flat out twenty-four hours a day can cost more in the cloud than on hardware you already own. The win from cloud is usually flexibility, resilience and getting out of the hardware refresh cycle, not always a lower monthly number.

Model the cost properly before you commit. Take your real usage figures, price them against the platform you are considering, and build in a buffer for the first few months while everyone learns where the meter runs fast. Set billing alerts from day one so a runaway process does not become a four-figure surprise.

Mistake three: leaving security and the Privacy Act as an afterthought

Moving to the cloud does not hand your security responsibilities to the provider. They secure the platform. You remain responsible for who can access your data, how it is configured, and what happens when an account is compromised. This split catches a lot of businesses out.

Under the Privacy Act 2020, your obligations follow the data wherever it lives. If you hold personal information about customers or staff, you need to know which country it is stored in, who can reach it, and how you would respond to a notifiable privacy breach. CERT NZ continues to report that credential theft and misconfigured cloud storage are among the most common ways New Zealand organisations get caught out.

A few non-negotiables for any migration:

• Multi-factor authentication on every account, no exceptions for the directors.
• Least-privilege access, so staff can reach only what their role requires.
• A backup that is separate from the live environment, because cloud platforms protect against their own faults, not against you deleting the wrong folder.
• Knowing your data residency, particularly for anything sensitive.

Build these in as you migrate. Retrofitting security after the fact is slower, more expensive and leaves gaps in the meantime.

Mistake four: forgetting the people

You can execute a flawless technical migration and still have a failure on your hands if staff cannot do their jobs on Monday morning. People are the part most often left out of the plan.

Tell staff what is changing and when, well before it happens. Run short training sessions on the new tools rather than emailing a PDF and hoping. Pick a quiet week for the cutover, not month-end. Have proper support ready for the first fortnight, because that is when the questions come thick and fast.

The businesses that adopt cloud well treat the rollout as a chance to improve how people work, not only where the files sit. Shared documents that several people edit at once, video calls that just work, and access from any device are the changes staff actually notice and value.

How to get it right

A migration that goes smoothly usually follows the same shape. Start with the inventory and the cost model. Pick the platform that fits your workloads and your team, not the one with the loudest marketing. Move in phases, beginning with something low-risk like email or file storage, so you learn the process before you touch anything mission-critical.

Test each phase with real users before you call it done. Keep the old system available as a fallback until the new one has proven itself. And once everything has settled, go back and tidy up, turn off the workloads you parked, right-size what you over-provisioned, and review the access list.

Done this way, cloud migration stops being a gamble and becomes a steady, predictable improvement to how your business runs.

If you are weighing up a move to the cloud and want a second opinion on the plan before you commit, the team at iT360 works with SMEs across New Zealand and is happy to talk it through.