Customize your SQL Server to Aurora PostgreSQL conversion with AWS Transform

This article explains how to review and customize transformation plans in AWS Transform before converting SQL Server databases to Aurora PostgreSQL, enabling intelligent decisions about schema mapping, data types, and deployment configuration.

• Transformation plans control database conversion order, conversion phases, SQL Server to PostgreSQL object mappings, and target cluster provisioning
• Execution waves sequence database conversions by risk, with up to five databases running in parallel per wave
• Conversion rules define type mappings (e.g., MONEY to NUMERIC), schema name mappings, function translations, and identity column strategies
• Character types default to case-insensitive CITEXT to preserve SQL Server behavior; override to VARCHAR for performance when case-sensitivity isn't needed
• Target provisioning creates new Aurora PostgreSQL clusters or connects to existing ones with specified instance classes and credentials
• Customize plans via the Review window Edit tab or plain-language job chat requests; all settings except locked extensions and identifier casing are editable

Transformation plans enable teams to standardize conversion rules once upfront, avoiding rework cycles and ensuring consistent application behavior after migration.