Skip to main content
Website migration is still in development. Fimo sets up the target project; your coding agent reads the source site or its files and does the rebuild.
Do not treat the generated project as complete. Compare it 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 project, 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. 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. 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 project.

​
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.