Migration | XAIO Docs

Why migrate to XAIO?

If you already have a site running on Lovable, Bolt, Base44, Manus, Webflow, WordPress or anywhere else, you can bring it into XAIO without rebuilding it from scratch. The agent reads what's there, rebuilds it as a clean XAIO project, and you keep iterating with prompts.

Three migration paths

Migrate from a URL — Paste the public URL of your live site. The agent fetches the page, extracts layout, copy, design tokens and assets, and rebuilds the structure inside a fresh XAIO project.

Migrate from a ZIP — Drop a ZIP exported from another builder (Lovable / Bolt / Manus / Base44 etc.). The agent runs a pre-analysis on the source code, identifies components, data models and business logic, then rebuilds it as XAIO with the same functionality and look.

Website renewal — Upload your existing site and ask the agent to rebuild a modern version. Same content, fresh design system, responsive, accessible.

Pre-analysis & XAIO.md

For a ZIP-based migration the agent first generates a XAIO.md file that captures the source project's design system, conventions and key decisions. You review and adjust before the actual rebuild starts. After migration, that same XAIO.md keeps documenting your project across every chat.

Smart model selection

Migrations use a higher-capability model by default — the agent needs to read potentially large source trees, infer intent and generate a clean rewrite, not just patch text. AI Task cost is a few times a normal turn but the result is a working project, not 30 iterations of fixing.

What gets migrated

HTML / CSS / JS structure → React + Vite + Tailwind
Pages and routes → React Router
Forms and submissions → wired into your XAIO backend (or external endpoints if specified)
Static assets (images, fonts, icons) → moved into the project's media library
Data models / collections → translated to PostgreSQL tables when relevant

What you'll likely tweak afterwards

Pixel-perfect alignment of edge cases
Custom integrations the source builder had baked in (those need to be wired through XAIO's integrations menu)
Anything bound to a third-party API key — drop the keys into Environment

Migration is one of those features where one well-formed prompt replaces a week of manual work — but the result is a real XAIO project, not a black-box import.