A successful Drupal update protects the work people already do on your website. Before choosing a maintenance window, write down the tasks that must still work afterward: publishing an article, sending an inquiry, signing in, and completing any important integration.
Agree on the scope
Separate a routine patch update from a major-version upgrade. Record the installed versions and review the relevant release notes. Drupal’s Composer update guide describes dependency updates, database updates, and cache rebuilding for minor and patch releases. Use the upgrade documentation for a move between major versions.
Ask the person doing the work to identify the target version, affected modules, and a rollback decision. “Update everything” gives you little basis for checking whether the work succeeded.
Rehearse with a realistic copy
Test on staging with representative content and configuration. Check the backup can be restored, and record which database and file snapshots belong together. Keep staging email and payment integrations pointed at their test destinations.
- Open a public page while signed out.
- Edit and preview a page using an editor account.
- Check image uploads, downloads, and navigation.
- Exercise the forms and integrations that bring business value.
Make the deployment repeatable
Keep the reviewed dependency lock file with the release. The production deployment should reproduce the tested dependency set. Agree who can approve the deployment and who will check the site immediately afterward. For a busy publishing team, a short editorial pause can prevent content changes from complicating a rollback.
Close the loop
Record the deployed version, test results, remaining issues, and the location of the recovery instructions. A green homepage alone does not establish that the whole site works. Ask an editor to perform a normal daily task as a final check.
Our recommended handover is a short release note with evidence and a named owner for follow-up. If your team needs help planning that process, explore our Drupal support plans.