Move it once,
move it properly.

Assessment, planning, and execution of a move to cloud, with an honest view of which workloads should move, which should not, and what it will cost to run afterwards. It is for organisations with ageing on-premise infrastructure approaching a refresh decision.

Not automatically, and often not at all if you move things unchanged. Cloud replaces a capital purchase every five years with a monthly bill that never stops, and a server lifted across as-is runs at full size around the clock whether or not anyone is using it. Cloud wins on flexibility, on resilience, and on removing hardware refresh cycles. It wins on cost when workloads vary, when you redesign on the way, or when you were about to buy hardware you would only half use.

There are two numbers and people usually only ask about the first. There is the project cost to move, driven mostly by how much has to be redesigned rather than copied. And there is the monthly running cost afterwards, which is the one that matters for years. We model both before you commit, because a migration that comes in on budget and leaves you with a bill you did not expect has not succeeded.

For a straightforward small environment, weeks. For a mid-sized organisation with line-of-business applications and integrations, several months, delivered in waves. The assessment and planning is a meaningful share of that and it is the part worth not rushing, because the migrations that go badly are almost always the ones that started before anybody understood the dependencies.

Anything with a hard latency requirement to something physical on your site. Applications licensed in ways that make cloud hosting disproportionately expensive, which is more common than you would hope. Systems with a data residency constraint, where sovereign hosting is the better answer. And anything due for replacement in the next eighteen months, where you would be paying to move something you are about to retire.

Yes, and anyone suggesting otherwise is being optimistic. Cloud moves the work rather than removing it. There is no hardware to maintain, and there is now cost management, identity and access control, backup of cloud workloads, and security configuration. The skills change. The need does not.

We quote after scoping rather than before. Anyone pricing this work without looking at your environment is guessing, and the guess is rarely in your favour. Scoping itself is quick, and we tell you what it costs before we start it.

A first conversation takes about half an hour and costs nothing. Scoping is usually a week or two of our time depending on the size of the environment, and we agree the delivery dates with you before anything is booked in.

Yes, and it is common. We are happy to work as an extra pair of hands under your internal team, or alongside an incumbent provider on a defined piece of work. We will set out in writing where the responsibilities split, so nothing falls between us.

No. This can be delivered as a standalone piece of work for an organisation we have never worked with before, or folded into a managed agreement if you already have one with us. Plenty of clients use us for one thing and keep everything else where it is.

Our team is based in Auckland and we attend sites across the wider region. Most of this work is delivered remotely, so we support organisations throughout New Zealand, and we will say up front where being on site genuinely matters.

Named people, not a queue. You get a lead who knows your environment and stays with it, which is the difference between explaining your business once and explaining it every time you make contact.

You keep the documentation regardless, and anything registered in your name stays in your name. Whether we stay involved is your call. Some clients take it in house from there, others move it onto an ongoing agreement with us. We would rather you left cleanly than stayed because leaving was difficult.