From inventory to cutover with Azure Catalyst
What changed for Azure Migrate?
Microsoft’s overview now calls the service Azure Catalyst, formerly Azure Migrate. It brings discovery, assessment and migration into one project. The classic experience lacks the newer application and cross-workload views. The preview Catalyst agent can help interpret project data and explore planning options. Migration execution takes place in the portal.
Start with one transaction
Imagine a distributor running an ASP.NET order portal on VMware. The web tier writes orders to SQL Server. A Windows service generates a dispatch file at midnight. The business owner defines success as an order arriving once in the warehouse before the morning shift. That definition immediately puts the file share, the service account and the scheduled job inside the migration boundary. An inventory listing only the web and database servers would miss the most important acceptance test.
Choose the right discovery evidence
The appliance collects configuration and performance observations over time. The collector offers snapshot discovery for restricted environments, and an inventory import can establish an initial list. For the distributor, a spreadsheet is enough to assign owners and identify candidate servers. Sizing the SQL tier needs a representative workload window. Include the dispatch run and month-end processing. Mark any period without observations so the estimate carries an explicit assumption.
Turn assessment into a target decision
Assess readiness, sizing, estimated running cost and network dependencies. SQL Server on an Azure VM, Azure SQL Managed Instance and Azure SQL Database are possible SQL assessment targets. For the example, list the database features, jobs and external file operations the application uses. Rehearse those operations on the candidate platform. Moving the web tier to App Service could simplify host maintenance, but the background Windows service still needs an execution environment and a way to reach the share.
Build a business case the owner can challenge
Use the current estate as the baseline. Separate recurring hosting costs from migration engineering, temporary replication and the period when both environments run. For an Australian business case, express each scenario in AUD and record the Azure region, licence assumptions, utilisation window and exchange-rate date where relevant. Run a second scenario with a month-end peak and a longer coexistence period. If the preferred target changes, the team knows which assumptions to validate before committing.
Design the migration wave around the dependency
Microsoft documents different migration mechanisms for VMware, Hyper-V and physical servers. Choose the supported path for each source. In this example, place the portal, database and dispatch service in one coordinated wave even if their replication methods differ. Give the warehouse integration its own test owner. If the destination cannot receive rehearsal files, arrange a test inbox and compare its output with a known-good dispatch file.
Rehearse the point of no return
Run a rehearsal in an isolated environment. Create an order, amend its quantity, cancel a second order and trigger dispatch. Check order identifiers, totals, file contents and duplicate handling. Time the final synchronisation and record who can stop the cutover. Before production writes begin, returning traffic to the source may be straightforward. After the target accepts a new order, rollback also needs a tested way to reconcile that order. Agree on that decision with the business owner before the change window.
Close the migration with evidence
After switching traffic, reconcile the first real dispatch against the orders accepted in Azure. Check monitoring, backup recovery and on-call ownership. Retain the source for the agreed recovery period and record the conditions for decommissioning it. For this workload, the migration is complete when the warehouse can process the order and the operations team can recover it. A running VM is only one milestone.