The short answer
LDelight migrates New Zealand businesses to AWS, including the Auckland region that opened in September 2025. We help you decide what should move to Auckland, what can stay in Sydney and what should come out of your server room, check each service is available in the newer region before designing around it, and build in the operability and security requirements of NZ regulators.
Key takeaways
-
Auckland, Sydney or both — decided per workload, not by default
-
Service availability in the Auckland region checked before the design is fixed
-
Repatriation from Sydney treated as a migration in its own right
-
Change windows in your evening fall within our working day
A new region changes old decisions
Until recently, a New Zealand business on AWS ran in Sydney because there was nowhere closer. The Auckland region, opened in September 2025, changes that. It is an opt-in region with three availability zones, and like any new region it is still gaining services. For some workloads — those where customers, contracts or public-sector buyers expect data to stay in New Zealand, or where latency matters — it is the obvious target. For others, Sydney's fuller catalogue and maturity remain the better home.
We make that call per workload. Before any design is fixed, we check each AWS service you plan to rely on against what Auckland offers today, and document the gaps. Designing around a service that is not yet available in the region is the most common way for a migration to stall.
Repatriating from Sydney
Moving an existing AWS estate from Sydney to Auckland sounds simple because both are AWS. In practice it is a migration: data has to be copied and kept in sync, network paths and DNS change, endpoints and integrations are reconfigured, and the cutover needs a rollback plan. Cross-region data transfer is charged, so the parallel period should be as short as is safe. We plan repatriation in waves, starting with the systems that gain most from being in New Zealand.
Out of the server room
Many New Zealand organisations still run core systems on premises or in a local data centre. For those, the choice of region matters less than the route: rehosting quickly to exit a facility, replatforming databases onto managed services, or rebuilding where the application justifies it. We sequence the work so hardware refreshes and facility contracts end on time, and so each wave is small enough to roll back.
Working across the gap
We barely overlap New Zealand working hours, so delivery is asynchronous by design: written hand-offs, a decision log, and a weekly late-afternoon review in your time. Our working day covers your evening and night, which is where most New Zealand change windows sit, so cutovers and rehearsals are carried out by a team that is at work rather than on call.
Every engagement starts with fixed-fee discovery: an inventory of what you run, dependencies between systems, a placement recommendation for each workload across Auckland and Sydney, and a costed wave plan. The discovery document is yours whether or not we carry out the migration.
Page reviewed Nov 14, 2026. Region and regulatory facts for New Zealand checked Nov 14, 2026. Rules change — confirm current obligations with your adviser.