We design, migrate and manage Azure, Microsoft 365 and local infrastructure. From a server refresh or VMware renewal to a cloud migration, we plan the platform, identity, connectivity and recovery together, then run the environment after the change.
We test whether serviceable equipment can run longer before you buy, then compare conventional servers, Azure Local, Nutanix and Proxmox for the systems that stay local.
Explore Infrastructure RefreshWe move applications, data and users to Azure and Microsoft 365 in planned waves, then run the environment after cutover with monitoring, access and cost under control.
Explore Cloud MigrationWe review the renewal quote against your hosts, licensed cores and hardware lifecycle, compare renewing, reducing and moving, and deliver the transition when the case holds.
Explore VMware RenewalThe licence follows physical cores, so moving virtual machines off these hosts doesn't reduce it on its own.
Migration from VMware for PPK Mining Equipment, with backup and recovery aligned to the new platform.
Azure, Microsoft 365, Entra ID, SharePoint, Exchange Online, Teams, OneDrive, Azure Virtual Desktop, Intune, Azure Backup and Microsoft Defender.
Local platforms for workloads that need predictable performance, private cloud capability or closer control.
Licence review, platform comparison and staged migration for organisations facing a renewal or ageing hosts.
Move to cloud, keep local, retire or replace, decided on latency, data size, dependencies, recovery, licensing and cost.
Recovery dependencies mapped before a migration, refresh or hybrid design is finalised.
Cost, access and monitoring planned before the move and managed after it.
Azure, Microsoft 365, identity, backup, monitoring and documentation run by our engineers after cutover.
Most infrastructure work starts with one pressure point. We look at what else is connected to it before the direction is set.
Hosts age, firmware falls behind and warranty dates close in. We check which workloads still need local hardware, what could move and whether some hardware still has useful life, before you commit to a purchase.
Best fit: Infrastructure Refresh →VMware Cloud Foundation and vSphere Foundation are licensed by physical core, so running fewer virtual machines doesn't lower the quote on its own. We count what is actually licensed and compare renewing, reducing and moving before the next term starts.
Best fit: VMware Renewal →We turn a general intention to move to the cloud into a plan: which workloads move, in what order, under which identity model and with what backup in place. Then we carry it out in waves.
Best fit: Cloud Migration →Spending drifts when resources have no owner, workloads are oversized or reserved capacity isn't planned. We right-size the environment, set owners and budgets, and review the bill with you as part of managed cloud.
Best fit: Cloud Migration →Recovery depends on identity, network paths and the order systems return in. We design protection across Microsoft 365, Azure and local workloads, then test restores so the plan is proven.
Best fit: Backup and Disaster Recovery →We map how applications depend on identity, DNS, network paths and shared data. That shows which systems can move on their own, which have to move together and what must stay available during migration and recovery.
Azure or Microsoft 365 suits workloads that gain from better access, variable capacity or managed services the application can use directly.
Local infrastructure suits low-latency work, large design files, plant and site systems, limited connectivity and steady, predictable use.
Duplicated, underused or unsupported systems are often better replaced by Microsoft 365, a SaaS service or an existing business application.
When identity, backup or network dependencies need work, they go to the front of the plan. Moving selected workloads can also shrink the next local refresh.
We agree recovery time and recovery point objectives, plan the order systems return in and prove it with restore testing.
We build the application and infrastructure inventory, covering users, sites, dependencies, utilisation, licensing and support arrangements, and check backup coverage and recovery evidence alongside production.
We set out what to keep, refresh, migrate or retire, with the cost and operating impact of each. Hardware support dates, renewal deadlines and business events set the sequence.
We define the target architecture, capacity, identity, connectivity, security and recovery, and agree migration waves, validation criteria, cutover windows and the limits of rollback.
We prepare the destination and move systems in the agreed order, checking application behaviour, access, data integrity, performance, monitoring and backup before each stage is accepted.
We document the configuration and recovery procedures, then run the environment within the agreed scope: monitoring, patching, access, vendor escalation, capacity and regular cost reviews.
Read FinOps cost signals and infrastructure decisions →We run infrastructure for our clients, so we weigh each option by what it costs to change and what it takes to run afterwards.
Migration effort, retraining, parallel running and support can outweigh a lower licence price. We include those costs in the comparison and keep existing infrastructure where it still does the job.
We keep local platforms such as Azure Local and Nutanix in the design wherever performance, site dependencies or running cost favour them, and move to the cloud what gains from it.
We moved PPK Mining Equipment from VMware to Azure Local, and took Australis Facade’s team to a hybrid model across Azure, Microsoft 365 and retained local systems.
A VMware exit can move workloads to another local platform, such as Azure Local or Nutanix, or to Azure and other cloud services. Azure VMware Solution continues to run VMware, so it changes where the platform is hosted rather than replacing it. We assess the alternatives against the applications and the commercial reason for change.
We compare the options over the same period and against the same workload demand. The model includes existing licence entitlements, hardware and support, migration, cloud consumption, connectivity, data transfer, backup and ongoing management. That brings out costs a server quote or a compute estimate alone can miss.
Current infrastructure and application records, renewal quotes, support agreements, cloud bills and backup reports are all useful. We also need to understand users, sites, performance issues and how much interruption the business can tolerate. We fill in missing technical detail during the environment review.
We agree ownership of monitoring, patching, access, backup, cost reviews and vendor escalation as part of the project. We can continue with managed infrastructure and cloud support, with responsibilities documented so the handover is clear. Support is raised and tracked in Microsoft Teams.
Both run virtual machines on local infrastructure, in hyperconverged or qualified external-storage configurations. Azure Local integrates that infrastructure with Azure management through Azure Arc, while Nutanix combines AHV, AOS and Prism for private cloud operations. We compare the supported hardware, application requirements, licensing and operating model for your environment.
Azure Local is billed through Azure per physical core. Organisations with Windows Server Datacenter licences under active Software Assurance can use Azure Hybrid Benefit to waive the host fee and Windows Server guest licensing on eligible deployments. VMware's current subscriptions are also licensed per physical core, with minimum quantities Broadcom has changed more than once, so we work from the terms on your actual quote.
Many workloads run well in Azure, but some are better kept local: large design files, latency-sensitive systems, plant and site systems, and steady workloads that would cost more as cloud consumption. We place each workload on its merits, and an Azure Local cluster can be managed from the Azure portal alongside cloud resources.
Sometimes. Like-for-like suits stable workloads with a few years left in the application. Before buying, we check Windows Server support dates, what could move to Azure or Microsoft 365, and whether the remaining workloads would sit better on a hyperconverged platform. Moving selected workloads first can also reduce what the new hardware has to carry.
Talk to us about a server refresh, VMware renewal, Azure migration or what your current environment costs to run. We'll review what you have and what needs to change.
Prefer email? contact@inlightit.com.au