Platform Migration
A migration is a data problem, a redirect problem and a trust problem at once. The technical part is usually the easiest of the three — the hard part is that the business keeps trading while you do it.
How I use it
Wee Rock Art — auditing before migrating
The Square catalogue turned out to be a 2019 snapshot: sync worked at launch then quietly died, stranding 129 products added over the four years since. Auditing both systems before touching either is what established WooCommerce as the source of truth rather than assuming the newer one was.
Wee Rock Art — seeding a live catalogue
Idempotent, re-runnable importers created 132 missing items with images, built ten collection categories and corrected eighteen stale 2019 prices upward. Verified by live read-back: 150 of 150 present, zero price mismatches, zero errors.
Wee Rock Art — legacy records that look like junk
121 orphaned catalogue items would normally be archived on sight. They were the owner’s point-of-sale library for in-person markets, so I excluded them at the storefront layer instead of touching her live system. Migrations go wrong when you optimise the data and break the business using it.
Switch Cart — tooling the repeat case
Built a WooCommerce-to-Payload migration tool rather than repeating the same export-and-reconcile work by hand a second time.
What I use
- WooCommerce
- WordPress
- Square Catalog API
- Astro
- Python
Where you can see it
Related skills
Want the detail behind any of this?
I can walk through any of it in as much depth as you want.