Migrations
Move stacks without losing the search baseline.
4 migration playbooks covering the most common stack and domain transitions for JavaScript-heavy sites. Each guide includes pre-flight checks, step-by-step execution, rollback plan, and post-launch monitoring discipline. Read before kickoff, reference during execution.
- Moderate2 to 4 weeks
SSR to SSG migration on Next.js
Move from server-rendered Next.js to fully static generation without losing SEO equity, with sane fallbacks for content that still needs freshness.
Read the playbook
- Moderate1 to 3 hours
SPA to prerendered architecture migration
Add the ostr.io prerendering layer to a client-rendered SPA without rewriting it. The migration that buys crawler reach without an SSR rebuild.
Read the playbook
- Hard8 to 16 weeks
WordPress to headless CMS migration
Move from monolithic WordPress to a headless setup (WP-as-CMS + JS frontend, or full migration to Sanity/Contentful) without losing the SEO baseline.
Read the playbook
- Hard4 to 10 weeks
Domain migration with SEO equity preservation
Move from one domain to another (rebrand, M&A, ccTLD consolidation) without losing rankings, indexation, or backlink equity.
Read the playbook
Migration not listed here?
Most migrations share the same risk surface — URL preservation, redirect discipline, rendering parity, post-launch monitoring. The scoping call is the right place to map your specific path.
One constraint runs underneath all of them: the cutover and the rollback window are both bounded by DNS, not by the plan. Records have to be in place before delegation moves, and TTLs have to be lowered before the switch rather than after. Bridge DNS is being built around that sequence — zone import first, delegation second, reversible afterwards. It is in development and not yet available.