> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/choosing-and-switching/getting-started/import-classic-projects.md). # Import Classic Projects The Classic Project Importer is an experimental feature. It can bring over the page structure and settings from your Classic project, but content import is less reliable because many page types cannot be mapped directly to Elements components. {% hint style="danger" %} **This is an experimental feature!** Please read the full document before importing a project. {% endhint %} Keep in mind this tool is designed to **help you move content across, not to recreate your site’s design**. You will need to rebuild the layout and styling using Elements components. Think of it as a way to save time copying text, images, and page structures rather than a one-click migration. If you’re planning a move from Classic, we strongly recommend reading the rest of the documentation to understand how Elements works, what can be imported, and what you’ll need to redesign. Watch the videos below to learn more about importing Classic projects into Elements.
Cover image
Dev Diary 96How to Import Classic Projects into Elements./files/ca3fBp6WOdm8puaLT17Shttps://youtu.be/-Eu-o9zRSmE
Dev Diary 97Import Stacks, Foundry and Foundation-based Projects./files/1yoIdbSsHEBT0AlaCvYphttps://youtu.be/JFymG65pDTw
## Importing a Classic Project To import a RapidWeaver Classic project, launch Elements and choose **File › \[Beta] Import Classic Project…**. ## Project Structure Elements will import all important site information including: * All pages, including file names, browser titles, page names and folder names * Page-level scripts * Meta information * SEO information * Robot tags * Site settings, including the name, site URL and logo * Favicons * Resources, including Stack page resources * Publishing destinations ## Styled Text Page Text from Styled Text pages is placed in Typography components, while images are placed in Image components. ## HTML and Markdown Pages These pages will be converted into code pages. ## Photo Album Page Elements imports photos from each Photo Album page, places them in a folder within Resources and creates a page containing a Photo Gallery component. ## Stack Plugin Pages Elements imports Stack pages and does its best to preserve content from popular stacks and frameworks. The importer transfers content but does not reproduce the styling of the original page. {% hint style="warning" %} **The Classic Project Importer does not yet read Partials.** To work around this, you may want to unpack any partials and save a copy of your Classic project before you import it into Elements. In Elements, [Globals](/elements-docs/using-elements/reusable-content/global-templates.md) provide a modern, customisable way to include shared content throughout your website. {% endhint %} ### Stack Resources Elements imports all Stack page resources, then removes duplicate files to make the project and published site smaller. ### Supported Stack Content Elements currently imports raw text and image content from a predefined list of stacks. Content is imported with minimal properties and does not retain colours, links or other styling. Elements will attempt to import content from the following stacks. Unknown stacks will be converted into named Containers. #### Built-in Stacks * Text > Text * Markdown > Text * HTML > Text * Header > Text * Quote > Text * Image & Site Image > Image * Button > Button * Column stacks will be converted into the Grid Component and use the corresponding number of columns. #### Foundry 2 * Button > Button * Container > Container * Vertical Center > Container * Header > Text * Header Plus > Text * Paragraph > Typography * Grid Content > Grid * Image > Image * Banner > Container * Margins > Container #### Foundry 3 * Container > Container * Columns Grid * Col > Container * Header > Text * Paragraph > Typography * Image > Image #### Foundation 6 * Container > Container * Column stacks > Grid * Grid stacks > Grid * Header > Text * Header Pro > Text * Text > Text * Quote > Text * Label > Text * Code > Text * Picture > Image
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.realmacsoftware.com/elements-docs/choosing-and-switching/getting-started/import-classic-projects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.