Skip to main content
Fimo sets up the target site; your coding agent reads the source site or its files and does the rebuild.
Compare the rebuilt site with the source and finish any missing pages, content, forms, redirects, metadata, and interactions before you deploy or publish it.

​
Choose your source

Published URL

Your coding agent opens the public site in a browser and rebuilds what it sees. Public pages expose less than source files do.

Source files

Give your coding agent a repository, export, structured content, or media files to use as migration evidence.

​
Set up the target

Run one of:
This creates or links the Fimo site, scaffolds it with the framework you choose, and pushes the first commit. It writes no schemas, entries, assets, or forms, and it does not read the source site. To migrate an existing app folder instead, your coding agent links that folder with fimo link; see Migrate from source. Then ask your coding agent to run the migration. It loads the fimo-migration skill, reads the source itself, and imports the result with the normal fimo commands. See the CLI reference for every setup flag.

​
Review the result

Before you treat a migration as complete, compare the rebuilt site with the source. Check every route, content collection, asset, form, locale, redirect, and metadata field that matters to your site. Record anything missing or unsupported instead of assuming the migration preserved it. The migration skill’s QA gate checks the rendered site, not the repository. Your coding agent lists the routes and the brand, legal, and navigation rules the site must keep, then proves each rule on rendered pages. Once copy lives in Fimo, a search of the source files cannot show what visitors see, and a check that observes no pages or no links fails instead of passing. The migration report includes that result; treat a missing or failed guardrails section as an incomplete migration. The gate also checks that people can edit the text. A faithful copy of the source can still keep every word typed in the code, where Fimo Studio shows “Nothing to edit”. The check lists each visible text that no label or CMS field renders, and the migration is incomplete until that text moves into Fimo or you agree to keep it in code, such as a brand symbol or a legal line. Run it with Fimo’s editing metadata on: against the dev server, or a build made with FIMO_EDITING_METADATA=true. Saved browser captures must include a successful page response and its final URL. Missing response evidence or a reported navigation error fails the check. Internal navigation checks include relative links and links on the same origin. Your coding agent still needs to review the pages in a browser, including error pages served with a successful status, links to specific page sections, and external destinations. Preserve needed redirects in Fimo’s hosting config. Migration does not publish the result. Follow the normal deploy and publish workflow only after you have reviewed the site.

​
What’s next

Source limitations

Decide which source material to provide and what a public page cannot recover.

Migrate from source

Use an existing repository or export as evidence for your coding agent.