local by flywheel stuck on starting local machine

However, it may also cause memory and timeout errors when trying to export your data. Depending on the specific configuration of your server and the size of your database, the process of exporting your contents to a SQL file may fail because of memory or timeout errors.Īlternatively, if you do not have access to phpMyAdmin you can try the WordPress plugin Adminer, which provides the same functionality as phpMyAdmin. If you have access to your database through phpMyAdmin, just try to export the SQL data following the steps explained in this article about nice phpMyAdmin tutorial to export your data.

To avoid this, I always recommend to go for the database directly, and export a SQL file. However, this may fail or not export/import all of the contents you have defined, but only a subset. To do this, you could use the Import/Export native function that WordPress has. The first step to start a migration of your WordPress site is to move the contents from your current host to a new server.

Exporting/Importing your WordPress Database However, there are some steps that, when not done right, could provoke several problems that cause trouble and lead to unsuccessful site transfers. In this post, I review the required steps in a WordPress migration to show you the most common problems I have found after three years migrating sites for customers of Migrate To WordPress. Migrating your WordPress site to another location should be a painless process: you just have to export your database, import it to the new host, move your files there, configure everything and make the new site live.

Local by flywheel stuck on starting local machine