skills.rest
aws
awsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dms-schema-conversion

Converts database schemas between heterogeneous engines using AWS DMS Schema Conversion.

2.5k|282|Updated Apr 23, 2026
Search Tags:#SQL Server#ddl#postgreSQL#assessment report#schema conversion#Database migration#aws dms
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill dms-schema-conversion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dms-schema-conversion
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/migration-and-modernization-skills/dms-schema-conversion
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill dms-schema-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating a database schema from one engine to another (e.g., SQL Server to PostgreSQL) requires assessing compatibility, converting DDL, fixing conversion issues, and applying changes — a complex, error-prone process. This Skill guides an AI agent through the entire AWS DMS Schema Conversion lifecycle, from project setup to applying converted schemas on the target database.

Core Features & Use Cases

  • Full Migration Project Setup: A step-by-step wizard creates migration projects, data providers, instance profiles, subnet groups, S3 buckets, and least-privilege IAM roles.
  • Schema Conversion & Assessment: Converts schemas to a target engine, runs compatibility assessments, and exports PDF/CSV assessment reports to S3.
  • Action Item Fixing: Reviews conversion issues from assessment reports and applies targeted fixes to only the affected code, marking generated SQL for verification.
  • Metadata Tree Navigation & SQL Conversion: Browses source/target metadata trees, compares source and target DDL, and converts individual SQL statements (SQL Server to PostgreSQL).
  • Use Case: A team migrating a SQL Server database to Aurora PostgreSQL uses this Skill to create a DMS migration project, assess conversion complexity, convert the schema, fix action items, and apply the converted DDL to the target database.

Quick Start

Ask the agent to convert your database schema to a new engine using AWS DMS Schema Conversion, for example: convert my SQL Server database schema to PostgreSQL and show me the compatibility assessment report.

Frequently Asked Questions about dms-schema-conversion

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

FAQPage Schema
How do I convert a SQL Server schema to PostgreSQL with AWS DMS?▼

Use AWS DMS Schema Conversion to create a migration project with source and target data providers, then run a metadata model conversion with selection rules scoping the objects. The Skill also exports a conversion assessment report to S3 and can apply the converted DDL to the target database.

How do I assess database migration complexity before converting?▼

Run a metadata model assessment with start-metadata-model-assessment scoped by selection rules, then export the assessment report to S3. The report shows conversion complexity, action items by severity, and estimated effort without converting any objects.

Can DMS Schema Conversion work without a live source database?▼

Yes, for SQL Server sources you can use offline mode, where DMS reads exported DDL scripts from an S3 bucket instead of connecting to the database. Scripts must be one CREATE statement per .sql file with a USE statement, and the data provider DatabaseName must match the DDL content.

Which database engines does DMS Schema Conversion support?▼

Supported sources include SQL Server, Oracle, MySQL, PostgreSQL, Db2, Db2 for z/OS, and Sybase. Supported targets include Aurora PostgreSQL, PostgreSQL, MySQL, Aurora MySQL, Redshift, and Db2. Single-statement conversion is limited to SQL Server to PostgreSQL.

Why does DMS Schema Conversion import fail with an unexpected application error?▼

For offline sources, this usually means the data provider DatabaseName does not match the database name in the DDL scripts' USE statements. Check the DDL processing statistics CSV in the project's S3 bucket for failed files, correct the DatabaseName, and retry the import.

How do I fix action items from a DMS conversion assessment report?▼

Verify the object already has converted target DDL, export the target as a SQL script, then fix only the lines flagged by each action item while leaving rule-based conversion output untouched. Generated SQL is wrapped in GenAI-generated comment markers and each fix requires customer confirmation.

Related Skills

Explore More Software Engineering Skills→
datasurfacedatasurface

Create a DataSurface Yellow Kubernetes Credential

Create Kubernetes secrets for DataSurface Yellow credentials with kubectl.

Official
Advanced
claude-office-skillsclaude-office-skills
368

Database Sync

Automate database synchronization, replication, and migration between heterogeneous systems.

Official
Advanced
mreferremreferre

setting-up-cloudtrail-multi-region

Configure multi-region AWS CloudTrail trails with S3 and CloudWatch Logs delivery.

Community
Advanced
Percona-LabPercona-Lab
1

oracle-to-percona

Map Oracle schemas and PL/SQL to Percona Server for MySQL.

Official
Advanced