Read this before you quote the work
The most forgiving destination for an exported site, because an .astro file accepts unmodified HTML. You can paste an exported page in verbatim and it builds — no attribute conversion, no framework idioms required on day one.
The order that works
- 1Create the project: npm create astro@latest
- 2Put assets and fonts in public/ so their paths stay identical to the export.
- 3Create src/pages/<name>.astro per exported page and paste the markup in unchanged.
- 4Lift the shared header and footer into src/layouts/Base.astro.
- 5Move repeated content into src/content/ collections when you want it editable.
What you keep
- Markup verbatim — no JSX conversion
- CSS, animations, and asset paths
- Page-level head tags
What you rebuild
- Nothing, for a static marketing site
The mistake to avoid
Leaving every page as a standalone paste. It works, but the shared nav is then duplicated per page and every future edit is an n-file change. Extract the layout on day one.
Questions
›Can I import a Framer site directly into Astro?
The most forgiving destination for an exported site, because an .astro file accepts unmodified HTML. You can paste an exported page in verbatim and it builds — no attribute conversion, no framework idioms required on day one.
›What transfers from Framer to Astro?
Markup verbatim — no JSX conversion. CSS, animations, and asset paths. Page-level head tags.
›What has to be rebuilt?
Nothing, for a static marketing site.
›What is the most common mistake on this migration?
Leaving every page as a standalone paste. It works, but the shared nav is then duplicated per page and every future edit is an n-file change. Extract the layout on day one.