How to Upgrade Mautic 5 to 7 Safely

Inventory the installation and its customizations

Record how Mautic is installed and deployed. List plugins, themes, integrations, API clients, cron jobs, custom overrides, and any dependency managed outside the core application. Mautic 6 removed legacy code, and Mautic 7 moved to Symfony 7.3 and removed additional legacy components, so custom code and extensions need explicit compatibility tests.

Sources checked August 23, 2026: Mautic 6 release announcement and Mautic 7 release announcement.

Verify the Mautic 7 server requirements

Confirm the requirements for the current stable Mautic 7.x target before touching application files. Mautic’s version 7 release announcement requires PHP 8.2 or newer. Its version-specific environment announcement raises the database minimums to MySQL 8.4.0 or MariaDB 10.11.0. Compare the target host’s PHP extensions with Mautic’s published requirements before updating.

Sources checked August 23, 2026: Mautic 7 release announcement, Mautic 7 environment announcement, and Mautic requirements.

Restore-test a files-and-database backup in staging

Back up the application files and database, then prove that both can be restored. Clone production into a representative staging environment. Before cloning, disable cron jobs so the staging copy cannot repeat live campaign actions or sends; use a test mail transport if outbound behavior must be exercised.

Sources checked August 23, 2026: Mautic’s update guide and staging guide.

For non-Composer installs, use the CLI updater

Run the commands as the normal deployment user or web-server user, not as root. From the Mautic directory, use the official find, apply, and finish sequence, follow the updater’s output, then clear the cache:

php bin/console mautic:update:find
php bin/console mautic:update:apply
php bin/console mautic:update:apply --finish
php bin/console cache:clear

The command output may identify conditions that must be resolved for this installation. Stop the rehearsal, restore the staging copy if necessary, and address those conditions before repeating the procedure.

Command sequence checked August 23, 2026 against Mautic’s official update procedure.

For Composer installs, update constraints and finish migrations

Back up composer.json and composer.lock. Change Mautic package constraints to the approved 7.x target, check Marketplace and extra-package compatibility, then run Composer and inspect scaffold changes such as .htaccess. Complete the documented cache, finish, migration, and final cache sequence:

composer update --with-dependencies
bin/console cache:clear
bin/console mautic:update:apply --finish
bin/console doctrine:migration:migrate --no-interaction
bin/console cache:clear

Composer procedure checked August 23, 2026 against Mautic’s official update guide.

Verify staging, then repeat the tested process in production

Confirm the installed version. Review System Info and the error log, navigate the dashboard, and test the visual editor. Then exercise the instance-specific forms, campaigns, cron jobs, mail transport, APIs, webhooks, integrations, plugins, and themes from Step 1. When staging passes, schedule production maintenance, take a fresh rollback backup, repeat the tested procedure, and run the same checks again.

If the update fails, start with Mautic’s troubleshooting documentation and the captured command output rather than improvising changes on production.

Verification checks retrieved August 23, 2026 from Mautic’s staging guide.