AWS SCT Converts Schemas. DBConvert Streams Moves the Data.
AWS Schema Conversion Tool is a free Amazon desktop tool that converts schemas and application code between engines but does not move data — that step is delegated to AWS DMS.
DBConvert Streams is an end-to-end MySQL ↔ PostgreSQL migration, validation, and CDC product.
Quick answer
Choose by job
Choose AWS Schema Conversion Tool if
- The migration is Oracle or MSSQL into AWS PostgreSQL, Aurora, or Redshift.
- You need stored-procedure and procedural-code conversion.
- You want a free assessment report before committing to a project.
- You will pair it with AWS DMS for the data move.
Choose DBConvert Streams if
- The migration is MySQL ↔ PostgreSQL.
- You want schema, data, validation, and CDC in one product without splitting tools.
- The target is self-hosted, not AWS-managed.
- You need continuous CDC after the migration.
At a glance
Side-by-side facts
Where AWS Schema Conversion Tool wins
Convert Oracle and MSSQL workloads into AWS targets for free
Analyzes and converts schemas, views, and application SQL from a wide engine matrix into RDS PostgreSQL, Aurora, or Redshift — with no license cost.
Rewrite procedural code, not just schemas
PL/SQL → PL/pgSQL conversion with manual fixup. DBConvert does not rewrite stored procedures at all.
Scope the project before committing
Assessment reports quantify object counts and conversion complexity up front — the standard first step for Oracle/MSSQL-to-AWS programs.
Where DBConvert Streams wins
Run the whole migration in one product
Schema conversion, resumable data load, validation, and CDC in one workflow — instead of splitting the job between SCT, DMS, and separate validation tooling.
Actually move the data
SCT converts schema and code only; the data move belongs to AWS DMS. DBConvert ships its own resumable migration runtime with parallel writes.
Target any MySQL or PostgreSQL, not just AWS
RDS, Aurora, self-hosted, on-prem, or another cloud. SCT is AWS-target oriented by design.
Continue with CDC after the cutover
Log-based binlog/WAL replication keeps source and target aligned after the load — no separate CDC tool to configure.
Workflow
Migrate MySQL ↔ PostgreSQL end to end without an SCT-plus-DMS toolchain
- 1Convert the schema with type mapping and overrides.
- 2Run the resumable data migration.
- 3Validate counts and schemas before cutover.
- 4Continue with log-based CDC replication.
One product instead of SCT plus DMS plus separate validation tooling.
FAQ
Frequently asked questions
Can DBConvert Streams replace AWS SCT?
For MySQL ↔ PostgreSQL schema and data migration, yes — in one product. For Oracle, MSSQL, DB2, or stored-procedure rewriting into AWS targets, no — that is SCT territory.
Does SCT move data?
No. SCT converts schema and application code and produces an assessment report. The actual data move is done by AWS DMS, which is a separate tool.
What about stored procedures, triggers, PL/SQL?
SCT converts procedural code (e.g. PL/SQL → PL/pgSQL) with manual fixup. DBConvert does not rewrite stored procedures — it focuses on schema, data, and CDC.
Is DBConvert AWS-only?
No. Targets can be any MySQL or PostgreSQL instance — RDS, Aurora, self-hosted, on-prem, or another cloud. SCT is AWS-target oriented by design.
Pricing?
SCT itself is free; AWS DMS for the data move is metered. DBConvert has a free IDE tier and paid migration and CDC runs without a separate cloud-runtime bill.
Why pair them rather than replace?
For Oracle or MSSQL migrations into AWS, SCT plus DMS is the standard path. DBConvert fits when the engines are MySQL and PostgreSQL and the team wants one product end-to-end.