// Cloud Migration, Sydney

Move to the cloud without betting the business.

Here's the short version: a good cloud migration is staged, reversible and boring. Email and phones first, files next, servers case by case. Anyone who quotes you an all-in migration without auditing what you actually run is selling, not advising. I do the audit first, give you a fixed quote, then move things in an order where nothing breaks on a Friday.

A cloud migration isn't one big lift. It's a series of small, separate moves: your email, your files, your phones, your apps. Each one has its own risks and its own rollback plan. Before anyone touches anything, these are the questions worth asking, of me or of whoever else you're talking to.

  • What actually needs to move, and what's fine where it is?
  • What happens to email mid-move? Does anything get lost in flight?
  • Can each stage be rolled back if something's off?
  • Who owns the data and the licences afterwards, you or the provider?
  • Can your internet connection handle everything living offsite?
  • What gets decommissioned, when, and who wipes the old drives?

If the person quoting you can't answer these in plain English, keep shopping.

// The honest bit

Migration is not "move everything."

The right migration for most Sydney small businesses is partial. Email and phones are almost always worth moving: they're cheap in the cloud, they work from anywhere, and on-premise mail servers stopped making sense years ago. Files usually follow. Servers and apps are where it gets interesting.

That ten-year-old accounting package running happily on a server in the corner? Forcing it into the cloud can cost more than the server is worth and run worse than it does now. Often the smart move is leaving it exactly where it is with a proper cloud backup behind it. Hybrid isn't a compromise, it's usually the correct answer.

So here's my rule: anyone who quotes you "all-in" without an audit is selling you their product, not solving your problem. The audit comes first. Then you decide what moves.

// Scope

What we migrate.

  • Email to Microsoft 365. Mailboxes, shared mailboxes, calendars and contacts, with mail flowing the whole time. Nothing lost in flight.
  • Files to SharePoint, OneDrive or a hosted file server. Permissions mapped properly, not dumped in one folder for everyone to see.
  • Phones to VoIP. Keep your numbers, drop the line rental, answer the office phone from anywhere.
  • Servers and apps to Azure or our own hosted infrastructure. Or they stay on-premise with cloud backup behind them, whichever actually fits.
  • Identity. One login for everything, with multi-factor authentication on from day one, not bolted on later.

On the vendor question: I resell Microsoft's cloud and I run my own data centre. I genuinely don't care which one you end up on. That's the point of being on both sides, I recommend what fits your business, not whichever platform pays better.

// The process

Audit, plan, cutover, verify, decommission.

Five stages, in order, no skipping. The whole design goal is that every step is reversible until it's proven.

  • Audit. What you run, what talks to what, and where the legacy weirdness hides. This is where surprises get found, on paper instead of mid-migration.
  • Plan. The order of moves, a rollback point for every stage, and a fixed quote. You see the whole map before anything moves.
  • Staged cutover. After hours, one service at a time. The old system stays live in parallel until the new one is proven. Nothing breaks on a Friday because nothing cuts over on a Friday.
  • Verify. Your people actually working on the new system. "It pings" is not verification, "the whole team got through Monday without noticing" is.
  • Decommission. Only after everything is verified. Old servers retired or repurposed, drives wiped properly, licences tidied up.

// Cost

What it costs.

Depends on three things: how many mailboxes and users you have, how much data is moving, and how much legacy weirdness is in the mix. A ten-person office on straightforward email and files is a small, predictable job. Custom apps on an ageing server talking to a database nobody remembers is a different conversation, and pretending otherwise is how migrations blow out.

That's why I don't publish a number for this one. Any figure I put here would be wrong for your business in one direction or the other. What you get instead: a short audit, then a fixed quote that doesn't creep. If the audit shows some things shouldn't move at all, the quote will say that too.

// Why us

Why us.

  • 18 years doing this. I've migrated businesses onto the cloud, off the cloud, and between clouds. The pattern of what goes wrong is well worn.
  • Own infrastructure. I run my own data centre and servers, so cloud isn't a product I read about in a partner brochure, it's gear I operate.
  • No lock-in. Your data and licences stay in your name. If you leave, you take everything with you and it's all documented.
  • Plain English. You get told what's moving, why, what it costs and what the rollback is. No jargon, no surprise invoices.

// Questions

Cloud migration, your questions answered.

How much downtime will a cloud migration cause?

Close to none if it's staged properly. Cutovers happen after hours, one service at a time, and the old system stays live until the new one is verified. Your team logs off Friday on the old system and logs on Monday to the new one. Days of downtime means the migration was planned badly, not that migrations are risky.

How long does a cloud migration take?

For a typical Sydney small business, email and phones move within days. Files take longer because permissions need to be mapped properly, usually a week or two elapsed. Servers and line-of-business apps are case by case, some move in a weekend, some should not move at all. The audit gives you a real timeline, not a guess.

Can we go back if it doesn't work out?

Yes. Every stage has a rollback point, and nothing gets decommissioned until the new system is verified in real use. Your data stays yours, your licences stay yours, and there are no lock-in contracts. If a stage isn't working, we roll it back and rethink it rather than pushing through.

Microsoft 365 or Google Workspace?

Microsoft 365 for most Sydney small businesses. If your team lives in Word, Excel and Outlook on Windows machines, M365 is the natural fit and the integration with everything else is stronger. Google Workspace suits some teams, and if that's you I'll say so. I sell the one that fits, not the one with the better margin.

What happens to our old server?

Three options: retire it, keep it for a local job like file caching or a legacy app with cloud backup behind it, or repurpose it. Nothing is switched off until every service on it has been verified elsewhere. When it does go, the drives are wiped properly, not just formatted.

Do we have to move everything to the cloud?

No, and for most small businesses you shouldn't. Email and phones are almost always worth moving. An old app that runs fine on a server in the corner is often better staying put with a proper cloud backup behind it. Hybrid isn't a compromise, it's usually the right answer.

// Pairs well with

Not sure what should move and what should stay?

Tell me what you're running and I'll come back with a staged plan and a fixed quote. No pressure, no jargon, no all-in sales pitch.

Beam us a message 🛸