Moving an existing site

What happens

Give the AI the address of your current website. It looks at the real site, asks you how to handle the design, and then rebuilds the site in Caelo: the homepage first, then the most important page types, then the rest. You answer a few questions and click Approve. You do not fill in forms or copy content.

The migration runs in its own chat, on its own branch. Other chats keep working in the shared draft undisturbed, and nothing from the migration reaches the site until it is staged. If the chat you are in already has unstaged changes, the AI asks you to start the migration in a new chat.

Step by step

1. The address. The AI asks only for the URL.
2. A first look. It reads the homepage and its navigation, works out the site's real page types (for example Pricing, Blog article, Use cases) and tells you its plan. Tag pages, date archives, author pages and other-language copies are filtered out as noise. It also sets the site's name, purpose and language from what it finds.
3. One design question. Before it builds anything, you choose: keep the design as close to the original as possible, refresh it (same brand, structure and content, modernised; the default if you are unsure), or let the AI propose a clearly improved direction.
4. The homepage first. The AI builds the homepage alone: header and footer once on the layout, your real logo, the content modules and a template. Images are copied into Caelo's media library, never linked from the old server. Then it shows you the result and asks whether the direction fits. Nothing else is built until you confirm.
5. Key page types. It builds two or three of the most important page types, one at a time, each as an example you can react to. Blocks that repeat across pages, such as a call-to-action band, become one shared module. Then it asks: build another type by hand, or import the rest?
6. The rest in bulk. Only now does it propose a crawl of the whole site. You approve it on a card in the chat (below). Each crawled page is rebuilt with the patterns already agreed, each with its own content. Larger sites are split across several helper agents working in parallel, and the AI reports progress as it goes.
7. Finish. The AI gives every page its meta description, sets the migrated pages to Published so they are included in the build, stages the result and closes with a migration report.

The AI stops for you at four moments: the design question, the homepage, the "another type or the rest?" choice, and the finish. In between it keeps working, unless something new goes wrong, such as a crawl that stalls or the budget running out.

The crawl

The full crawl is never started without an approval. Caelo's crawler stays on your site's own domain, honours robots.txt (including its crawl delay), uses your sitemap to find pages, and can be limited to one language or section of the site. For every page it stores the text, a screenshot and the design values it finds, such as colours and fonts. The rebuild works from that stored copy, so your old server is not asked again for each page.

Approving the crawl sets a spending limit for the run. You can also set a migration budget in the chat. The AI checks spending after the homepage, after the key types and before the bulk import, and pauses to ask if the limit is reached.

Rebuilt, not copied

Old page-builder markup (WordPress, Elementor, Divi and similar) is not carried over. Every page is written fresh as clean HTML in Caelo modules, also when you chose to keep the design. The content is complete: every heading, paragraph, list, image and link of the source page must appear, and the AI checks each rebuilt page against the source for anything missing.

Meta descriptions and addresses

• Meta descriptions are carried over. The description of each old page is taken over, shortened to at most 160 characters. Where the old page had none, the AI writes one from the content. A Stage would refuse published pages without one anyway.
• Addresses. Navigation links and pages use your site's own paths where possible, so most URLs stay the same. When a page gets a new address in Caelo later, a permanent 301 redirect from the old one is created automatically. Other redirects can be added in bulk by asking the AI, or under Settings → Redirects.

Nothing goes live by itself

The migrated pages start as drafts. Setting them to Published only means they are included in staging and live builds. The AI stages the result, the quality check runs, and you look at staging. Publish live stays your click. See Drafts, staging, publishing and Quality gate.

The migration report

The migration ends with a report in plain words: pages built per type, what the AI fixed on the way (for example typos or missing alt texts), what you should look at, pages the crawl could not fetch, and URLs it skipped and why. The AI does not call the migration finished while a page still links images from the old server or is missing content. It names those pages instead.

Past imports and their pages are listed under Settings → Site import.

Limits

• A full migration spends real AI budget. Set a limit before you start a large site.
• The crawler only reads public pages it can reach from your site's own domain.
• Caelo is pre-1.0. The migration flow is tested on real sites, but expect to review the result page by page before you publish.