I’ve been using Local by Flywheel for years now and I love it. It’s a great environment for spinning up & developing WordPress sites. Better yet, you don’t have to use it with Flywheel hosting, you can just use it develop WordPress locally.
Now that Local “Lightning” is out, Local is much faster. It’s a great upgrade to what is usually an environment that just works, however it’s a different app.
Moving from Local by Flywheel to Local should be as easy as exporting one site and importing it back in. However, sometimes that doesn’t work.
It seems that the import/export functionality expects standard WordPress sites with standard wp-config.php files. Even though things worked fine in Local by Flywheel, they will not always import into Local.
The good news is you can work around import errors with a few manual steps.
- Start the site in Local by Flywheel.
- Export the site from Local By Flywheel – This is just a backup incase things go wrong.
- Export the database separately via Adminer.
- Stop the site in Local by Flywheel.
- Find the site folder on your computer and rename it to something different.
- Open Local.
- Create a new site in Local with the same name it had in Local by Flywheel.
- Find the new site folder on your computer and rename to something different.
- Find the old site folder from step 5 and rename it back.
- Import the database via Adminer.
That should do it. As long as you kept the site name correct, the site should now be transferred to Local.
In my option, Local should be able to detect and transfer files between apps without having to import and export. Especially when importing runs scripts which is where it fails most of the time. Maybe some day they’ll figure out a better import process.