> I migrate WordPress, Webflow and Framer sites to Astro with a headless CMS. Roadmapping, existing content migration and editor training included. Canonical: https://augustynglowacki.com/services/migrate-to-astro # Move to Astro & headless CMS I help you use the move to rethink how the website serves your business. I work through the structure with you and rebuild it in Astro, with a CMS your team can use directly or through supported AI tools. [Plan your migration](/contact#lead-form) [Start with an audit](/services/website-audit) ## Content built around your business I build reusable page sections and a content model around your business. Your team can edit in the CMS or use Claude and Codex through supported connectors, with a way to review changes before publishing. I build on [Astro, now backed by Cloudflare](https://astro.build/blog/joining-cloudflare/), an open-source framework used by companies including Microsoft and Google. I keep the templates and editing rules in the repository so the next developer or coding agent can understand the site. ### Sanity my recommended choice Structured content with a Claude connector and a writable MCP server. [Astro & Sanity migration](/services/migrate-to-astro-and-sanity) · [Claude connector](https://claude.ai/directory/sanity) · [MCP setup](https://www.sanity.io/docs/ai/mcp-server) ### Storyblok Visual editing with a Claude connector and MCP access for Codex. [Astro & Storyblok migration](/services/migrate-to-astro-and-storyblok) · [Claude connector](https://claude.ai/directory/storyblok) · [MCP setup](https://www.storyblok.com/docs/tooling/mcp-server/setup) ### Payload For a CMS you run yourself, I use Payload. I plan hosting and updates with you. [Astro & Payload migration](/services/migrate-to-astro-and-payload) · [About Payload](https://payloadcms.com/docs/getting-started/what-is-payload) ### Contentful Shared entries and an editing workflow for teams already working in Contentful. [Astro & Contentful migration](/services/migrate-to-astro-and-contentful) ### Prismic Keep your existing content, with the Astro integration and editing workflow checked before the build. [Astro & Prismic migration](/services/migrate-to-astro-and-prismic) ### Keystatic A Git-based CMS. Editors use an interface while content stays in files alongside your code. [Astro & Keystatic migration](/services/migrate-to-astro-and-keystatic) ## A migration with the planning included I help you map your business onto a well thought out information architecture before the build starts. ### Roadmap workshop I agree the audience, pages and the job each page needs to do. You review the structure before I build. [How roadmapping works](/roadmapping). ### Astro rebuild and CMS I build the agreed site and editing setup, then migrate the existing content included in the scope. ### Launch and handover I check redirects and train your editors before launch. I agree who looks after the site. ## Before you migrate ### Can I start with an audit? Yes. An [audit](/services/website-audit) is optional and helps when you want to understand what is wrong before deciding to rebuild. Roadmapping is included in the migration, so I agree the site's purpose and structure before building it. ### Why Astro rather than Next.js? I've built projects with both. For a marketing site, I usually choose Astro because it [sends HTML and CSS by default](https://docs.astro.build/en/concepts/islands/), with JavaScript added for interactive parts. Visitors can read about your company without loading React for the page. I use Next.js when application features justify it, such as a customer dashboard. ### Why hire you if I can build it with Claude? If both you and I build the website with Claude, who do you think will get a better result? I bring the decisions and review that come from building production websites, including the content model and what happens when the site goes live. Claude helps me do the work. I remain responsible for checking it. ### Do I need a CMS if I already use a coding agent? A solo owner comfortable changing files with an agent and reviewing them in Git may not need one. Once editors need access, I look at how they preview, approve and publish changes. A Git-based CMS is also an option when you want an editing interface with content kept in the repository. See [how I approach sites without a CMS](/posts/no-cms-does-not-mean-no-content-model). ### Does moving off WordPress remove all maintenance? No. A static Astro site does not need a public WordPress installation to serve its pages. The CMS and any forms or other services still need care. I agree who maintains each part before launch, and can provide ongoing work through a [website retainer](/services/website-maintenance-retainer). ### Do you write the content? Your team supplies the copy and images. I can migrate your existing content, with the sources and volume agreed before work starts. Copywriting and adding new copy are outside the migration scope. ### What happens to my existing URLs? I inventory the current addresses and plan a redirect for each one that changes. I check the agreed redirects at launch. A migration can affect search traffic, so I do not promise unchanged rankings. ### Who owns the finished site? Your team owns the repository, code and content model. The project work transfers to you once the invoices for that engagement are paid. Existing tools and open-source dependencies keep their own licences. I work in a Git repository your team can access, and hosting and CMS accounts belong to you. I offer a handover session for whoever continues the work. ### What happens if you get sick for two weeks? I work with trusted subcontractors who can stand in for me. I sign a subcontracting agreement with them before they start, and agree any access to your code and content with you. ### Can I see a website you built that is still live? Yes. My [work page](/work) links to live projects and explains my contribution to each one. The [ECCA conference platform](/work/ecca-conference-platform) is a site I designed and built myself. I describe my role when a project was a team effort. ### How do I get my website back if we stop working together? The repository and service accounts stay accessible to your team. I document how to build and deploy the site, what it connects to and any unfinished work. I agree the final work and invoices with you under our contract, then remove my access when the handover is complete. A handover session is available on request. ### What is not included in the migration price? Your team supplies new copy and images. Copywriting, a new brand identity and ongoing maintenance are outside the build price. I agree the content migration volume and any integrations in the scope before work starts. CMS subscriptions, hosting and usage charges are paid through your accounts. ## Take your first step towards Astro ### Send me your brief Share your current site and what is getting in your team's way. ### Agree an action plan I review your situation and propose the migration scope and billing. ### Move to Astro I workshop the structure with you, then rebuild the site and help your editors get started. [Send your brief](/contact#lead-form)