Select Page

Data Platforms Reaching End of Life in March 2026

Author: Tom Hoblitzell | 6 min read | March 26, 2026

End of support dates can creep up on you when you’re heads-down and managing complex, multi-platform data environments. Missing these dates can result in failed audits, reduced performance, increased costs, or even data breaches. To help you keep track, we’ve created a Data Platform End of Life 2026 Calendar and will highlight the March deadlines in this post.

Data Platforms to Take Action on in March 2026

Databricks

Databricks 12.2 LTS will be fully retired without extended support available. You’ll ideally want to upgrade to a recent long-term support version, such as Databricks 13.3 or newer.

Databricks 17.2, a non-LTS release, is also reaching end-of-support. You should upgrade to either the 17.3 LTS release, or Databricks 18.x if you’d like to use a non-LTS version.

Amazon DocumentDB

Amazon DocumentDB 3.6 goes end-of-life at the end of this month, but you can opt for 3-years of paid extended support. If you don’t upgrade your DocumentDB instances by March 30, 2026, you’ll automatically get enrolled in extended support. To avoid those costs, you can do an in-place upgrade to Amazon DocumentDB 5.0.

Azure Database for PostgreSQL

Azure Database for PostgreSQL 11, 12, and 13 have reached end of life, but Azure is offering free extended support until July 31, 2026. Paid extended support will be available after that point for up to 3 years, depending on your PostgreSQL version.

You can do in-place upgrades to a later version, such as PostgreSQL 17 or 18. However, due to the number of major versions you would skip over, make sure that you test extensively to confirm no applications have broken. Alternatively, you could do smaller jumps, such as PostgreSQL 11 to 15, before going to a later version.

What’s on the Data Platform End of Life Horizon in April 2026

All set with your March end of life data platforms? Here’s what you should keep in mind for April:

  • MySQL 8.0
  • IBM Db2 11.1 LUW

See every data platform that you need to take action on in our Data Platform End of Life 2026 Calendar.

 

Frequently Asked Questions About Data Platform End-of-Support Management

What happens if I miss a data platform end-of-life deadline?

Missing an end-of-life deadline means your platform no longer receives security patches, bug fixes, or vendor support. For IT leaders, this translates directly into compliance risk, audit failures, and exposure to data breaches. Performance can also degrade over time as the platform falls out of sync with the broader data ecosystem. In regulated industries, running unsupported software can trigger findings that require costly remediation—or worse, result in penalties.

How do I plan an upgrade from a deprecated database version without disrupting operations?

Start with a thorough impact assessment: identify all applications and integrations that depend on the current platform, then map out a phased upgrade path. For platforms where multiple major versions are involved—such as moving from PostgreSQL 11 to 17—incremental upgrades and extensive testing at each stage reduce the risk of application breakage. Scheduling upgrades during low-traffic windows and maintaining rollback plans are standard practices that protect business continuity throughout the process.

Is paid extended support worth it, or should I prioritize upgrading now?

Extended support buys time, but it carries a cost—both financially and strategically. Platforms like Amazon DocumentDB and PostgreSQL offer paid extended support windows, which can make sense if your organization needs more runway to complete a complex migration. That said, extended support does not eliminate end-of-life risk; it delays it. Organizations that treat it as a long-term solution often face larger technical debt down the road. Use it as a bridge, not a destination.

How can I stay ahead of data platform end-of-life dates across a complex environment?

Managing end-of-life timelines across multiple platforms requires a centralized tracking approach. Maintaining a calendar of support deadlines for every platform in your environment—and reviewing it quarterly—prevents last-minute scrambles. Many organizations also benefit from a managed services partner who monitors these dates proactively and flags action items before they become urgent. Staying ahead of these deadlines reduces unplanned spend, protects data security, and keeps your team focused on strategic work rather than firefighting.

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.