Local 3.3.0 to 5.2.3

Support Uncategorized
4

In that case, maybe an alternate method might work. Here are two that you could try. They’re a little more work than what I described above, but they might overcome problems in the Local import script, if you’re seeing them.

The first approach is one that I use regularly when moving a Local site to a notebook computer when I travel. It involves using a backup plugin like UpdraftPlus to backup the site in one installation of Local (e.g. on my desktop workstation) and then to import it into another installation (e.g., on my notebook):

  1. Use UpdraftPlus or another WordPress backup plugin to backup your site from Local 3.3.0 to an external location. That could be a folder on your computer or a cloud service like Google Drive.
  2. In Local 5.2.3, create a site identical to the one you want to move – same name, same everything, but in a different folder.
  3. In this new site running in Local 5.2.3, install UpdraftPlus or whatever backup plugin you are using.
  4. Use the backup plugin to restore the backed up files and database from your original site.
  5. You should now have a functional site running under Local 5.2.3.
  6. I’ve never had this fail. I use it regularly to bounce sites back and forth between computers. If you want to return the site to your desktop workstation, just use UpdraftPlus to backup from the notebook and restore it to the desktop.

The second approach is a more direct way of doing the same thing:

  1. With the site running in Local 3.3.0, go to the database tab and open Sequel Pro
  2. Go to File > Export and export the database.
  3. Create an identical site in Local 5.2.3 as above.
  4. Remove the wp-content folder from the site you just created and replace it with a copy of the folder from the original site. This will give you your plugins, images, and theme files.
  5. With the site running in Local 5.2.3, go to the database tab and open Sequel Pro.
  6. Select all the tables in the sidebar on the left and delete them. Yup. Delete them. Don’t worry about messing this up. It’s easy enough to recreate the new site if something goes wrong.
  7. Go to File > Import and import the database you exported in step 2.
  8. You should now have your site running under Local 5.2.3.

One of these methods will almost certainly work for you. And once you’re running in 5.2.3, I think you’ll like it. It’s significantly faster.