How to upgrade a Drupal site without losing content

Updating a Drupal site is a mandatory process that ensures security, performance, and compatibility with new modules. However, site owners are often afraid of this stage: "Will the content disappear?", "What if the layout breaks?", "Will the site stop working?" - these questions arise for a reason. In this article, we will analyze step by step how to update Drupal in such a way that all the content, structure, and working functions of the site are preserved. This is an instruction for owners who want to understand how everything works, even if the update is performed by the technical team.

Why you need to update Drupal

Drupal, like any software environment, is constantly being improved. Core and module updates address security issues, increase speed, eliminate bugs, and add new features. Ignoring updates leads to vulnerabilities, incompatibility with modern services, and scaling difficulties. If your site stores personal data, has a feedback form, or an online store, updating is critically important.

Content in Drupal is stored in the database, and the structure is stored in configuration files. If the database is backed up and the configurations are saved, no page, product, article, or form will disappear. Problems only arise when an update is made “live,” without preparation. That is why it is important to work with a copy of the site, use a version control system, and test the update on a staging server.

How to prepare for a Drupal upgrade

The first step is to create a full backup: database, files, modules, themes. The second is to check the compatibility of modules and themes with the new version of Drupal. The third is to update the site on a copy (staging), test the operation of all functions: forms, filters, search, admin. Only after that are the changes transferred to the "live" site. In case of a complex update, it is worth using migration tools: Drush, Composer, automated scripts.

What can go wrong and how to avoid it

The most common problems are: module incompatibility, dependency conflicts, API changes, cache failure, and missing styles due to theme changes. To avoid this, you should:

• use only verified modules from the official Drupal.org catalog;

• do not change the kernel manually;

• update Composer projects according to official documentation;

• monitor errors in logs;

• have technical support that monitors the process.

The content will not disappear if it was saved and the migration goes through official Drupal tools.

How often should Drupal be updated?

It is recommended to install security updates — immediately after release. Minor updates — once every few months. Major updates — depending on the support for the current version (usually once every 2–3 years). Important: if you have missed several versions, updating requires a phased approach. Therefore, it is better not to delay — this reduces risks and reduces the cost of updates in the future.

GL.ua — a team that updates Drupal without stress

If you need a Drupal site update —  GL.ua will help . The company  has been working exclusively on Drupal since 2008 , so it knows all the nuances of the process. They update projects of any complexity: with a large database, unique modules, complex logic. You get a site that works stably, without losing content, with improved security and speed.

The company also provides ongoing technical support : monitoring, auditing, optimization, development of new features. With GL.ua, your site remains modern, secure, and ready for growth.