Taking over a Drupal site built by another provider: the handover checklist

· 5 min read

End of contract, an agency changing priorities, a freelance developer who is no longer available, dissatisfaction… Switching providers on a Drupal site is common. It is also a risky moment: lost access, missing code, technical debt discovered too late, regressions on the very first update.

A successful handover is prepared before you terminate the contract, then follows a few simple steps. Here is a complete checklist for taking over a Drupal site for ongoing maintenance.

Before terminating: recover everything that belongs to you

This is the most important step, and the most often overlooked. Once the relationship has ended, getting an access or a file becomes much harder.

Access

  • The Git repository: make sure it is hosted on an account you own (GitHub, GitLab, Bitbucket), not on the provider’s personal account. Otherwise, ask for a transfer.
  • Hosting: the hosting console, SSH or SFTP access, the database.
  • The domain name and DNS: the registrar and the DNS zone must be in your name.
  • Third-party services: CDN (Cloudflare…), email delivery (SMTP, Mailjet, Brevo…), API keys, Google Search Console, analytics tools, monitoring.
  • A named Drupal administrator account, and access to account no. 1 (the super administrator).

Code and configuration

  • The complete code: composer.json and composer.lock, custom modules and themes, deployment scripts, CI configuration.
  • The patches applied to core or contrib modules, ideally declared in Composer rather than applied by hand.
  • The exported configuration (the config/sync folder), up to date with production.
  • The settings.php file, and the list of secrets (passwords, keys) to be handed over through a secure channel, never by email.

Data

  • A recent database dump.
  • The site’s files: sites/default/files, and the private files folder if there is one.
  • The current backup policy: frequency, retention, and the date of the last restore test.

Documentation

  • The architecture and environments (local, staging, production).
  • The deployment procedure.
  • Scheduled tasks (cron, external scripts) and integrations with other systems (CRM, ERP, SSO…).
  • The list of open tickets and known issues.

If your contract has no reversibility clause, now is the time to discuss it. It requires the outgoing provider to hand over everything above within a set timeframe, and it is the best insurance for a smooth handover.

Week 1: secure

Before touching the code, make sure nothing can be lost:

  1. Change the passwords and revoke the previous provider’s access (hosting, Drupal, third-party services) once the transfers are complete.
  2. Take a full backup (database + files + code) and test the restore on another environment.
  3. Check alert emails: do notifications from the host, the registrar or the SSL certificates reach you?

Week 2: rebuild the site locally

The most revealing test of a handover: can the site be rebuilt from the repository?

git clone <repository> && cd <project>
composer install
# Import the database dump, then:
drush updatedb -y
drush config:import -y
drush cache:rebuild

If this sequence works without workarounds, that is a very good sign. If it fails, you have just found what is missing: a module absent from the repository, an unversioned patch, configuration changed directly in production.

Two additional checks:

  • drush config:status on production: it lists the differences between the active configuration and the one in the repository. Many differences mean changes were made “by hand” in production.
  • Compare core and contrib modules with the official releases. A core modified directly, without a declared patch, is one of the most expensive traps: the next update will overwrite those changes.

Week 3: the handover audit

Once the site is reproducible, take stock:

Item How to check Warning sign
Drupal and PHP versions Status report (/admin/reports/status) Version out of support
Security updates drush pm:security, composer audit Pending security fixes
Contrib modules composer outdated "drupal/*" Abandoned modules, very old versions
Custom code Code review, phpcs with the Drupal standard Duplicated logic, no tests
Configuration drush config:status Large gaps with the repository
Performance Logs, cache settings, response times Caching disabled, PHP errors in a loop
Security Administrator accounts, permissions Shared accounts, development modules enabled

The outcome of this audit is a prioritised action plan: security first, then whatever blocks updates, and finally the technical debt that slows down new features.

The classic traps

In a handover, the same problems come up almost every time:

  • Core or contrib modules modified directly, without a patch: every update becomes a risk.
  • Unversioned configuration, changed in production through the UI: no way to know what the “normal” state of the site is.
  • Custom modules duplicating an existing contrib module, often less well maintained than the original.
  • Secrets in the Git repository: API keys, database passwords.
  • Administrator accounts shared between several people, with no traceability.
  • Unknown scheduled tasks, run from a server or service nobody monitors.
  • Dependence on the outgoing provider: shared hosting on their side, a licence in their name, an internal tool required for deployments.

None of these problems is serious if it is found early. They become expensive when they surface during an urgent security update.

After the handover: switching to run mode

Once the audit is done, maintenance can start on healthy foundations:

  • security updates applied quickly;
  • error and performance monitoring;
  • a documented, reproducible deployment process;
  • a regular report on the state of the site.

Conclusion

Taking over a Drupal site is not risky if you follow a precise order: recover, secure, rebuild, audit. Most difficulties come from things that were not handed over when the previous provider left. This checklist is there to make sure nothing is forgotten.

Switching providers for your Drupal site? I can help with the handover, from the initial audit to ongoing maintenance: see my services.