Skip to main content
If you have a repository or export, your coding agent can use it as the main source for a migration. It rebuilds the site as a Fimo site rather than wrapping the existing application unchanged.
Review the rebuilt site against its source, because the workflow can leave pages, content, integrations, or behavior incomplete.

​
What to provide

Give your coding agent the source material you are allowed to use:
  • the source repository or builder export
  • structured content exports
  • referenced media files
  • a public URL for visual and metadata comparison, when available
Some repositories depend on private services or data that are not included in the checkout. Provide approved access separately when it is required. Do not add credentials to source files, migration artifacts, or reports. If the repository includes CMS code but not its deployed content, your agent asks how to continue. You can provide a limited read-only export, approve rebuilding the selected published pages from the public website, or migrate the code while leaving that content in the existing CMS. Public pages cannot reveal drafts, unlinked records, private fields, or all editorial relationships, so the migration records those gaps instead of guessing. See migration sources for the limits of each input type.

​
Choose the target folder

Your coding agent can put the existing folder itself on Fimo when you ask for that, or work in a separate copy when the original must stay untouched. Before it changes an existing folder, it keeps an exact copy of its original state, including uncommitted files, so you can compare routes, content, behavior, and visual details throughout the migration. Your coding agent follows the migration guidance shipped with your installed Fimo CLI. Install the Fimo skills first if your agent does not have them:

​
Approve migration decisions once

Your coding agent inspects the source before it changes the target. When the source cannot answer a decision, the agent groups the choices into one question screen when its coding environment supports one. Typical questions cover:
  • whether an existing integration should stay connected
  • whether environment configuration should stay where it is, move into Fimo, or remain unconfigured
  • whether missing CMS records should come from approved access, the public website, or remain in the existing CMS
  • when only part of the site is moving, whether links to the remaining pages should keep opening the current site or those pages should be removed and redirect to the migrated homepage
Asking to migrate a site does not authorize the agent to move environment values or credentials. It identifies key names without reading hidden values and asks before storing anything in Fimo. Add sensitive values as Fimo-managed site secrets, not in source files, migration reports, or chat messages. If you choose a partial migration and do not specify what happens to the other pages, the agent asks before setup. It does not leave links pointing at routes the new site does not implement. The first migration keeps the current framework and behavior wherever possible. When local Markdown or other bundled content moves into Fimo, the agent keeps those reads on the server or at build time and checks that the new API connection does not add avoidable delays. A major framework or router upgrade is separate work and starts only when you ask for it.

​
Review before completion

Source access improves the evidence available to your agent, but it does not guarantee a lossless migration. Verify the rebuilt site against the source and its exports. Check the routes, content, media, forms, locales, redirects, metadata, and interactions your site relies on. The coordinator gives each reviewer the scope and migration choices you approved, so an intentionally excluded route or integration is not reported as missing. Reviewers still inspect the finished site independently. Leave missing or unsupported items visible with a next action. Do not deploy or publish as a substitute for this review.

​
Check Next.js Preview security policy

Before changing Content Security Policy for a Next.js migration, inspect the app while it is loaded in Fimo Studio’s Preview iframe. frame-ancestors controls the Studio page that embeds the app; the app’s Preview URL is the framed site, not the parent. Resource directives such as script-src, connect-src, frame-src, and form-action should cover only Fimo resources the iframe actually uses. Do not add a Studio-parent WebSocket to the app’s CSP. Fimo’s Next.js integration does not currently rewrite response headers or adapt an application-owned CSP automatically, so a restrictive policy may still need a narrowly scoped Preview change. Preserve production protections and unrelated security headers.

​
What’s next

Migration overview

Understand the migration flow, current status, and review requirements.

Set up your coding agent

Give your coding agent the Fimo guidance that matches your CLI version.