62px
62px
Work on an existing website · Version updates

Hosting is phasing out an old PHP version — we update the website without downtime

An email from hosting saying “PHP 7.4 is being discontinued”, deprecated warnings in logs, plugins stopped updating. First we check compatibility on a copy and provide a list of incompatibilities, then we update and switch within an agreed window. Compatibility check €190.

Use the form below
€190
Compatibility
check
8.3
PHP version
we migrate to
2-5d
Typical update
time
0min
Downtime: we work
on a copy
Does this look like your case?

When to update the version

An update is not a reason to rebuild the site. In most cases, it is a few days of work if started before the hosting disables the old version.

Hosting sent an email

"Your site runs on PHP 7.4, support ends on such-and-such date." After shutdown, the site returns a 500 and does not open at all.

Logs are full of deprecated

The site still works, but every page shows warnings. This is the buffer time that is better spent now.

Plugins are not updating

New versions require a newer PHP or a newer CMS; old ones no longer receive security fixes.

Security requirement

A bank, payment provider, or client requires a supported version. The old one will not pass the check.

Framework is a major version behind

Laravel 8, Symfony 4, Django 2 — updating across one or two versions is harder than regular updates, but still cheaper than a rewrite.

No one to update

The developer is out of reach, but the hosting will not wait. We take over someone else's code and bring it to a working version.

How we update

Step-by-step update: first a copy, then the production site

01

Inventory

We check PHP, CMS, framework versions, the list of plugins and custom modules. We flag what is known to be incompatible and requires replacement.

02

Copy and test run

We set up a test copy on the target version. We run key scenarios: forms, payment, personal account, exports. We collect a list of errors.

03

Fixing incompatibilities

We fix our own code and replace abandoned plugins with supported alternatives. Disputed points are agreed upon — sometimes it is cheaper to drop a feature than to keep carrying it.

04

Switch and monitoring

We switch within an agreed window and keep a rollback ready. For a week we monitor logs and metrics to catch rare scenarios.

Price for the work

How much does a PHP and framework update cost

We quote after a compatibility check — before that an honest figure does not exist; too much depends on plugins and custom code.

Work
Price from
Timeline
When this is your case
Compatibility check
€190
1–2 days
you need to know the scope and risks before deciding
PHP version update
€390
2–5 days
site is live, plugins are supported, migration to 8.x is needed
CMS or framework update
€690
1–2 weeks
major version: Laravel, Symfony, Django, WordPress with a custom theme
Replacement of abandoned plugins
€290
2–4 days
some functionality depends on plugins that are no longer maintained
Migration to supported hosting
€390
2–5 days
the current hosting does not provide the required version or environment
Post-update monitoring
€49/mo
ongoing
so the next version does not come as a surprise

We work with WordPress, Bitrix, Laravel, Symfony, Django and custom PHP. If the site runs on code without source files, we will tell you during the audit, before invoicing.

What you will keep

What you get besides the updated website

Compatibility report

A list of what was blocking the update and what was done about it. Useful for the next developer.

Pre-update copy

Files and database as they were before any intervention — keep them, this is your insurance.

Current dependency list

PHP, CMS, plugin and module versions with end-of-support dates — so you can see when the next update is due.

Rollback plan

Step by step instructions on how to return to the previous version if something comes up a month later.

Honest boundary

When updating costs more than rebuilding

Updating makes sense as long as the code can be brought into order. We show both estimates before starting work:

  • No source code — the site was built long ago, there is no access to the code, only files on the hosting in a closed form. There is nothing to update — it needs to be rebuilt.
  • Engine is no longer supported — Drupal 7, old Joomla, custom code on mysql_* and PHP 5. Fixes will become more expensive, and security cannot be covered.
  • Features depend on abandoned plugins — if half of the site consists of paid plugins from ten years ago, replacing each one is comparable to reworking a section.
  • The site will need to be changed anyway — if the design and structure are outdated and a rework is planned this year, it is more reasonable to build it right away on a current stack.

In such cases we show the update cost and the cost of the new version side by side — the decision remains yours.

FAQ · Version updates

Frequent questions about updating PHP and the framework

Will the site go down during the update?
No. We do everything on a copy; the live site is switched over during an agreed window — usually a few minutes at night. A rollback is prepared in advance, so in the worst case we return to the previous version the same evening.
The hosting will disable PHP in a week — will you make it?
Usually yes: the compatibility check takes a day or two, and the update itself takes from two days. If we do not make it, most hosting providers allow temporarily restoring the old version or moving to a platform where it is still available.
Why can't you name the price right away?
Because the price depends on what is inside: two WordPress sites that look identical can differ tenfold in the amount of work. That is why first €190 for an audit — and then a fixed amount for the work.
Can you update the design at the same time?
That is a different job. Version updates are a technical task without changing the appearance. If you need a new look, see website redesign — it often makes sense to combine them.
What should be done with plugins that are no longer maintained?
Three options: replace with a supported alternative, rewrite the function with custom code, or drop it. We present all three with a price and a recommendation; the decision is yours.
What if something breaks a month after the update?
For the first 30 days we fix update-related issues free of charge. After that there is website support from €49 per month: monitoring, backups, and scheduled updates so you do not fall behind.
Do you update only PHP, or also the database and the server?
We review the entire environment: PHP version, database, web server, extensions. If the issue is with the hosting itself, we will tell you honestly that it is cheaper to migrate — that is a separate job at €390.
We have Laravel 8 — should we jump straight to 11?
We usually go through major versions, running tests at each one: this way errors are visible immediately and easier to localize. Development on this stack is described separately — Laravel development.
Contact

Send the website address — we will check compatibility

We need the website address, the current PHP version (if you know it), and the email from the hosting provider, if any. We reply within 60 minutes during business hours (GMT+3).

Compatibility check €190 — before the decision and before the invoice

Updating is cheaper while the site is still running

Send the address — we will come back with a list of incompatibilities, a timeline and a fixed price for the work.

Write on Telegram