Database Upgrades & End-of-Support Programs
Every engine has a clock. RDS and Cloud SQL now bill for extended support on old PostgreSQL and MySQL versions, SQL Server 2017 support ends in October 2027 and MongoDB 7.0 in August 2027. We plan, rehearse and run the upgrades on a fixed fee.

Dates that drive this work
- days Google Cloud SQL Cloud SQL for MySQL 8.0 moves to paid extended support.ics
- days Amazon RDS RDS for PostgreSQL 14 ends standard support; Extended Support charges begin.ics
- days MongoDB MongoDB 7.0 reaches end of life (Server and Atlas Dedicated).ics
- days Microsoft SQL Server 2017 extended support ends.ics
Sources: Google Cloud: Cloud SQL database version policies, MongoDB Software Lifecycle Schedules, AWS: Release calendars for Amazon RDS for PostgreSQL, Microsoft Lifecycle: SQL Server 2017
Sound familiar?
- Your AWS bill now carries RDS Extended Support charges for MySQL 8.0 or PostgreSQL 13, and PostgreSQL 14 joins them on February 28, 2027.
- You still run SQL Server 2016, which left extended support in July 2026, or SQL Server 2017, which follows on October 13, 2027.
- MongoDB 6.0 is already past end of life, 7.0 ends on August 31, 2027, and nobody has tested the drivers against 8.0.
- Cassandra 3.x or Aerospike 7.x clusters are out of support and the upgrade path cannot skip versions.
What you receive
- Inventory of versions, support dates and extended-support cost
- Upgrade path and runbook per database
- Compatibility test results
- Rehearsal timings and rollback plan
- Post-upgrade cost and performance report
What we deliver
Scope is confirmed in writing in the assessment, with anything out of scope listed too.
- 01
Estate inventory
Every instance and cluster with engine, version, edition, support date and extended-support cost, in one sheet you keep.
- 02
Upgrade path per engine
In-place, blue/green or logical replication for PostgreSQL and MySQL; rolling upgrades for MongoDB replica sets and Cassandra rings.
- 03
Application compatibility
Driver versions, deprecated features, query plan changes and extension compatibility tested before production.
- 04
Rehearsal and timings
A full rehearsal on a production-sized copy so the change window is measured, not guessed.
- 05
Cut-over with a way back
Blue/green deployments, replicas or snapshots arranged so every step can be reversed.
- 06
Cost clean-up
Extended-support charges removed, instance classes right-sized and reserved capacity reviewed after the upgrade.
Fixed scope and a fixed fee, agreed in writing.
Every engagement is scoped after a free 30-minute review. The scope and fee are confirmed in writing before work starts, and the assessment fee is credited toward the project.
Step 01
Upgrade readiness review
Fixed fee, scoped after the free review
Inventory of versions and support dates, upgrade path per database, application impact, risks and a fixed quote. Credited toward the upgrade.
Step 02
Upgrade program
Fixed fee, scoped after the free review
Scoped per database or per estate from the review, agreed in writing before work starts.
Samples and an example engagement
Templates with fictional systems and an illustrative scope, so you can judge the depth before the first call.
PostgreSQL fleet upgrade before Extended Support charges
A software company runs a few dozen Amazon RDS for PostgreSQL 13 and 14 instances. Standard support for 14 ends Feb 28, 2027 and Extended Support is billed per vCPU-hour after that.Sample deliverableSample assessment report: database upgrade readiness
The structure and depth of the written plan you receive at the end of a paid assessment, shown with fictional systems.Sample deliverableSample cut-over runbook: PostgreSQL major upgrade with blue/green
A step-by-step runbook excerpt with timings, owners, checks and the rollback path.From first call to delivery
You can stop after any step and keep everything we have written.
- 01
Free
Free 30-minute review
We look at what you run, what is urgent and whether a fixed-fee engagement fits. You get a short written summary.
- 02
1–2 weeks · credited
Readiness review
Written path, risks and a fixed quote from read-only access or exports.
- 03
Typically 2–8 weeks
Upgrade program
Rehearsed, reversible upgrades, environment by environment.
Technologies
Names are trademarks of their owners. Listing does not imply partnership.
Questions about this service
Straight answers on scope, fees and how we work. Anything else, ask us.
What does RDS Extended Support cost us?
AWS charges per vCPU-hour for each instance running a major version past its end of standard support. The charge rises in the third year. The readiness review lists the exact instances and the monthly amount from your own bill.
Can we skip versions?
Often, but not always. PostgreSQL can jump several majors with pg_upgrade or logical replication; Cassandra and MongoDB need one major at a time. The review sets the shortest supported path for each engine.
How much downtime should we expect?
Blue/green or replication-based upgrades usually need a switchover of seconds to minutes. In-place upgrades take longer. We measure it in rehearsal before production.
Is the review fee credited?
Yes. The full fee is deducted from the fixed fee of the upgrade program if you go ahead.
Start with a free 30-minute review.
Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.

