dms-schema-conversion

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

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill dms-schema-conversion-richardnroman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dms-schema-conversion
Source: https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform/tree/main/.agents/skills/dms-schema-conversion
Command: npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill dms-schema-conversion-richardnroman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating a database schema from one engine to another (for example SQL Server to PostgreSQL) requires assessing compatibility, converting DDL, fixing conversion issues, and applying changes — a complex multi-step process that this Skill orchestrates end to end through AWS DMS Schema Conversion. ## Core Features & Use Cases - Full Migration Project Lifecycle: Create migration projects with a guided setup wizard covering data providers, instance profiles, IAM roles, S3 buckets, and Secrets Manager credentials. - Schema Conversion & Assessment: Convert schemas to a target engine or run compatibility assessments, with exported PDF/CSV assessment reports delivered to S3. - Action Item Fixing & Tree Navigation: Review and fix conversion action items with targeted DDL edits, browse the metadata model tree, and convert individual SQL statements (SQL Server to PostgreSQL). - Use Case: A team migrating a SQL Server database to Aurora PostgreSQL uses this Skill to assess conversion complexity, convert all schemas, review action items, export the converted DDL as a script, and apply it to the target database. ## Quick Start Ask the assistant to convert your database schema to a target engine using AWS DMS Schema Conversion and it will check for existing migration projects or guide 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 SQL Server schema to PostgreSQL with AWS DMS?▼

Use DMS Schema Conversion by creating a migration project with source and target data providers, then running start-metadata-model-conversion with selection rules scoping the objects. The Skill guides you through setup, conversion, assessment reports, and exporting the converted DDL to S3.

How do I assess database migration complexity before converting?▼

Run start-metadata-model-assessment with selection rules for your scope, then export the assessment with export-metadata-model-assessment. DMS produces PDF and CSV reports in S3 showing conversion complexity, action items, and estimated effort per object category.

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

Yes, DMS Schema Conversion supports virtual targets, letting you review converted schemas without provisioning a live database. SQL Server sources also support offline mode using exported DDL scripts uploaded to S3 instead of a direct connection.

Which engine combinations support single SQL statement conversion?▼

Statement-level conversion via start-metadata-model-creation is only available for SQL Server to PostgreSQL or Aurora PostgreSQL migration projects. Other engine combinations support full schema conversion and assessment but not individual statement conversion.

Why does my DMS schema conversion fail with credential or connectivity errors?▼

Failures usually come from invalid Secrets Manager credentials, unreachable databases, or misconfigured S3 and IAM roles. Verify the secret values, security group rules, S3 bucket versioning, and that IAM role trust policies include the DMS service principal.