PHP upgrade service

Upgrade your legacy PHP application without an unnecessary rewrite

I upgrade custom PHP applications from PHP 5.6, PHP 7.x and older environments to a currently supported PHP version — including applications without a framework.

Get your PHP application assessed post@stefanpilz.ltd

Your PHP version, hosting setup and any error message are usually enough to start the conversation.

I’m Stefan Pilz, a PHP and Shopware developer based in Paphos, Cyprus. I help companies and agencies take over, upgrade and maintain existing PHP software remotely across Europe and worldwide.

  • Building PHP websites since 2004
  • Work directly with the developer
  • Custom applications welcome
  • Framework optional
  1. PHP 5.6 / 7.x
  2. Assess
  3. Adapt
  4. Test
  5. PHP 8.x

What brings you here?

The site broke after a PHP change

A blank page, HTTP 500, a fatal error or a broken login needs a diagnosis. Send me the PHP error and describe the affected workflow.

The original developer has left

I can take over an unfamiliar codebase, including custom software built over many years. Missing documentation, old libraries and Composer conflicts are reasons to investigate the application carefully.

You need to add features

A useful application should not have to stand still because its runtime or framework is outdated. Restore a workable technical foundation, then plan the next improvements.

No framework required. No forced rewrite.

An older application may consist of PHP files, includes, custom database access, forms, sessions, scheduled jobs and business rules. That is still software worth assessing on its own terms.

It does not need a move to Symfony or Laravel before a PHP upgrade can begin. Procedural PHP and custom applications are welcome. Modernizing PHP without a framework starts with what the business already uses.

Already using a framework?

Symfony

For an older Symfony application, I assess PHP, components and package dependencies together. Symfony is part of my work and a possible destination, not a requirement for every modernization.

Laravel and CakePHP

Updating the existing framework may be the practical route. The version and package ecosystem determine the options; switching to Symfony is not the default answer.

Zend Framework, Yii, Slim and others

These applications need an assessment of the actual code and dependencies before an upgrade path can be agreed. Plan a framework upgrade without assuming every old version has a direct route forward.

Upgrade or rebuild?

A targeted upgrade

Keep useful business logic and change what the runtime and dependencies require. The value of established workflows can outweigh the appeal of a cleaner implementation from scratch.

A complete rewrite

A rebuild can make sense when the application no longer fits the requirements. It also increases the surface to test and may introduce more cost and migration risk. I weigh maintainability, business needs and risk before recommending it.

In practice: PHP 5.6 → PHP 8.4, keeping the application

A custom website developed many years ago used numerous individual PHP files and no framework. There was no Symfony or Laravel project to upgrade. I adapted the existing code to PHP 8.4.

  • The existing application was retained and runs on PHP 8.4.
  • No complete rewrite was needed.
  • The codebase can now support further development.

Read the PHP 5.6 to PHP 8.4 case study.

How the work proceeds

  1. Initial assessment: establish the current version, the problem and the hosting constraints.
  2. Code and system review: understand the application and agree a scope.
  3. Compatibility work: adapt code affected by PHP changes.
  4. Dependencies: update or replace relevant libraries, extensions and framework components.
  5. Testing: agree the important workflows and check them in the target environment.
  6. Go-live: prepare backups, a change window and a rollback plan, then check logs and key functions after switching.
  7. Optional development: prioritize new features separately once the upgrade is complete.

What can be included in the assessment?

The checks depend on the application and agreed scope. Not every project needs every item below.

Code and runtime

Removed functions, breaking changes, Composer packages, manually installed libraries, PHP extensions, filesystem operations and error handling.

Data and user workflows

MySQL/MariaDB access, sessions, cookies, authentication, forms and email delivery. The test plan follows the workflows people actually use.

Operations and integrations

Scheduled jobs, APIs, external services, logging and web-server or hosting configuration. Command-line jobs and web requests may use different PHP settings.

Keep developing the software you already have

The next step can be new features, APIs, ERP or CRM integrations, automation, imports and exports, administration tools, performance improvements, security work or a refreshed frontend. Shopware integrations and other e-commerce features can build on the same application.

For broader work on architecture, see legacy PHP modernization. Explore API integration, custom software development, Shopware services or the PHP freelancer overview.

FAQ

Can a PHP 5.6 application still be upgraded to PHP 8?

Yes, it can be possible. The code, libraries and hosting determine the work. A direct production switch may be feasible even though the compatibility work must account for changes across several PHP releases.

Does legacy PHP software need a complete rewrite?

No. I first assess what needs to change. A rebuild is an option to evaluate, not an assumption.

Can you take over code written by another developer?

Yes. I work through unfamiliar code and identify the workflows, access and knowledge needed to maintain it.

What if there is no framework?

That does not prevent an upgrade. Standalone PHP files, includes and custom database code do not automatically require a move to Symfony or Laravel.

Must Laravel or CakePHP applications move to Symfony?

No. Updating the existing framework may be the better choice. Symfony migration is an option, not a prerequisite.

What do you need for an initial assessment?

The current and available target PHP versions, hosting details, a short application description and any relevant error. If you do not know the versions, start by describing what is happening.

Can you develop the application after the upgrade?

Yes. Features, integrations and improvements can follow as a separate scope of work.

Is very old custom PHP code still worth assessing?

Yes. The PHP 5.6 to 8.4 case study is one example. It is not a guarantee for every application: unavailable dependencies or components can change the scope.

Can we start with just the PHP upgrade?

Yes. The first engagement can focus on running the application on a supported PHP version. Broader modernization can be decided afterwards.

Tell me what your PHP application needs

Your PHP version, hosting setup and any error message are usually enough to start the conversation.

If available, include the target PHP version and a short description of the application. You do not need a complete specification to get in touch.

Get your PHP application assessedE-Mail