The audit comes before the promise
We do not quote a migration before reading what is there. The first step is an audit: which pages actually get traffic, which plugins are load-bearing, what the forms are wired to, and what breaks if it disappears. Often part of the site should not be migrated at all — it should be retired, and that is cheaper than moving it.
Keeping the SEO you already paid for
A migration that loses rankings has not saved money, it has spent it somewhere you cannot see. Every URL is inventoried and mapped: what stays, what redirects where, and what genuinely disappears. Redirects go in before the switch, not after the traffic drops.
Why the site gets faster
The gain is not a plugin. Most aging sites render every page on every request through layers that were never needed. Rebuilt on Astro, pages are HTML by default and JavaScript only where it earns its place; served from Cloudflare, they are close to the visitor wherever the visitor is. The speed is a consequence of the architecture, not a setting.
The forms are the risky part
A migration usually breaks quietly at the point where somebody was filling in a form. We move the forms first, verify a real submission arrives where it should, and only then move the traffic.
Measured, not claimed
Before and after on the same real pages, with the same measurement. If the new site is not faster where it matters, that is a finding and not a footnote.