Skip to main content
AI & Technology

Move the Database First or Move the App with It? Lessons from Azure Catalyst at Microsoft Ignite

Follow a warehouse shipment from barcode scan to invoicing to decide whether the app, database, and scheduled jobs belong in the same migration wave.

Azure CatalystAzure MigrateCloud MigrationSQL Server
A worker scans a carton at a warehouse packing station
AI-generated illustration of a warehouse packing station.

Picture a warehouse that has just moved its SQL Server database. Staff can still scan boxes and close shipments. The following morning, Finance cannot issue invoices because the overnight shipment export is still reading from the old database. In this hypothetical example, the screen passed its test but the process broke between shipping and billing.

To decide whether the database should move first or alongside the app, start with the work people do. Trace which systems read or write the same data, then test whether the business process still works with the app and database in separate locations.

What Microsoft announced at Ignite

On November 17, 2026, Microsoft introduced Azure Catalyst at Ignite. It connects Azure Migrate with GitHub Copilot modernization capabilities for discovery, planning, migration, and modernization of apps and data. Microsoft said Azure Catalyst and the Azure Catalyst agent are generally available (GA). Expanded capabilities such as AI-powered application discovery and integrated app and database modernization in GitHub Copilot remain in preview. Microsoft Ignite announcement · Microsoft's Azure Catalyst announcement

Azure Migrate calls a group of workloads you plan to move together a wave. Wave planning and execution remain in preview. For waves created on or after November 11, 2026, Azure Migrate generates an execution plan based on the workloads, target services, and migration methods the team selects. Before starting, the team reviews the sequence, fills in missing inputs, and sets approval points. Microsoft's migration execution guide

When the database can move first

Have the application owner and database administrator review the connections and scheduled job history with the warehouse lead and Finance. Identify which systems read or write data at each step between closing a shipment and issuing an invoice. In this example, follow a single shipment ID from the warehouse screen to the export file and invoice. That gives the team a way to check whether the discovered dependencies cover overnight work.

Moving the database first is an option if rehearsal shows that the existing app and scheduled jobs can connect to the target with the right permissions, scans are still fast enough for the floor, and all records reach Finance. If the team cannot verify that they work separately, put the app, database, shipment export, and invoicing job in the same rehearsal and cutover wave. Steps can still run in sequence. For example, hold the export until the database cutover is complete and the team has verified that it can close a shipment.

Give the teams receiving the work a say before reopening

During rehearsal, have the warehouse lead confirm that staff can scan and close shipments. Ask the export owner to compare shipment IDs and record counts in the file with the source, and have Finance reconcile totals and check for duplicate invoices. Agree ahead of time on where to stop if totals differ, who has authority to decide, and when to check again.

The documented SQL Server path in wave execution uses Azure Database Migration Service in offline mode to move databases to Azure SQL Managed Instance. Other migration paths can require work outside Azure Migrate. Microsoft's guide also says pausing or cancelling a wave stops it from scheduling new work. Operations already running can continue until they reach a stopping point. Neither control undoes migration work. Rehearse returning to the original system. If the target has accepted new writes after cutover, specify how the team will suspend writes and reconcile those records before the original system takes over. Microsoft's guidance on wave pause and cancellation

Before booking cutover, pick one shipment from the test data, run it all the way through export and invoicing, and have the warehouse and Finance review the same evidence. If the team cannot trace that shipment to the invoice or agree on a way back to the original system, keep the move in rehearsal.

"Empowering Innovation,
Transforming Futures."

Contact us to make your project a reality.