Fast. Simple. No meetings. No delays.
Home / Blog / Australia / Upgrading an Old PHP Application in an Australian SME

Upgrading an Old PHP Application in an Australian SME

What to do when the business runs on an old PHP system built by one developer: assess risk, secure it, then modernise in stages.

Cover graphic for the article: Upgrading an Old PHP Application in an Australian SME

To upgrade an old PHP application in an SME safely, first find out what you actually have: who can access it, whether it is backed up, and which PHP version it runs. Then secure it with quick wins, and modernise in stages while it stays online. The biggest risk is rarely the code; it is that only one person understands it.

The one-developer problem

Many small businesses run on a bespoke system written years ago by a single developer: quoting, stock, scheduling, a customer portal. It works, so nobody touches it. The risks are organisational as much as technical:

  • The developer may have moved on, changed careers or become hard to reach.
  • Passwords, hosting accounts and the domain may sit in their name, not the business's.
  • There is no documentation, so a new developer starts by guessing.
  • Nobody is applying updates, so the system quietly ages.

If that sounds familiar, the first goal is not a rewrite. It is control: know where the system lives, who has the keys and whether you could rebuild it from a backup. For a general step-by-step upgrade method, read our legacy PHP modernisation playbook; this article focuses on ownership and risk in a small business.

End-of-life PHP and what it means

Each PHP release is supported for a limited time. Once a version reaches end of life, it no longer receives security fixes, so newly discovered vulnerabilities stay open. Very old versions such as PHP 5 have been unsupported for years, and even later versions eventually drop out. The current supported versions are listed on php.net, so check there instead of trusting a hosting panel label.

Out of support does not mean the application will fail tomorrow. It means risk accumulates: security exposure, hosting providers dropping old runtimes, libraries that no longer work with it, and difficulty hiring people who want to work on it. Customer or staff data in the system raises the stakes, and you should ask a qualified adviser what obligations apply to you under privacy rules, which change over time. Our PHP 7 to PHP 8 checklist covers the technical side of version jumps.

A two-week risk assessment before you upgrade an old PHP application

Before spending on changes, buy clarity. A short assessment by an independent developer should answer these questions in about two weeks, depending on size:

  1. Inventory. What does the system do, who uses it, what other systems and services does it connect to?
  2. Environment. PHP version, database version, operating system, frameworks and libraries, and which are out of support.
  3. Access. Who holds the hosting, domain, repository and database credentials? Are they in the business's name?
  4. Recovery. Do backups exist, where are they, and has anyone restored one successfully?
  5. Security. Obvious issues such as outdated dependencies, exposed admin pages, shared passwords and unvalidated input.
  6. Code health. Size, structure, tests, and which parts are most fragile or most changed.
  7. Business criticality. What would an outage cost per day, and which functions are essential?

The result should be a short, plain-language report with ranked risks, not a tool printout.

Quick wins: backups, patches, access

You can reduce most urgent risk before any modernisation project:

  • Backups. Automatic, off-server, covering both database and uploaded files, with a restore test on a separate environment.
  • Access. Move hosting, domain and code repository to accounts owned by the business. Use individual logins, strong passwords and two-factor authentication where available. Remove access for people who left.
  • Source control. If code lives only on the server, put it in a repository now.
  • Patching. Apply the updates that are safe on the current version, and move to the newest PHP version the code can run with minimal change.
  • Exposure. Restrict admin areas, turn off debug output, and review file upload and login forms.
  • Monitoring. Basic uptime and error alerts so you hear about failures before customers do.

Staged modernization plan

Replacing everything at once is expensive and risky. Break it into stages, each of which leaves the system working:

  1. Stabilise: the quick wins above, plus a staging copy where changes can be tested.
  2. Test the critical paths: add automated checks around the functions that make or lose money.
  3. Upgrade the runtime: move to a supported PHP version in steps and fix what breaks.
  4. Modernise the structure: introduce a maintained framework gradually, replacing the riskiest modules first.
  5. Retire or rebuild the rest: only when the business case is clear.

Because each stage ships on its own, the system can stay online throughout, with changes released during quiet hours and a rollback plan ready. For ongoing care after the project, see keeping a PHP or Laravel application healthy.

Budgeting and priorities

We cannot quote costs here because they depend on size, complexity and condition. What you can do is budget in layers:

  • A small fixed amount for the assessment and the safety quick wins.
  • A planned amount per stage, approved one stage at a time.
  • A recurring amount for maintenance, so you do not fall behind again.

Prioritise by risk and business value: first what could cause data loss or a security incident, next what blocks growth, and last what is merely untidy. Ask each supplier how they would split the work and what you could stop after each stage.

Documenting for the next person

Good documentation turns a one-person dependency into a manageable asset. Ask for it as a deliverable of every stage:

  • A one-page system overview and a list of integrations.
  • Setup instructions that let a new developer run the project locally.
  • A list of accounts, services and renewal dates, held in a business-owned password manager.
  • Notes on odd business rules found in the code.
  • How to deploy and how to restore from backup.

The article on documentation and handover explains what a good handover includes.

Putting it together

Regain control first, assess for two weeks, secure the obvious gaps, then modernise one stage at a time. If you would like an outside view of a bespoke system, our software development in Australia page explains how we work remotely with local businesses, and you can reach us through the contact page.

Frequently asked questions

How do I know if my PHP is out of support?

Find the exact PHP version your site runs, from your hosting panel or a developer, then compare it with the list of supported versions on php.net. If your version is not listed as receiving security fixes, it is out of support. Check regularly, since versions age out on a schedule.

What happens if the original developer is unavailable?

You can still recover. Secure the hosting, domain and code in accounts you own, take and test a backup, and ask an independent developer to assess the system and write documentation. Without the code or credentials, rebuilding gets harder, so start there.

Can the system stay online during upgrades?

Usually yes. Work on a staging copy, test critical paths, then release changes in small steps with a rollback plan, often outside busy hours. Big database or hosting changes may need a short planned window, which you can agree with staff and customers in advance.

Related articles

PHP Development USA

Scaling a PHP Application for Higher Traffic

Where PHP applications actually hit limits — database queries, sessions, caching and file storage — and the fixes in the order that pays off.

5 min read

🚀 Start Now