Upgrading MySQL Binary or Package-based Installations on Unix/Linux mysql -u root -p --force < data-for-upgrade.sql It is not recommended to load a dump file when GTIDs are enabled on the server ( gtid_mode=ON ), if your dump file includes system tables.  mysqldump issues DML instructions for the system tables which use the non-transactional MyISAM storage engine, and this combination is not permitted when GTIDs are enabled. Also be aware that loading a dump file from a server with GTIDs enabled, into another server with GTIDs enabled, causes different transaction identifiers to be generated. mysqladmin -u root -p shutdown mysqld_safe --user=mysql --datadir= /path/to/8.0-datadir  --upgrade=FORCE & Upon restart with  --upgrade=FORCE , the server makes any changes required in the  mysql  system schema between MySQL 5.7 and MySQL 8.0, so that you can take advantage of new privileges or capabilities. It also brings the Performance Schema,  INFORMATION_SCHEMA , and  sys  schema up to date for MySQL 8.0, and examines all user schemas for incompatibilities with the current version of MySQL. mysql_upgrade -u root -p Then shut down and restart the MySQL server to ensure that any changes made to the system tables take effect. For example: mysqladmin -u root -p shutdown mysqld_safe --user=mysql --datadir= /path/to/8.0-datadir  & The upgrade process does not upgrade the contents of the time zone tables. For upgrade instructions, see Section 5.1.15, “MySQL Server Time Zone Support” . If the upgrade process uses  mysql_upgrade  (that is, prior to MySQL 8.0.16), the process does not upgrade the contents of the help tables, either. For upgrade instructions in that case, see Section 5.1.17, “Server-Side Help Support” . Loading a dump file that contains a MySQL 5.7  mysql  schema re-creates two tables that are no longer used:  event  and  proc . (The corresponding MySQL 8.0 tables are  events  and  routines , both of which are data dictionary tables and are protected.) After you are satisfied that the upgrade was successful, you can remove the  event  and  proc  tables by executing these SQL statements: DROP TABLE mysql.event; DROP TABLE mysql.proc; 290 Note Note Note 8. Load the previously created dump file into the new MySQL server. For example: 9. Perform any remaining upgrade operations: •In MySQL 8.0.16 and higher, shut down the server, then restart it with the  --upgrade=FORCE  option to perform the remaining upgrade tasks: •Prior to MySQL 8.0.16, execute  mysql_upgrade  to perform the remaining upgrade tasks: