Six steps. No leaps.
Your current site stays live until the new one is ready. Launch is a planned cutover with a fallback.
Nothing goes dark
Your current site stays live and editable until launch day.
Everything is reviewable
Each phase ends with something you can open and check on staging. No slide decks.
You own it from day one
The code is in your repository and the hosting is on your accounts.
The six phases.
Click a phase, or let it play.
Audit
Every URL, collection, and integration, mapped.
- 01
Audit
We review your current site, CMS structure, URLs, integrations, SEO setup, and migration risks.
- URL & traffic inventory
- CMS collection map
- Integration list
- Risk register
- 02
Architecture
We define the target stack, content model, redirect strategy, and delivery plan.
- Stack recommendation
- Content model
- Redirect strategy
- Fixed scope & timeline
- 03
Build
We rebuild the frontend and set up the CMS, content types, components, and integrations.
- Component library
- CMS schemas
- Forms & analytics
- Preview environment
- 04
Migrate
We migrate content, media, metadata, and URLs, then check everything on a staging site.
- Content & media import
- Metadata & schema parity
- 301 redirect map
- Staging QA report
- 05
Launch
We deploy the new site, switch on the redirects, and check the site every day for 30 days.
- DNS cutover plan
- Rollback plan
- 30 days of monitoring
- Search Console checks: day 0, 30, 60
- 06
Support
You get documentation, editor training, and the option of a support plan with one dedicated developer.
- Editor training
- Technical docs
- Repository handover
- Optional support plan
Launch with a fallback.
We rehearse on staging. On the day, every step is checked and the old site stays ready.
- Content freeze window agreed in advance
- Final content sync from the old platform
- Redirects deployed and verified before DNS switch
- DNS cutover, with the old site ready as a fallback
- Live crawl for 404s, redirect chains, and missing metadata
- Sitemap submitted, Search Console monitored
What we need from you.
Less than you'd think.
- ✓
One decision-maker
Someone who can approve scope and sign off on launch.
- ✓
Read-only access
Platform, analytics, and Search Console during the audit.
- ✓
Editor time for training
A couple of sessions with the people who will publish.
- ✓
Your accounts
Hosting, repository, and CMS accounts live in your organization.
It starts with an assessment.
Architecture, risks, scope, and next steps for your site.