This partner may have Drupal expertise and may have contributed to Drupal, but is not a Drupal Certified Partner. Drupal Certified Partners represent the top 5% of contributors to Drupal, and are the experts who contribute the most to Drupal itself. Click here to see a list of Certified partners.
Services
3rd party Integration, Accessibility, Cloud hosting, Consulting, Data migration, Deployment, Development, E-commerce, Migration, Multilingual websites, Security reviews, SEO, Site Audits, Support, Theming, Upgrades, VPS hosting
Sectors
Beauty and Fashion, E-Commerce, Education, Media, Non-profit, Technology
Locations served
Poland, United Kingdom
Office locations
United Kingdom
Headquarters
Cambridge UK
Organization type
Drupal service provider

Meet Steady Drupal

I'm Luke, and Steady Drupal is me — one developer who's been working with Drupal since 2007.

I build Drupal sites, and I move old ones onto Drupal 11. Those turn out to be the same job — a migration is a build with someone's existing content and history attached, which is the part most people underestimate. After either, I can keep the site maintained. Everything at a fixed price, quoted before I start.

My day job is at the University of Cambridge, where I'm a senior developer on a platform hosting more than 700 university websites — including the migration of over 500 legacy Drupal 7 sites to Drupal 11. When I say I've seen your migration problem before, I mean I've probably seen it several hundred times.

Most of my clients are charities, schools and small organisations still running Drupal 7 or 9. They tend to have been quoted something enormous by an agency, or nothing at all by anyone. The sites aren't complicated; they just need someone who's done it before and won't disappear halfway.

If you're stuck on an old version and want a straight answer about what it would take, get in touch.

Learn more and get started today

Drupal Contributions

Contributed a fix to the Content Activities History module resolving memory exhaustion during purge operations (#3601300). The module's purge service loaded every matching entity into memory before deletion, causing fatal OOM errors on sites with large activity tables — and its batch operations completed in a single non-iterative step, so cron-driven auto-purge failed silently on every run.

The patch refactors the purge service to delete in chunks via the database connection, adds a public deleteChunk() method so callers can iterate without re-implementing query building, and rewrites the three batch methods to iterate properly with accurate progress reporting. Verified against a production-derived dataset of 47,278 rows: peak memory dropped from a fatal 1GB OOM to around 16MB, with all rows deleted successfully. Reviewed and tested by the community.

Professional Drupal work

Senior developer at the University of Cambridge on a platform hosting more than 700 university websites, including the migration of over 500 legacy Drupal 7 sites to Drupal 11.
Active Drupal.org member since 2007.