Replatform Craft CMS to Astro
Keep Craft running, or move it to Astro — whichever is cheaper to own.
Craft CMS is a well-built content system and we support teams already running it. But most Craft sites we are handed do not need a database in front of every page request. Where that is true we re-platform to a static Astro front end on Cloudflare — the same content, the same URLs, served from the edge — and the licence, the PHP hosting and the patching come out of the publishing path with it.
Craft CMS 
Astro
Cloudflare 
Sanity, if you edit What actually changes
Your design is carried across exactly as it is. A redesign is a separate project, quoted separately, and only if you want one.
Website replatforming
Off Craft CMS. Onto Astro, served from Cloudflare's edge.
Craft CMS AstroCloudflare Sanity, if you edit An ageing content management system costs you three ways at once: maintenance and licences you keep paying, a break-in risk you carry, and slow pages that lose the visitors your ads and search already paid for. Replatforming removes all three, keeps your design, content and addresses, and leaves a site ready for what comes next.
Why replatformWhat staying on Craft CMS costs you
The valueWhat replatforming returns
A server and plugins still yours to patch
The site runs code against a database on a server you are responsible for patching, and every plugin is third-party code with the same reach.
Attack surface removed
No plugins. No database. No server of yours to patch. The category of exposure disappears instead of being managed.
Upgrades that cost money as well as time
Plugin licences are tied to major versions, so every upgrade is a purchasing decision as well as an engineering one. A plugin not carried forward holds the whole site back.
Nothing to re-license or port
Content, design and web addresses come across, and upgrades stop being a purchasing decision.
Licences billed every year
An annual platform licence, annual plugin renewals, and a server with a database to maintain. Billed every year, used or not.
Maintenance cost removed
No platform licence. No plugin renewals. No server. Static hosting that does not climb with traffic, and editing stays as good as it is today.
Speed depends on server load
Pages are assembled on request, so what the visitor gets depends on server load, and caching is something you have to tune and trust.
Measurably faster pages
Pages are pre-built and served from the edge, with nothing to tune. At least a 20 per cent improvement where there is room for it, measured on the same test.
Live state split across two places
Content and configuration are spread between the control panel and the project files. The live state of the site is recorded in no single reviewable place.
Versioned, with one-step rollback
Every change versioned, reviewed and tested before release. Rollback to any previous version in one step. Recovery in minutes.
AI cannot reach your content
Your content is locked in a database behind a login. An AI tool cannot act on what it cannot read.
AI and agentic foundations
Content becomes machine-readable and deployment becomes something software can run. Module 01 of the roadmap below, and the prerequisite for every module after it.
Our own site runs on it. Every page sits in Google’s “good” band for speed, on mobile and desktop, measured 17 September 2026.
How we replatform
01
Discovery
We map the current site, its content, integrations and traffic, and agree what must be preserved.
02
Plan
A written migration plan: scope, page-by-page mapping, redirects, risks, and the measured baseline.
03
Approval
You approve the plan and the agreed targets. No build starts without it.
04
Replatform
Build, test and launch, then re-run the same tests and hand you the before-and-after.
Typical outcome: at least a 20 per cent improvement in measured performance where the current measurement leaves room for it, and the plugin and theme attack surface removed entirely. Measured on the same test, before and after.
Where this sits — the nine-module Growth Engine
- 01Websites
- 02Discovery
- 03Digital funnel
- 04Market sizing
- 05Data & KPIs
- 06Digital voice
- 07Automation & Integration
- 08AI
- 09SAOS
Replatforming is module 01, deliberately first: a fast, secure, agent-readable website is the asset every later module reads from and acts on. Each module stands alone, and there is no obligation to take the next.
What Replatform Craft CMS to Astro delivers
Supported either way
We support an existing Craft CMS site. The migration is an option we recommend on the evidence, not a condition of working with us.
Faithful re-platform
Entries, sections, assets, URLs and redirects carried across to Astro, so rankings and inbound links survive the move.
Editors keep a CMS
Move the content into Sanity as a headless CMS, or go fully static — whichever matches how often your team actually publishes.
Cheaper to run
Edge-served on Cloudflare — no PHP process, no per-request database, no licence renewal in the diary.
Primary tools
Craft CMSAstroSanityCloudflareSecondary tools
Sentry.io
Playwright
GitHub
Infisical
Looker
OpenAI
Anthropic Claude
n8n
ResendOne data layer · measured & owned
Every service creates data that is captured, measured and owned.
Replatform Craft CMS to Astro doesn’t just run. It generates signal. We land that data in one warehouse and turn it into live KPIs tied to a named owner, so performance is attributable and acted on, never trapped inside a single tool.
Data warehouse
Supabase
Snowflake
Keboola
BigQuery KPIs, dashboards & apps
Plotly
Retool
Apache Superset Platform-agnostic: we connect what you already use and add a warehouse only where it earns its place.
Generative, RAG and Agentic
Three different things — most businesses need more than one.
A licensed, self-hosted PHP content management system with a well-regarded editing interface and a flexible content model.
When you need it: It is a sound choice for a site that is edited constantly. For a site that is mostly read and rarely changed, the database in front of every page is cost without benefit.
Building every page once at publish time and serving the finished file, rather than assembling it again for each visitor.
When you need it: It removes the server, the database and the patching from the request path — which is where both the latency and most of the risk live.
A recorded rule for every old URL, pointing at its new home, applied on the day of the cutover.
When you need it: It is the difference between a migration that keeps its search rankings and one that quietly loses years of them.
Capability Maturity — we walk you up the five levels
Operated at Level 4 · Quantitatively Managed — measured, predictable and owned. We track this rank and raise it over time. See the five levels →
Why this matters
Functional value, value-stream value, and why it can't be ignored.
Supports an existing Craft CMS installation, and where it is the better outcome re-platforms it to a static Astro front end on Cloudflare — optionally with Sanity as a headless CMS — carrying content, structure, URLs and redirects across.
Takes a per-request database and a licensed PHP stack out of the publishing path: pages get faster, hosting gets cheaper, and the security surface shrinks — without losing the content the business already owns.
A Craft site is only as safe as the server it sits on and the version it is pinned to. Every deferred upgrade is an unpatched PHP stack in front of your brand, and every dynamic page render is speed you are paying for and giving away.
How we select technology
We choose technology last, for the outcomes it has to earn.
Never tech for its own sake. A tool joins the stack only where it measurably protects value, cuts cost or speeds delivery. It must fit a designed system, be owned where it counts, and be measurable from day one. How we select technology →
Speed
Modern, edge-served stacks are sub-second. Slow surfaces cost conversion and SEO every single day.
Cost
Cut licence, hosting and per-task SaaS fees. Pay for capability, not lock-in or idle enterprise tiers.
Security
Flat, edge architecture with almost nothing left to attack: fewer moving parts, smaller surface.
Ownership & no lock-in
Composable and self-hosted where it counts, so you own the system, not rent someone else’s.
Measurability
Clean data and KPIs built in. You cannot improve, automate or apply AI to what you cannot measure.
Fit to process
The right tool for a designed system, selected against process readiness, so it amplifies, not adds friction.
How we deliver · DMAIC
Every Replatform Craft CMS to Astro engagement runs on DMAIC.
Define the goal and its value, measure the baseline, analyse the real constraint, improve with a controlled build, then control the gains, so results are predictable, repeatable and defensible, not down to luck.
Agree the goal, value, budget & timescale up front.
Baseline the KPIs above: current state, not guesswork.
Diagnose the real constraint and the solution needed.
Build the chosen solution; prove the uplift.
Lock in the gains; monitor and sustain them.
FAQ
Common questions
What is Replatform Craft CMS to Astro?
Craft CMS is a well-built content system and we support teams already running it. But most Craft sites we are handed do not need a database in front of every page request. Where that is true we re-platform to a static Astro front end on Cloudflare — the same content, the same URLs, served from the edge — and the licence, the PHP hosting and the patching come out of the publishing path with it.
Why does Replatform Craft CMS to Astro matter?
A Craft site is only as safe as the server it sits on and the version it is pinned to. Every deferred upgrade is an unpatched PHP stack in front of your brand, and every dynamic page render is speed you are paying for and giving away.
How does Sentry deliver Replatform Craft CMS to Astro?
Supports an existing Craft CMS installation, and where it is the better outcome re-platforms it to a static Astro front end on Cloudflare — optionally with Sanity as a headless CMS — carrying content, structure, URLs and redirects across.
What do I get with Replatform Craft CMS to Astro?
Supported either way: We support an existing Craft CMS site. The migration is an option we recommend on the evidence, not a condition of working with us. Faithful re-platform: Entries, sections, assets, URLs and redirects carried across to Astro, so rankings and inbound links survive the move. Editors keep a CMS: Move the content into Sanity as a headless CMS, or go fully static — whichever matches how often your team actually publishes. Cheaper to run: Edge-served on Cloudflare — no PHP process, no per-request database, no licence renewal in the diary.
Free migration quote
Get a quote for your Craft CMS to Astro migration
Tell us where your site is and when you need it moved. A person reviews every request and replies within one working day. You and our team both get a copy by email.
Start here · the free first step
Replatform Craft CMS to Astro starts the same way every engagement does: with Discovery.
Two distinct moves. A free, no-obligation Discovery Session to frame your biggest measurable constraint and what it may be worth, with a one-page written summary afterwards. Then, where the evidence warrants it, the paid Discovery & Blueprint: 14 written outputs (value model, roadmap and business case) before a pound of delivery is committed.
Engaged alone or as one engine