Cloud Transformation

Migration to Azure in Waves

Discover with Azure Migrate, move servers, databases and file shares wave by wave, test, cut over, then operate.

The four-stage migration process from NGT's Azure offering, drawn with Microsoft's own tools. The Azure Migrate appliance discovers servers and their dependencies, the wave plan decides rehost or refactor per application, and the landing zone is ready before wave 1. Each wave is replicated, tested and cut over with rollback ready, then runs under Azure Monitor.

discoverreplicatemigrate onlinecopy, then syncrehostrefactortest each wavego liveOn premisesMicrosoft Azure1 · Assess and discoverWave 0 · landing zone2 · Implement, wave by waveLanding zone · spoke virtual network3 · Test and optimise4 · OperateServersVMware, Hyper-V, physicalDatabasesSQL Server and othersFile sharesSMB and NFSAzure Migrate:discoveryappliance, dependenciesData MigrationAssistantSSMA for other enginesCost estimatebusiness caseWave planrehost or refactor, per appAzure landing zonebuilt as codeAzure PolicyAzure Migrateserver migrationAzure DatabaseMigration ServiceAzure Storage MoverAzure VirtualMachinesrehostedAzure SQL ManagedInstanceAzure FilesAzure App Servicerefactored appsAKScontainerised appsAzure BackupPerformance testsJMeter, network testsProductionverificationapproval testingCutoverrollback readyAzure MonitorLog AnalyticsCost Management

Point at a component to light its links; select it for what it does here and the practice that makes it right on Azure.

When to use it

  • End of support for Windows Server, SQL Server or VMware
  • A data-centre contract that expires, or acquisitions to integrate
  • An estate too large to move in one weekend

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Cloud Transformation