Prepare an existing installation for an update

Archived guide for existing Fusion Owned License installations; use the instructions for your installed build.

Match the instructions to the target release

The historical guide describes updating from a full release package rather than applying every intermediate package. Follow the target package's README for the actual supported path; the undated article cannot establish that every legacy build can upgrade directly to every other build.

A note in that guide states **PHP 7.2 with ionCube Loader 10.2**. The separate requirements article states **PHP 7.4+ with ionCube Loader 13+**. These are conflicting historical contexts without a shared build number. Preserve them as reference points, then use the exact target package's requirements instead of treating either note as universal.

Back up and apply the update

1. Back up the database, for example using phpMyAdmin.

2. Back up all site files, including custom language and template files.

3. Locate the eligible target package in the existing Customer Hub or through the provider of your licence. The article calls its action **Download Latest Version**; availability and entitlement must be checked for the actual account.

4. Extract the package locally.

5. If the admin directory was renamed, rename the package's admin directory to match the existing name before transferring it.

6. Apply the target package to a restored test copy first. For the actual update, follow the README when copying replacement files into the existing installation directory.

7. Open the site's `/installer/` URL over HTTPS, follow the upgrade screens and review the licence agreement.

8. Remove the installer directory after the update completes.

9. Hard-refresh the browser or clear its cached site assets; the historical desktop shortcut is **Ctrl+F5**.

10. Compare custom templates with the new or changed template files and merge the required changes.

Check the result

Verify admin sign-in, customer pages, service prices, ordering, mail and scheduled tasks. Keep the database and file backups until these checks pass.

Licence ownership and maintenance are separate: an Active owned licence does not itself confirm update coverage, and a Fusion PRO subscription does not renew legacy maintenance. Check the account's actual eligibility before applying a package.