MySQL 5.7 support, now deprecated

Legacy service being withdrawn. MySQL 5.7 is out of vendor support and no longer receives general security fixes. It is not offered for new sign-ups, sales, development or new databases.

Legacy databases that still depend on MySQL 5.7 must be migrated to a database version currently supported on the service. The deadline to complete the migration is 31 December 2026; legacy access must not be treated as a permanent solution.

MySQL 5.7 reached the end of its public updates in October 2023; you can read the vendor's notice. Hostsuar's service withdrawal timeline is separate from the vendor's.

Migration plan

1. Take stock of the application, its connectors, character sets, collations, data types and incompatible queries.
2. First update the application, framework, drivers and extensions to versions that support a supported database.
3. Export the database, import it into a staging environment with the chosen supported version and fix incompatibilities without improvising changes to third-party code.
4. Test integrity, writes, searches, scheduled tasks, backups and restores. On the clone, disable emails, payments, webhooks and tasks that could duplicate production actions.
5. Schedule a change window, take a final backup, migrate and keep a time-limited rollback plan.

Check in cPanel or with support which supported database version is available on your service before preparing the target.

Required temporary controls

• Confirm the network restrictions of the legacy environment with support and use only authorised access. Do not publish a standalone phpMyAdmin installation to get around those restrictions.
• Limit network and user access to the minimum needed, use unique credentials and rotate any shared secret.
• Do not add new applications, data or features to the legacy environment.
• Keep verified external backups, rehearse restoring them and monitor access, errors and changes.
• Review which data the application needs to keep and avoid creating new, uncontrolled copies. If you need extra network restrictions, arrange them with support: the node's firewall is not managed from your account.

Contact support to confirm the source, the supported target and a migration date within the deadline. A temporary exception only reduces exposure; it does not restore support or fix MySQL 5.7 vulnerabilities.

Check the change

Check the version from the connection the application actually uses, not just from another phpMyAdmin login. After the change, review errors, recent records and scheduled tasks. If you need to go back to the source, stop writes and decide how to keep the data created on the target; changing only the credentials can lose those operations.