dms-schema-conversion

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

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill dms-schema-conversion-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dms-schema-conversion
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/dms-schema-conversion
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill dms-schema-conversion-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating a database to a different engine requires translating schemas, assessing compatibility, and fixing conversion issues manually. This Skill automates the full AWS DMS Schema Conversion lifecycle, from creating migration projects to converting schemas, running assessments, and applying changes to the target database. ## Core Features & Use Cases - Project Setup Wizard: Guides you through creating migration projects, data providers, instance profiles, IAM roles, S3 buckets, and subnet groups step by step. - Schema Conversion & Assessment: Converts database schemas to a target engine and exports conversion assessment reports (PDF/CSV) to S3 with complexity statistics and Action Items. - Metadata Tree Navigation & SQL Conversion: Browse source and target metadata trees, view DDL definitions, and convert individual SQL statements (SQL Server to PostgreSQL only). - Use Case: You need to migrate a SQL Server database to Aurora PostgreSQL. The Skill sets up the migration project, imports metadata, converts all schemas, shows how many objects converted automatically, and helps you fix remaining Action Items before applying the DDL to the target. ## Quick Start Ask the assistant to convert your database schema to a new engine using AWS DMS Schema Conversion, and it will check for existing migration projects or walk you through creating one.

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 database schema to another engine with AWS DMS?

Create a DMS migration project with source and target data providers, then run start-metadata-model-conversion with selection rules scoping the objects to convert. The Skill waits for completion and exports an assessment report to S3 showing conversion results.

How do I assess database migration complexity before converting?

Run start-metadata-model-assessment with selection rules for your scope, then call export-metadata-model-assessment to generate PDF and CSV reports in S3. The reports show object counts, automatic conversion rates, and Action Items by complexity level.

Which database engines does DMS Schema Conversion support?

Supported sources include SQL Server, Oracle, MySQL, PostgreSQL, Db2 LUW, Db2 for z/OS, and Sybase. Supported targets include Aurora PostgreSQL, PostgreSQL, MySQL, Aurora MySQL, MariaDB, and Redshift.

Can I convert a single SQL statement instead of a whole schema?

Yes, but only for SQL Server to PostgreSQL or Aurora PostgreSQL projects. The Skill creates a statement-based metadata model with start-metadata-model-creation, converts it, and returns the translated SQL along with an assessment report.

Why does my DMS schema conversion fail with a connectivity error?

Connectivity failures usually mean wrong server name or port in the data provider, restrictive security group rules, or missing network routes between the DMS subnets and the database. Verify the data provider settings and security group egress rules, then retry.

Can I cancel a running DMS schema conversion?

Yes, conversions and statement creations are cancellable via cancel-metadata-model-conversion or cancel-metadata-model-creation, but all progress is lost. Imports, assessments, and exports cannot be cancelled and must run to completion.