Three things you are actually buying.
The architecture decision
The right framework, host, and content model for your site, your team, your integrations, your SEO and AEO goals, and how much autonomy you want to give AI.
The migration itself
Design, content, forms, analytics, metadata, and redirects, rebuilt and verified pixel for pixel against the site you have today.
The operating transformation
Repo, host, previews, agent instructions, organizational context, approvals, and Dispatch onboarding, so your team can operate the site with AI from the week you land.
You have options. That is the point.
Platforms want you to migrate deeper into them. We migrate you into your own code, then recommend the host per site.
| Consideration | Astro + Cloudflare | Astro + Netlify | Next.js + Vercel |
|---|---|---|---|
| Content volume | Best for content-led sites | Best for content-led sites | Strong at any volume, more to set up |
| Interactivity | Static first, islands where needed | Static first, islands where needed | Strong for app-like pages |
| Forms and auth | Forms yes, auth is extra work | Forms built in, auth is extra work | Forms and auth are native |
| Content model | Git-based content | Git-based or headless CMS | Headless CMS or database |
| Budget and hosting cost | Varies by plan, low for static | Varies by plan | Varies by plan, scales with traffic |
| Team and preferred agent | Any agent, content-shaped repo | Any agent, content-shaped repo | Any agent, app-shaped repo |
| Time to cut over | Fastest for content sites | Fastest for content sites | Longer where app features are rebuilt |
Content lives in git for most business sites, with a headless CMS or database where the site needs one. Costs vary by plan and are billed by your providers, not by Dispatch.
How a migration runs.
01
Assess
Your site, platform, content, integrations, traffic, and how your team works. Pages inventoried and scored, options written up.
02
Architect
Framework, hosting, content model, integrations, and the AI operating workflow, recommended per site with the reasons.
03
Migrate
Rebuild and move it, protecting design, content, functionality, analytics, and search visibility. Every page pixel-checked against the live site; redirects and sitemap mapped.
Pixel check
26 of 26 pages match
/
Match/services
Match/blog/what-to-expect
Match
04
Connect
Dispatch, organizational context, workflows, permissions, approvals, and crawl cadence, set before the first agent change ships.
05
Launch
DNS, forms, analytics, search console. Live on an AI-native foundation, with the record already running.
What a migration can include.
We migrate from
- Webflow
- WordPress
- Squarespace
- Wix
- Framer
- HubSpot CMS
- Legacy and proprietary platforms
It can include
- Design and page reconstruction
- Content and media
- Forms and business integrations
- Analytics and conversion tracking
- SEO metadata and structured data
- URL preservation and redirects
- Performance and accessibility
- Repo, hosting, preview, and deployment setup
- Agent instructions and organizational context
- Dispatch onboarding
What you keep
Your content and blog.
Your URLs, redirects, and rankings.
Your design, matched pixel for pixel.
Your code, in your repo, with no lock-in.
Nothing is locked in.
Not even to us.
Platforms keep you by holding your site. Dispatch keeps you by being useful. Leave tomorrow and you take everything with you.
Your website keeps running.
Code, content, and history live in your repository and your host, not in Dispatch. Switch Dispatch off and nothing about the live site changes.
Your history stays in git.
Every change ships as a normal commit. Restore points, branches, and previews are yours whether or not Dispatch is watching.
Your knowledge exports.
Prompts, context, agents, workflows, documents, and the full request and approval record download from Settings as JSON and Markdown, any time.
Your agent is your choice.
Bring Claude Code, Codex, or Gemini today and something else next year. Dispatch governs the work; it never owns the tool.
Recent migrations.
By type. Every one landed connected to Dispatch.
Law firm
Webflow to Astro on Cloudflare Workers. Pixel-verified against the live site, git-based blog, governed from cutover.
Financial advisory firm
To Astro on Netlify. Two design variants delivered as live previews.
Agency
Next.js on Vercel. Runs its own site on Dispatch.
Migration is only the beginning.
A faster site on modern infrastructure is valuable. A site your team can improve continuously with AI is the point.
- Request changes in plain language
- Approved brand and business context for agents
- Preview and approve before anything ships
- Decide which changes need human review
- Every human and agent action on the record
- Restore any version
Get a migration quote.
Scoped, fixed quotes for most business sites. A paid assessment is credited against the migration.
Tell us about the site and we come back with the architecture we would pick, what the move includes, and the number.
Migration questions, answered.
Quick answers on running a website that AI agents build and your team governs. More in the Knowledge Center.
No. The site is rebuilt to match, and every page is checked pixel for pixel against your live site before cutover. Where a page differs, the difference is fixed or shown to you and agreed before launch. Design updates, if you want them, are scoped separately so the migration itself stays a like-for-like move.
Leave the CMS. Keep everything else.
Tell us about your site. We come back with the architecture we would pick and a scoped, fixed quote.