sqlclient-migration

Name: sqlclient-migration
Availability: InStock
Author: Microsoft

Automates .NET project migration from System.Data.SqlClient to Microsoft.Data.SqlClient.

19|2|Updated May 13, 2026

Search Tags:#migration #data access #upgrade #.NET #SQL Client

Ready to run

npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill sqlclient-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sqlclient-migration
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/sqlclient-migration
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill sqlclient-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires upgrade-dotnet, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of upgrading .NET projects from System.Data.SqlClient to Microsoft.Data.SqlClient, simplifying the migration process and ensuring compatibility.

Core Features & Use Cases

Automated Assessment: Scans the solution to identify usage of System.Data.SqlClient and potential issues.
Migrating Code and Packages: Applies namespace changes and package updates to the codebase.
Connection String Analysis: Reviews and adjusts connection strings for the new Microsoft.Data.SqlClient library.
Validation: Ensures the solution builds without errors and runs correctly with the new library.

Quick Start

Run the sqlclient-migration skill to automatically upgrade your project to use Microsoft.Data.SqlClient.

Frequently Asked Questions about sqlclient-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate a .NET project from System.Data.SqlClient to Microsoft.Data.SqlClient?▼

To migrate from System.Data.SqlClient to Microsoft.Data.SqlClient, run the sqlclient-migration Skill to automate assessment, apply namespace changes, update packages, adjust connection strings, and validate the build.

Why upgrade .NET data access to Microsoft.Data.SqlClient?▼

Upgrading .NET data access to Microsoft.Data.SqlClient enhances SQL Server compatibility and ensures long-term support, replacing the legacy System.Data.SqlClient library which is no longer receiving new feature updates.

Does the migration process adjust SQL connection strings automatically?▼

Yes, the migration process includes connection string analysis to automatically review and adjust configurations for compatibility with the new Microsoft.Data.SqlClient library in your .NET projects.

What steps are required to move System.Data.SqlClient code to the new library?▼

Moving System.Data.SqlClient code requires assessment, planning, execution, and validation phases to resolve namespace changes, update packages, and ensure the .NET solution builds and runs correctly.

Can I use this migration approach for any .NET application using SQL Server?▼

Yes, you can use this approach for .NET applications using SQL Server, provided you have the upgrade-dotnet dependency available to support the underlying project upgrade and package migration processes.

What happens if the .NET solution build fails after the SqlClient migration?▼

If the .NET solution build fails after the SqlClient migration, the Skill's validation phase identifies remaining namespace or package issues from the System.Data.SqlClient transition requiring manual resolution.