947 MBdatabase exported
Out of a host that allowed only FTP, through a full copy of the site run locally.
Online fashion shop · CH · 2024
Getting a shop's database out when the host allowed only FTP
The old host would not export a moving shop's database, so I got it out through a local copy, with that day's orders in it.
1 day
The shop ran on the new server with that day's orders in place.
An agency was moving a small WooCommerce shop to a new server that evening, and the database would not come out. The old host allowed only FTP, the site was very slow, and the database was 1.66 GB.
First I checked that I could get into the WordPress admin, so there was no need to fight with the host. Through the admin I took a full 10 GB copy of the site, ran it locally and exported the database there: 947 MB. The agency imported it on the new server.
The last order visible in the shop looked ten days old, so I checked the order table itself. That day’s orders were there. After the import the site kept pointing to my local copy. I wrote SQL to rewrite the site address in the key tables, tested it on the copy and showed it to the agency. They fixed the table prefix on their server and confirmed the shop working on the new server, with that day’s orders in place.
WordPress support for a German timber merchant's site
Two support cases on a timber merchant's WordPress site. I traced an admin hang on a copy, reopened a locked admin and measured why updates kept failing.
A German WooCommerce shop: theme migration and hack clean-up
I moved a small shop off an abandoned theme to Flatsome. Two years later I found a hack hidden since 2019 and cleaned it out with the catalogue intact.
A bilingual brand site and shop, through its relaunch
I put a new design and bilingual forms into a brand site and shop before launch, then supported it once it went live.
Contact
Have something similar?
Use the form or message me on LinkedIn.
Already working with me on Upwork? Write there.