Evidence
Migration evidence: URL maps, truth tables and live redirect parity for two Kirby-to-Astro moves
168 of 168 mapped old URLs on the two moved sites answer 301 to their new address on production.
Two sites moved to a new platform, every old URL checked.
For owners worried about broken links: every old URL gets a 301 redirect, checked against a crawl of the old site. The method moved prlwarehouse.com and a mortgage site: 168 of 168 mapped URLs answer 301.
The two moves
Your platform is slow, pricey or a cage, and you want out. Broken links, lost search listings and a lost weekend keep you stuck. That is the part we own: every old address gets a place to go.
We moved two of our own sites from Kirby, a content system, to Astro 5 and Tailwind 4: prlwarehouse.com, a warehouse-equipment store, and a mortgage site. Try one: an old prlwarehouse.com service-area address answers 301 and lands on its new page. [Kirby, Astro 5, Tailwind 4]
Live
prlwarehouse.com (production: the owner's pallet-racking brokerage site)
prlwarehouse.com, the warehouse-equipment store: 34 of 34 old URLs return a 301 to their new address on production.
Example
staging.prlwarehouse.com (noindex staging of the 2026-09-02 restyle)
A staging copy of prlwarehouse.com is where atomic releases and health checks are rehearsed before every move.
The parity table
Each old URL needs a destination on record before anything can check its redirect. The table counts what was checked, one plain request per URL, without following the redirect.
| What was counted | Result | Date | Source |
|---|---|---|---|
| Mapped old URLs answering 301, prlwarehouse.com | 34 of 34 | 1 Nov 2026 | GET check |
| Mapped old URLs answering 301, mortgage site | 134 of 134 | 1 Nov 2026 | GET check |
| Build tools per site | About 25 | 14 Oct 2026 | Toolchain audit |
The method
This part is for the technical reader.
Before the move, a crawl of the old site lists every page address. A truth table sorts each content folder into live, draft or unreachable. Each old URL gets a 301 redirect, and the redirects are checked against that crawl before launch. [truth table, 301 redirects]
We move every page, post and image and compare the text with the old site. A content-fidelity check fails the release unless only the declared change touched the text. A schema.org layer describes each page for search engines. [content-fidelity gate, schema.org]
Each release switches over atomically, with a health check and a way back to the previous version.
Built and verified on staging
Every build is verified on staging before it reaches production, and the redirect counts above are measured on production itself.
The target build
These pages belong to Colorado trade businesses, and the code behind their contact forms passed its checks against a test mail server. [PHP-FPM]
The static site examples show the kind of target build you can inspect. [Astro 6]
Moves for other people
We moved sites for other people too.
Tell us what you would change
Name your old platform. Nothing moves until a paid audit maps every page, redirect and risk and says which platform we would pick and why. The audit is yours to keep.