Service pillar
Drupal developer for upgrades, maintenance and custom modules
Plan Drupal workSend me the site details.
Include the Drupal core version, the list of contributed and custom modules, the hosting setup and what has to keep working during the upgrade.
- UpgradesDrupal 7 and 10 to 11
- Maintenancecore and module updates
- Modulescustom code, Composer, Drush
- HeadlessJSON:API front ends
Councils, universities and charities
Drupal is common where one organisation runs many sites, many editors and strict permissions: local authorities, universities and larger charities. Public sector sites in the UK fall under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, and in Ireland the obligations come from EU Directive 2016/2102. I run accessibility checks as part of every upgrade.
What I work on
Security and minor updates with a tested Composer workflow, migrations from Drupal 7 to a fresh Drupal 11 install and from Drupal 10 to 11, custom modules and themes, Drush-based deployments, caching and database tuning, integrations with CRMs and single sign-on, and headless front ends that read content through JSON:API. Drupal 12 is scheduled for the week of 7 December 2026, so new modules are written to keep that upgrade cheap.
What I avoid
I do not push a rebuild or a move to WordPress when Drupal fits the organisation. Multi-site estates, granular editorial roles and multilingual content are things Drupal does well. A migration between Drupal and WordPress, in either direction, is on the table only when the site has outgrown its platform or the team cannot maintain it.
How does a Drupal 7 to Drupal 11 migration work?
A Drupal 7 site cannot be upgraded in place. I build a fresh Drupal 11 install and bring content, users, files and taxonomy across with the Migrate and Migrate Drupal modules in core, rerunning drush migrate:import on staging until the record counts match the old database. Views I rebuild by hand, field collections usually become Paragraphs, and the PHPTemplate theme is replaced by a new Twig theme. Migrate Drupal is deprecated and is removed in Drupal 12.0 with no contributed replacement, so I land Drupal 7 sites on Drupal 11 and upgrade from there. Every old path gets a redirect through the Redirect module, which matters on council sites whose URLs are printed in letters and PDFs. The final import runs after a short editorial freeze, and the old site stays online read-only while both run in parallel for an agreed period.
What does a Drupal upgrade audit check?
Before estimating a 10 to 11 upgrade I install Upgrade Status with Composer on a copy of the site. It runs PHPStan over custom and contributed code, building on drupal-check, and lists deprecated API calls and contributed projects still without a Drupal 11 release. Mechanical fixes go through Drupal Rector (palantirnet/drupal-rector), and I review every rewritten line. The site must already run Drupal 10.3.0 or later, because Drupal 11 removed the update functions from older releases, and the server needs PHP 8.3 or newer. One contributed module without a Drupal 11 release is enough to stop Composer resolving the whole upgrade. If the module only needs its version constraint changed, the Drupal Lenient Composer plugin lets it install with a patch; if its code breaks, I patch or replace it. composer update --dry-run shows which case applies before anything changes. A council gets the result as a per-module estimate it can attach to a procurement request.
What does monthly Drupal maintenance include?
Drupal core security releases come out on one Wednesday a month, usually the third, and contributed projects can get one on any Wednesday, between 16:00 and 22:00 UTC. In the UK and Ireland that is late afternoon or evening, so I read the advisory that evening and have the update on staging the next morning. The order does not change: composer update for the affected packages, drush updatedb, drush config:export, a pass through the pages editors use most, a database and files backup, then deployment to production. New core minor versions take the same route a few weeks later, after the first patch release. The export step is there because an update hook can change active configuration, and if that change never reaches the sync directory, the next deployment that runs drush config:import reverts it. Councils with a change advisory board get each deployment written up in the format the board already uses.
Frequently asked questions
Do I need a Drupal agency or a freelance Drupal developer?
For maintenance, upgrades and module work on one site or a small estate, a senior freelancer is usually enough and cheaper to coordinate. An agency makes sense when you need design, content and development teams working in parallel. I tell you which one you need after reading the codebase.
What happens to our Drupal 7 site now that support has ended?
Drupal 7 stopped receiving official security advisories on 5 January 2025, and external scans flag it as insecure. The site keeps running, but every new vulnerability stays open. The route forward is a content and configuration migration to Drupal 11, or to WordPress if the site no longer needs Drupal.
How long does a Drupal 10 to 11 upgrade take?
It depends on how many contributed modules have Drupal 11 releases and how much custom code uses deprecated APIs. I start with an automated deprecation scan and a module audit, then give you an estimate per module. Drupal 10 reaches end of life on 9 December 2026.
Can you migrate from Drupal to WordPress?
Yes, and from WordPress to Drupal too. I recommend it only when the platform no longer fits: a small brochure site on Drupal is a common case for WordPress. Content, users, redirects and media move with scripted migrations so the old URLs keep working.
Do you build headless Drupal sites?
Yes. Drupal core ships JSON:API, which works well as a content back end for a separate front end. I check first whether headless pays off, because it adds a second application to host and maintain.
Explore other WordPress services and knowledge base
Strengthen your business with professional technical support in key areas of the WordPress ecosystem.
WCAG 2.2, BFSG, EAA conformance report and remediation backlog.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Custom WordPress engineering and architecture.
Clearer structure, messaging, and conversion flow.
Core Web Vitals, caching, and faster delivery.
NIS2 and DORA scope mapping, supplier register, incident runbook.
Related categories
Supporting articles

Germany's Barrierefreiheitsstärkungsgesetz applied from 28 June 2025. It transposes EAA Directive 2019/882 into national law. I unpack how it affects WooCommerce stores in DE and the four plugin failure patterns I see in audits.

WCAG 2.2 was first published as a W3C Recommendation on 2023-10-05; the current published version on www.w3.org/TR/WCAG22/ is dated 2024-12-12. The EU Accessibility Act (Directive 2019/882) applies from 2025-06-28. Germany's Barrierefreiheitsstärkungsgesetz transposes it into federal law on the same date. This article is the implementation map for a WordPress site in 2026.

BFSG and the EU Accessibility Act require a published accessibility statement with a working complaint mechanism, not just a compliant front end. This is a copy-ready template structure mapped to EN 301 549 clauses and WordPress deliverables.
Related services
Senior Drupal developer: security updates, Drupal 7 and 10 upgrades to 11, custom modules, headless JSON:API builds and accessibility work for public bodies.
Send me the site details.
Include the Drupal core version, the list of contributed and custom modules, the hosting setup and what has to keep working during the upgrade.
Plan Drupal work