Website migration guides
One guide per move we run, from builder to builder, builder to Astro, and AI prototype to a production codebase. Each covers what carries over, how content maps, the redirect plan and the risks we check, with the timeline only where we can stand behind it.
Trusted by B2B and premium service brands in 17+ countries.
Moving between site builders and CMSs
- Framer to AstroMoving from Framer to Astro means rebuilding the front end in code, because Framer has no HTML export for self-hosting.Read the guide
- Squarespace to FramerSquarespace's export covers layout pages, one blog and gallery pages, so a Squarespace to Framer migration starts from a full crawl, not the export alone.Read the guide
- Webflow to AstroA Webflow to Astro migration is a rebuild, not an export: Webflow's code export leaves Collection lists empty and leaves form processing, site search and localised content behind.Read the guide
- Webflow to FramerMoving from Webflow to Framer, your CMS collections come across as CSV with rich text carried over as HTML, while the class system and interactions are rebuilt as Framer components and effects.Read the guide
- Wix to FramerWix sites cannot be exported, so a Wix to Framer migration rebuilds every page in Framer.Read the guide
- WordPress to AstroMoving WordPress to Astro replaces themes and plugins with a fast static front end, while posts, pages, categories and media come across from the built-in export.Read the guide
- WordPress to FramerA WordPress to Framer migration moves your posts into Framer's CMS through CSV import and rebuilds the theme as a Framer site your team can edit without plugins.Read the guide
Taking an AI-built prototype to production
- Bolt to productionA Bolt.new app becomes production software when it leaves the in-browser runtime for real environments, a backend chosen for your data, and code a team can review.Read the guide
- Lovable to productionTaking a Lovable app to production means keeping the code you own and rebuilding what a prototype skips: access rules, backend services, deployments and monitoring.Read the guide
- v0 to productionv0 already generates Next.js with React, TypeScript, Tailwind and shadcn/ui, so taking a v0 app to production rarely means changing stack.Read the guide
Our migration process
About two to four weeks, four stages.
Every stage has named outputs, so you always know what you are getting and when. We audit the old site first, map every URL, rebuild, then switch over with monitoring so nothing is lost.
Step 01Week 1
Audit & Inventory
We crawl the current site, inventory every URL and record what ranks and gets traffic.
Outputs
- full URL inventory
- ranking and traffic baseline
- content list
Step 02Week 1 to 2
Redirect Mapping
We map each old URL to its new destination and plan the structure so link equity carries over.
Outputs
- 301 redirect map
- URL structure plan
- metadata inventory
Step 03Week 2 to 3
Rebuild & Transfer
We rebuild on the new platform, transfer content and reapply metadata and structured data.
Outputs
- rebuilt site on staging
- migrated content
- reapplied SEO
Step 04Week 3 to 4
Switchover & Monitor
We point the domain, submit the new sitemap, then watch indexing and rankings to catch any drop early.
Outputs
- live switchover
- submitted sitemap
- post-launch monitoring
Common questions
Questions about website migration.
Everything teams usually ask before the first call.
Will I lose my Google rankings when I migrate?
Not if the migration is done properly, which is the whole reason to plan it rather than rush it. The risk comes from broken or missing redirects and changed URL structure, so we map every old URL to a new one with a 301 and keep metadata intact. We also baseline your rankings before launch and monitor after, so if anything moves we see it and fix it quickly.
Can you keep my existing URLs?
Where it makes sense, yes, and keeping URLs stable is the safest path for SEO. When the new platform or a cleaner structure means URLs have to change, we put a 301 redirect in place for every old address so search engines and existing links follow through. We never leave an old URL returning an error.
How long does a migration take?
About two to four weeks for a typical marketing site, depending on how many pages there are and how clean the current site is. Large sites, messy URL structures and heavy integrations take longer. We scope the timeline after the initial crawl, since the URL count drives most of the work.
Can you move my content without me re-entering it?
Yes. We transfer pages, posts and CMS content as part of the migration rather than asking you to rebuild it by hand. How smoothly it moves depends on the source platform and how the content is stored, and we confirm what can be automated versus what needs manual work during the audit.
Tell us what you are building.
A 30-minute call. We will look at where you are, what is not working, and what we would do about it. No deck, no pitch.