Build With KawalSenior Drupal developer
All posts

What happens in a Drupal upgrade audit

By Kawal Kohli · · 4 min read

I don't quote a fixed price for an upgrade until I've looked inside the site. Not because I want to make it complicated, but because the inside is where the cost is. The audit is how I find it.

What I need from you

Usually a copy of the codebase and a recent database backup, or access to a staging copy. I don't need to touch your live site. If you're worried about sharing access, we can talk about how to do it safely, and I'm happy to sign an NDA.

What I look at

  1. Core version and update history. How far behind is the site, and has it been patched?
  2. Contributed modules. Which ones you use, which have versions for Drupal 10 or 11, and which are abandoned.
  3. Custom modules. What each one does, whether it's still used, and whether it needs small fixes or a rewrite.
  4. The theme. How it's built and how much of it can carry over.
  5. Content. How many content types and fields, how much content, and how clean it is.
  6. Users, roles, and permissions.
  7. URLs and redirects, so search rankings hold after launch.
  8. Hosting. PHP version, database version, and how deploys work today.

What you get

A written report in plain language. It lists what I found, the recommended upgrade path, the risks, and anything I'd suggest dropping. Then a fixed quote and a timeline based on that report.

The report is useful even if you don't hire me. It tells you what you have and what it will take, which is exactly what you need to compare quotes or plan a budget.

What I don't do in an audit

I don't start fixing things, and I don't change anything on your live site. The audit is for looking and writing things down. The work starts after you've seen the quote and said yes.

The first step is a 30 minute call. Bring the URL, and I'll tell you what the audit will likely turn up.

Want to know what your upgrade looks like? 30 minutes, and you'll know.

Book a discovery call