3-year cost calculator
Pre-filled for MySQL → PostgreSQL. Adjust every figure with your own numbers.
Every figure here is an illustrative estimate, not a vendor quote. Defaults are editable starting points compiled from public information; real, binding pricing comes from the vendor or an authorized distributor. See our methodology.
How this is licensed: Oracle and SQL Server license by the vCPUs of the database server VM. Oracle applies a per-core factor and counts ALL vCPUs unless the workload runs on approved hard-partitioned or Oracle-engineered hardware; SQL Server has a 4-vCPU-per-VM minimum. Set $/vCPU to your edition and core factor.
All figures are illustrative and fully editable — adjust the cost-per-vCPU and migration inputs with your own numbers. Not guaranteed vendor pricing (defaults reviewed May 2026). For a binding quote, use the request form below to reach an authorized distributor or partner.
Quick comparison: MySQL vs PostgreSQL
Common trade-offs teams weigh when staying on MySQL versus moving to PostgreSQL. These are general, commonly-reported considerations — not statements of fact about any vendor — so check them against your own contract and the vendors' current terms.
- Already in production — no migration effort or risk
- Established and already integrated in your stack
- Re-evaluating cost, support, or strategic fit
- Open source — no license fees
- No vendor lock-in
- Cost model: Free (optional support)
- Requires a migration (~15 weeks, medium effort)
- Community support by default — paid support optional
Why teams evaluate alternatives to MySQL
Reasons commonly cited by users and in public industry coverage for re-evaluating MySQL. These are general, reported considerations — not statements of fact about Oracle — and may not reflect your situation or the vendor's current terms. Verify against your own contract before deciding.
- Re-evaluating cost, support terms, or strategic fit.
The migration plan
Roughly 15 weeks for a mid-size estate, in six phases.
Tooling & automation
pgloader handles schema + data; review SQL dialect differences.
OffVendor's wizard pre-fills these scripts with your environment — inventory export, disk/schema conversion, bulk provisioning, and validation.
Frequently asked
Is migrating from MySQL to PostgreSQL worth it?
For most teams facing rising MySQL costs, yes — PostgreSQL (free (optional support)) typically lowers 3-year total cost of ownership, though the right answer depends on workload complexity and in-house skills. Use the calculator to model your own numbers.
How long does a MySQL to PostgreSQL migration take?
A typical mid-size estimate is around 15 weeks across six phases — discovery, design, pilot, waved production migration, validation, and decommission. Larger or more complex estates take longer.
What tools are used to migrate from MySQL to PostgreSQL?
pgloader handles schema + data; review SQL dialect differences.