Migration
Leaving WordPress, Wix, and Squarespace
The rebuild should feel like a cutover, not an amnesia event.
Inventory before design
We list URLs, titles, content worth keeping, forms, embeds, and integrations before we propose a new look. Wix and Squarespace sites often need a manual inventory because the export is incomplete. WordPress needs one because the database is full of leftovers.
What is useless gets dropped on purpose. What still earns its place gets a new URL or a redirect.
Redirects are part of the launch
Old URLs should resolve to the closest useful new page. A homepage dump for every legacy URL is how a migration wastes the equity it claimed to save.
The redirect list is reviewed like content, then checked after DNS moves.
Retire the old runtime
Leaving a builder half-connected — old plugins still mailing, old DNS still split — creates a long, confusing launch. The plan includes turning the old stack off.
The new site is the static build. The old login is not a backup plan that stays public.
Continue
When a Database Still Belongs
The honest cases where WordPress, an application database, or a builder-like tool still makes sense beside or instead of a static site.
Read →Forms and Commerce on Static Sites
How static sites handle inquiries, booking links, and commerce without becoming WordPress, Wix, or Squarespace shops.
Read →Version Control vs Click-to-Edit History
Why Git history is a better record than the undo stack inside WordPress, Wix, Squarespace, or a page builder.
Read →