An outdated website is one of the most common reasons sites get hacked. We update WordPress, Drupal, Laravel and other systems, their plugins and their PHP version, move sites whose support has ended to supported versions and put the server in order, keeping your content, URLs and data intact. We also work on sites built by other developers.
What the service covers
Security updates
We install security fixes for the core system, plugins and themes, testing them in a staging environment first so an update does not break the site.
PHP and server upgrades
We move to supported versions of PHP, the database and the operating system, and fix any code that no longer works on the new version.
Upgrades to newer versions
We move sites from Drupal 7, 8 or 9 to Drupal 11, upgrade old WordPress and Laravel versions and replace plugins that are no longer maintained.
Outdated custom-built sites
If a site runs on a system that has not been maintained for years or on hand-written code, we move its content to a modern content management system and keep the URLs, so the site keeps its Google rankings.
Backups and a rollback plan
Before every change we take a backup and agree how to return to the previous version if something goes wrong.
Maintenance afterwards
Once the upgrade is done, we can maintain the site so that security fixes go in on time and it does not fall behind again.
How the work is done
Assessment
We check the versions of the system, plugins, PHP and server, find known vulnerabilities and assess what can be updated straight away and what needs more work.
Plan
We prepare an upgrade plan with the order of work, the risks and the scope.
Staging environment
Every change is made first on a copy of the site, where we test forms, payments, integrations and the design.
Release
The upgraded version goes live at an agreed time, with a backup and a rollback plan.
Checks and maintenance
After release we monitor errors and performance and agree on future updates.
When a security fix is released for a system or plugin, the vulnerability it fixes becomes public knowledge too. Attackers scan automatically for sites where the fix has not yet been installed, so an unpatched site will be found however well known it is. Versions whose support has already ended are an even bigger risk, because they no longer receive security fixes at all. Drupal 7 and older PHP versions are examples.
When to upgrade and when to rebuild
In most cases an existing site can be upgraded while keeping its design, content and URLs. If a system is so old that upgrading it would take almost as much work as a new site, we will say so plainly and compare both routes by cost and risk.
For public sector institutions
We can carry out upgrades with documented changes, testing in a staging environment and handover reports, as the maintenance of public information systems requires. This is how we work on the portals we maintain for state and municipal institutions.
Frequently asked questions
Can an update break the website?
It can, if it is done directly on the live site. That is why we test every change on a copy first and only release it once everything works, with a backup and a way back.
Our website was built by another company. Can you update it?
Yes. We first get to know the code and its quirks, then propose an upgrade plan. If the code is of poor quality, we will tell you in the assessment.
How often should a website be updated?
Fixes for critical vulnerabilities should go in within a few days of release. Other updates are usually bundled into regular monthly maintenance.
Is a Drupal 7 site still safe?
Official support for Drupal 7 ended in January 2025 and it no longer receives security fixes. The site keeps working, but every new vulnerability stays open, so we recommend moving to Drupal 11.
What does the price depend on?
On how old the system is, how many plugins and how much custom code it has, whether the server needs upgrading too and how many features need testing. We give you the scope of work after the assessment.