Service Offerings
Drupal 10.x End-Of-Life FAQs
Drupal.org announced that support for all applications running Drupal 10.x will end December 9, 2026. Similarly, Acquia will also end support for Drupal 10.x on Acquia products and services on December 9, 2026.
Drupal.org announced the End of Life (EOL) for Drupal 10.x. In alignment with this timeline, Acquia will also end support for Drupal 10.x on December 9, 2026. Upgrading to Drupal 11 is essential to keep websites secure, fast, and supported with the latest features. As Drupal 10 is reaching its end-of-life, older, unsupported versions leave our platforms vulnerable to security risks and compliance issues.
After December 9, 2026, there will be no security updates, new features, bug fixes, or documentation updates for Drupal 10 from the Drupal community. You must consider Drupal 10.x an insecure and unsupported application framework after December 9, 2026.
Drupal.org and Acquia have officially announced that community and platform support for all applications running on Drupal 10 ends when Drupal 10 reaches end-of-life on Wednesday, December 9, 2026. This means any applications still running on Drupal 10 after the deadline do not receive security patches or platform support. To maintain security and compliance, all applications must upgrade to Drupal 11.
A: This schedule is driven by the new major release schedule for Drupal. For more information, refer to Drupal 10 will be supported until the release of Drupal 12 in mid-late 2026.
A: Any customer currently running an application built on Drupal 10.x is directly impacted. This also affects users who rely on Acquia products that are tied closely to the Drupal 10 lifecycle, such as Site Studio 7.x.
A: Yes. If your application is currently using Drupal 10.x, plan the upgrade to Drupal 11 ahead of the December deadline. While applications may technically function beyond December 9, 2026, every day an application remains on Drupal 10.x past this date introduces security, integrity, and compliance risks to enterprise data.
A: The deadline is December 9, 2026. Acquia does not guarantee Drupal 10.x compatibility with Acquia's products and services after this date.
Moving forward, Acquia's compatibility testing is limited exclusively to Drupal 11.x and above. Platform architecture updates can impact legacy Drupal 10.x application functionality or site availability, and upgrading to Drupal 11 is the only available remedy.
A: Acquia supports Drupal 10.x applications as part of standard Support services until December 9, 2026 (to provide diagnostic support and ensure cloud compatibility). After December 9, 2026, Acquia concludes support services for Drupal 10.x.
A: Use these verified resources to map out your technical upgrade workflows:
A: This depends entirely on your development and deployment approach. With methodical local sandbox planning, rigorous testing of custom code, and smooth continuous integration, teams can do this migration with zero downtime for live production applications.
A: No. Drupal 11 has entirely removed older database update hooks and deprecated APIs. Custom code update tools such as Upgrade Status do not work in the process and updates cannot be done to the database. Sites that run Drupal 9 cannot jump straight to 11. You must first update the application to the latest minor release of Drupal 10 (specifically Drupal 10.3 or higher) before you can successfully update to Drupal 11.
Cloud Classic infrastructure is on MySQL 5.7 and will not be upgraded to MySQL 8.0. Only Cloud Next infrastructure runs MySQL 8.0.
To upgrade applications to Drupal 11 on Cloud Classic infrastructure, you must use the MySQL 8.0 to 5.7 backport database driver. For more information, refer to MySQL 8.0 to 5.7 backport database driver for upgrading to Drupal 11.
A: Yes. Custom technical engagements are available through Acquia Professional Services for accounts that need specialized hands-on assistance to migrate complex Drupal 10 architectures to Drupal 11.
A: For general questions about the Drupal 10 end-of-life, contact your Acquia account team. For technical questions about how to upgrade your Drupal 10 application to Drupal 11, contact Acquia Support.
A: This schedule is driven by the new major release schedule for Drupal. For more information, refer to Drupal 10 will be supported until the release of Drupal 12 in mid-late 2026.
A: Any customer currently running an application built on Drupal 10.x is directly impacted. This also affects users who rely on Acquia products that are tied closely to the Drupal 10 lifecycle, such as Site Studio 7.x.
A: Yes. If your application is currently using Drupal 10.x, plan the upgrade to Drupal 11 ahead of the December deadline. While applications may technically function beyond December 9, 2026, every day an application remains on Drupal 10.x past this date introduces security, integrity, and compliance risks to enterprise data.
A: The deadline is December 9, 2026. Acquia does not guarantee Drupal 10.x compatibility with Acquia's products and services after this date.
Moving forward, Acquia's compatibility testing is limited exclusively to Drupal 11.x and above. Platform architecture updates can impact legacy Drupal 10.x application functionality or site availability, and upgrading to Drupal 11 is the only available remedy.
A: Acquia supports Drupal 10.x applications as part of standard Support services until December 9, 2026 (to provide diagnostic support and ensure cloud compatibility). After December 9, 2026, Acquia concludes support services for Drupal 10.x.
A: Use these verified resources to map out your technical upgrade workflows:
A: This depends entirely on your development and deployment approach. With methodical local sandbox planning, rigorous testing of custom code, and smooth continuous integration, teams can do this migration with zero downtime for live production applications.
A: No. Drupal 11 has entirely removed older database update hooks and deprecated APIs. Custom code update tools such as Upgrade Status do not work in the process and updates cannot be done to the database. Sites that run Drupal 9 cannot jump straight to 11. You must first update the application to the latest minor release of Drupal 10 (specifically Drupal 10.3 or higher) before you can successfully update to Drupal 11.
Cloud Classic infrastructure is on MySQL 5.7 and will not be upgraded to MySQL 8.0. Only Cloud Next infrastructure runs MySQL 8.0.
To upgrade applications to Drupal 11 on Cloud Classic infrastructure, you must use the MySQL 8.0 to 5.7 backport database driver. For more information, refer to MySQL 8.0 to 5.7 backport database driver for upgrading to Drupal 11.
A: Yes. Custom technical engagements are available through Acquia Professional Services for accounts that need specialized hands-on assistance to migrate complex Drupal 10 architectures to Drupal 11.
A: For general questions about the Drupal 10 end-of-life, contact your Acquia account team. For technical questions about how to upgrade your Drupal 10 application to Drupal 11, contact Acquia Support.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Service Offerings