An application might need a framework upgrade, dependency updates, or a move to Azure. But behind that application is often a database that needs its own modernization decisions: Is the SQL Server workload ready to move? Which Azure SQL target is the best fit? What compatibility issues need to be addressed? How should the target be sized? And ultimately, how do you move the data safely?
With the GitHub Copilot modernization agent, delivered through the Modernize CLI, we are bringing these decisions closer together.
The modernization agent already provides an agentic workflow for application assessment, modernization planning, and execution. It can analyze applications and repositories, understand dependencies, create modernization plans, and orchestrate modernization work.
Now, SQL Server migration assessment extends that experience to the database.
Start by understanding whether your SQL Server is ready to modernize
Before moving a database, you need evidence.
A SQL Server migration assessment helps answer several fundamental questions:
- Can this workload move to Azure SQL?
- What compatibility issues or migration blockers exist?
- Which Azure SQL target is appropriate?
- What configuration and capacity should the target use?
- What could that target cost?
Our SQL migration work brings together four important lenses: compatibility, assessability, sizing, and pricing. The goal is not simply to produce a list of issues. It is to turn assessment evidence into a useful modernization decision: target fit, prioritized blockers, recommended compute and storage, and estimated cost with the assumptions behind it.
This is important because compatibility alone does not answer the customer's real question.
Compatibility tells you whether you can move.
Sizing and pricing help tell you where you should land.
Bring SQL assessment into the Modernize CLI
With SQL Server migration capabilities in the Modernize CLI, you can assess the database as part of the same modernization workflow you use for your application.
Instead of switching between disconnected tools, reports, documentation, and calculators, the goal is to let the modernization agent invoke database-specific migration expertise when it recognizes that an application depends on SQL Server.
That expertise can evaluate readiness and help identify migration blockers, dependencies, target options, SKU guidance, and cost considerations. Our SQL migration skills are being designed around a skills-first model where specialized SQL expertise can be invoked by agents across developer and database experiences.
Imagine starting with a simple modernization goal:
“Assess this application and its SQL Server database for modernization to Azure.”
The application assessment can analyze code, configuration, frameworks, and dependencies. The SQL assessment can then evaluate the database workload and its suitability for Azure SQL.
The result is a more complete picture of the workload rather than two independent assessments.
From a database assessment to a modernization decision
Finding an issue is useful. Understanding what to do next is much more valuable.
For a SQL Server workload, assessment results can help organize the migration decision around three questions.
- Is the workload ready?
The assessment identifies compatibility issues and conditions that could prevent or complicate migration. That gives you a clear starting point for remediation instead of discovering incompatibilities late in the migration process.
- Where should it run?
SQL Server modernization isn't simply a cloud-versus-on-premises decision. Depending on workload requirements, the destination might be Azure SQL Database, Azure SQL Managed Instance, SQL Server on Azure Virtual Machines, or other supported SQL targets.
The SQL migration agent is designed around helping customers assess, right-size, and move workloads across Azure SQL targets rather than forcing every workload through the same migration path.
- What will the target look like and cost?
A migration recommendation becomes much more actionable when readiness is connected to sizing and pricing.
That means going beyond “this workload is compatible” and providing sufficient information to begin planning capacity, configuration, and cost.
Assessment is only the beginning
This is where an agentic approach becomes especially interesting.
The GitHub Copilot modernization agent already follows a workflow where assessment findings can become a modernization plan. The plan is reviewable and editable before execution, keeping people in control of the modernization process.
We want the database journey to follow the same principle.
For SQL Server, the journey naturally progresses from:
Assess → Recommend → Plan → Migrate → Validate
Our broader SQL migration direction includes specialized skills for readiness and blockers, target and SKU guidance, prerequisites and remediation, migration using approaches such as BACPAC or LRS where applicable, and post-migration validation.
That changes the role of assessment.
Instead of assessment being a report that someone reads and then manually translates into another tool, the output can become context for the next agentic action.
If there is a migration blocker, the agent can help explain it and identify remediation.
If the workload is ready, it can help determine the next migration step.
If a target has been selected, it can help prepare a migration plan.
And, as migration capabilities expand, that same plan can become the basis for executing and validating the move.
Modernize the application and database as one workload
This is ultimately the bigger opportunity.
Customers don't operate applications and databases as independent modernization projects. The database is a dependency of the application, and changing one frequently affects the other.
The Modernize CLI already supports application assessment across individual or multiple repositories, including aggregated reports, dependency analysis, recommendations, and modernization planning. Batch assessment can also produce an aggregated view that helps organize applications into migration strategies and waves.
Adding SQL Server migration readiness creates the foundation for looking at the application and its database together.
For example, an application modernization assessment might identify:
- application or framework changes,
- application dependencies,
- Azure service opportunities,
- SQL Server dependencies,
- database compatibility issues,
- an Azure SQL target recommendation,
- database sizing and cost considerations.
Rather than producing separate application and database projects, those findings can contribute to one modernization plan.
That is particularly important at estate scale.
An organization may have hundreds of applications and SQL Server instances. The challenge isn't simply assessing all of them. The real challenge is turning the results into decisions:
What is ready? What is blocked? What should we modernize first? Which workloads belong together? What is the expected effort and cost?
The Modernize CLI's batch-assessment capabilities already support per-repository and aggregated reports, including migration recommendations and migration-wave insights. Connecting database evidence to that model creates the potential for much richer application-and-database modernization planning.
And then, move from assessment to migration
Assessment shouldn't be the end of the journey.
Our direction for SQL migration is to connect the stages that customers today frequently perform through separate experiences:
Discover → Assess → Recommend → Plan → Provision → Migrate → Validate
The SQL migration work already describes a longer-term workflow covering registration and discovery, migration readiness, blocker analysis, right-sizing, migration planning, execution, and validation.
The important difference is that these aren't simply additional commands.
They can become skills available to an agent.
The user states their goal. The agent determines which expertise is required. The skill performs the specialized operation and returns structured evidence. The agent then uses that evidence to determine the appropriate next step, while important or consequential actions remain subject to user review and approval. SQL migration guidance explicitly follows the principle that migration actions should require confirmation rather than being performed automatically.
This gives us a model where:
AI recommends. Experts approve. Skills execute.
One modernization conversation
Consider where this can ultimately lead.
Instead of beginning a modernization project by asking which tool to open, a developer, DBA, architect, or migration engineer can start with the outcome:
“Modernize this application and its database to Azure.”
The agent can help break that goal into the work required:
- Assess the application.
- Identify its SQL Server dependency.
- Assess database migration readiness.
- Select an appropriate Azure SQL target.
- Identify blockers and required remediation.
- Build a modernization and migration plan.
- Review and approve the plan.
- Execute the application and database changes through the appropriate skills and tools.
- Validate the resulting environment.
The user remains in control, but no longer has to manually translate every finding from one tool into the next.
Modernization is becoming agentic
The GitHub Copilot modernization agent establishes the broader model: understand the existing environment, build a plan, let people review it, and then use agents and specialized capabilities to help perform the modernization.
Bringing SQL Server migration readiness into that experience takes an important step toward treating the application and database as the connected workload they really are.
Today, you can start by assessing SQL Server migration readiness.
The next step is turning those assessment results into increasingly actionable migration decisions and workflows.
Learn More
Assess SQL Server Migration Readiness with the Modernize CLI - GitHub Copilot Modernization Agent