Migration sources

Use the most complete source material you can obtain. A repository or structured export usually contains information that public pages do not show.

​

Source repositories

A source repository lets your coding agent inspect routes, components, content files, and application behavior. It may still depend on data or services that are not present in the checkout. Provide any content exports, media folders, environment-independent fixtures, and a public comparison URL that you are allowed to share. Do not put private credentials into migration artifacts.

​

Structured exports

CSV, JSON, XML, Markdown, and MDX exports can preserve content more accurately than rendered HTML. Their coverage depends on the source platform and the options used when the export was created. Check whether the export includes:

• every collection and record you expect
• stable IDs, slugs, dates, relationships, and locale fields
• referenced media files or usable public media URLs
• redirects, metadata, and form definitions

Missing fields cannot be recovered reliably from the export alone.

​

Builder and static exports

HTML, CSS, JavaScript, and media exports can provide layout and styling evidence. They often omit managed content, form processing, search, member areas, ecommerce behavior, and other hosted features. Treat platform-specific scripts and generated markup as source evidence. Your coding agent may need to rebuild their behavior with supported Fimo features.

​

Published URLs

In a URL-only migration your coding agent reads the published pages in a browser. It cannot reach unpublished pages, private content, complete CMS records, source components, or server-side behavior. Coverage is only as good as the agent’s review, so name the routes that matter and check them yourself. Authentication, blocked requests, and rate limits reduce what the agent can see. Start a URL migration from the migration overview. For a repository or export, use the source migration guide.

​

What’s next