Migrate from other platforms
Lyra writes into a git-based blog, so if your posts live in a hosted CMS you migrate to a Markdown-in-a-repo setup first. The platform changes, but the discipline that protects your rankings does not. This page covers the shared playbook and links to the detailed guide for each platform.
If you are on Framer, see the dedicated Migrate from Framer guide.
The discipline is the same everywhere
Every platform migration protects rankings the same way. Follow this regardless of where you are moving from:
- Map every indexed URL. Pull the full list from Google Search Console's Coverage report and build an old-to-new URL spreadsheet. Do not trust the CMS's own page list as complete.
- Decide your new URL structure first. Settle it before writing redirects.
- Export your content and rebuild its structure. Get your posts out, then recreate categories, tags, authors, and frontmatter as real structure in the new repo. Exports usually flatten these relationships. See Blog frontmatter.
- Redirect with 301s. Write permanent 301 redirects for every mapped URL on the new host. A 301 carries rankings across; a 302 does not. Handle a domain change at your DNS provider or registrar.
- Launch the site and redirects together, then submit the new sitemap in Search Console the same day.
- Watch and hold. Monitor Coverage and Performance daily for two weeks, then weekly through 90 days. Keep redirects live for at least a year.
Platform playbooks
Each platform has its own export path and its own gotchas. The Lyra blog has a sourced guide for each.
| From | What changes | Full guide |
|---|---|---|
| Webflow | CMS Collections do not map cleanly to Markdown; rebuild the structure | Webflow to git-based blog migration |
| WordPress | Moving to a static framework like Astro; real cost and timeline ranges | WordPress to Astro migration |
| Ghost | Ghost ships schema and sitemaps already; what you keep and what changes | Ghost to git-based blog migration |
| HubSpot | Why SaaS teams outgrow HubSpot's cost tiers; the redirect checklist | HubSpot to git-based blog migration |
| Notion | Notion's publish flow has no sitemap or per-page meta control | Notion to git-based blog migration |
A note on headless CMS
If you are considering a headless CMS (Contentful, Sanity, Storyblok) instead of a fully static git-based blog, know the tradeoff first. A headless setup adds a sync step between publishing in the CMS and the page being live as HTML, a webhook or revalidation that can fail silently and leave a page invisible to crawlers for days. A git-based static site removes that step by construction: a merged pull request is both the publish event and the build. See Headless CMS vs git-based blog.
Lyra works with a git-based blog. If you land on a headless CMS, she does not write to the CMS content store.
Then connect Lyra
Once your posts are Markdown files in a repo with frontmatter, and your redirects are live, your blog is ready:
What's next
- Choose a framework: Pick a static site generator.
- Blog frontmatter: The frontmatter Lyra learns.
- Migrate from Framer: The Framer-specific guide.
- Connect your repository: Once your blog is ready.