I have Wordpress sites already hosted by C-Panel hosting services already running but wish to import them as a local back-up in Local. How can I accomplish the following:
How can I export or create a back-up of my Wordpress site in my C-Panel hosting service
How can I import this Wordpress site back-up into Local to create a local replica of my website?
Thank you!
System Details
Local Version: 9.2.5+6810
Operating System (OS) and OS version: Mac OS Sequoia 15.6.1
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however thereās always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isnāt private info like passwords being displayed.
Before I start with my question I wish to share how impressed I have been with Local as a local development platform for Wordpress and with your customer support. Every time I have had a question about Local and posted it here, I was surprised with a quick and very detailed answer from you that fully addressed my question or concern. Thank you very much for your help.
As for my question, I am experiencing a problem and it may well be related to my hosting service. I have downloaded and installed WP Migrate as you recommended. I tried to run it and produce Wordpress back-ups for three Wordpress sites I have with GoDaddy but all three failed. One returned the following message:
Migration Failed
The Export Migration failed during the migration initialization stage.
The string did not match the expected pattern.
The other returned the following message:
Migration Failed
The Export migration failed during the migration initialization stage.
Internal Server Error.
Are you able to identify the error and how to fix it? If not, do you know another plugin or back-up protocol that can produce a back-up in a format that can be imported by Local?
Then run the import again and check the file in your WordPress install at wp-content/debug.log, which can reveal errors that arenāt normally available on the plugin screen.
If this is a production site, donāt forget to change the ādefineā lines back to their original state after saving your debug.log files.
Thank you again for your response and for your help. I have tried to follow your instructions but wasnāt able to resolve the problem. I am not an IT professional and my knowledge of Wordpress is limited. Would you be able to help me export my sites so I can import them into Local? It goes without saying that I would be happy to pay your fee for performing this service. Please let me know and how we can contact by e-mail outside of this forum.
Sorry to hear that, @JRC. We donāt offer paid consulting, but you could try making a zip file manually from your siteās database and wp-content folder:
Download your siteās wp-content folder (from a site backup or using SFTP).
Export your siteās database (your C-Panel hosting may offer this feature, or look for PhpMyAdmin and use the export option there).
Compress the wp-content folder and the exported database SQL file together into a zip file on your computer.
Drag that zip file into Local.
On macOS it looks like this, but Windows is similar:
Hi nickc and thank you again for your very helpful response.
I have one questions before I proceed. I was able to produce one debug log and it showed the message PHP deprecated on numerous lines. I noticed that the version of PHP being used on my hosting panel is 7.4 but the most recent is 8.5. I tried to switch to a higher version which starts at 8.0 right after 7.4 and kept going up. However, whenever I change the version of PHP from 7.4 to any other version my sites stop working.
Could PHP be the reason I am unable to export my sites properly? In this case how can I upgrade my Wordpress sites so they become compatible with the more recent version of PHP?
Itās possible that the āInternal Server Errorā and āstring did not matchā errors you saw during the WP Migrate exports are due to out-of-date themes or plugins, which could also affect your ability to upgrade to a newer PHP version.
I linked to some general guidance about how to safely update PHP below. You could follow the guide to update plugins and see if you have any that are not compatible with newer PHP versions.
If you can successfully update to a newer PHP version, you could then try running WP Migrate again.
Forgive me the long delay in providing a response but it took me a while to solve the problem. Since I donāt have advanced knowledge of Wordpress and you couldnāt help me with it, I contacted my hosting service (GoDaddy) and contracted their technical support specialists to do it. They upgraded the PHP, have all sites running on the latest PHP version (or one version before the latest) and the sites are running fine. After PHP was updated the problem remained as it was - the WP Migrate plugin still wouldnāt work. After working on the sites some more the specialist shared the problem was in the .htaccess file and he made some changes on it.
After these issues were resolved I was able to run the WP Migrate plugin, export all three Wordpress sites and import them into Local. The export process with WP Migrate and the subsequent import into Local couldnāt have been any easier. It worked exactly as you described and all three sites appear to be working just fine in Local.
I want to thank you one more time for you amazing support and for all the detailed instructions you shared so I could solve this problem.
Actually I have one more question if you allow me. Itās not entirely related to this post but still related to the same sites I am trying to build in Local.
After I started working on the sites I noticed one keeps asking me to āTry Againā every time I try to save the site after I make some change. Let me be more specific.
I am editing the page contents using the option āEdit with Diviā. Once I make my change I go to the bottom of the page and click on the plus sign on the lower right hand corner to save the changes and a message appears:
This is kind of a general error message that could have a lot of different culprits and might take some additional troubleshooting. Here are some resources you could start with:
As far as server resources, the Local defaults should be more than enough to run Divi on their own but if you are running other plugins itās possible there could be a resource bottleneck so you could try boosting the memory limit. We have some instructions on how to do this at the bottom of our performance guide here: Troubleshoot: Performance Issues - Local
I did exactly what you recommended and it solved the problem. Memory limit for the site was set to 256M. I changed it to 512M and it stopped display the error message.
Thanks for letting us know @JRC! Iāll go ahead and close this out for now but if you have any other questions or concerns donāt hesitate to reach back out. We are always happy to help!