> 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.md).
# Moving from Classic
{% hint style="success" %}
This guide will help you migrate successfully from RapidWeaver Classic to RapidWeaver Elements.
{% endhint %}
Elements is a fresh, modern way to build websites, but you are not starting over. Most of what you already know still applies; Elements simply offers a more modern workflow. This guide brings together everything you need to make the move.
Elements also includes many new features and improvements to the RapidWeaver experience. Once you become familiar with the workflow, building and maintaining websites becomes much easier.
### Four Things to Get You Started
Moving from RapidWeaver Classic? We will guide you through the process one step at a time and at your own pace. The guide contains four sections that you can explore as you learn Elements. Our in-depth manual and videos can then help you discover more of its features.
{% hint style="warning" %}
The videos in this guide are **slower and more detailed** than our general tutorials, giving new users time to follow along and understand each step. If you get stuck, [ask on our forum](https://forums.realmacsoftware.com/), where we are always happy to help.
{% endhint %}
#### 01: The Phrasebook
There is always a learning curve when moving to new software, and the transition from Classic to Elements is no different.
Elements uses new names for concepts you probably already know. For example, stacks become components and partials become Globals. [*Read the Phrasebook*](/elements-docs/choosing-and-switching/getting-started/the-phrasebook.md) for a quick translation guide.
#### 02: Switching to Elements
A slower-paced video series that assumes no prior knowledge. Build your first project, style it, make it responsive and publish it from start to finish. [Watch the videos](/elements-docs/choosing-and-switching/getting-started/rapidweaver-elements-vs-classic.md).
#### 03: Starter Projects (coming soon)
Ready-made projects covering the types of sites people build most often. Open the one closest to yours, follow along and make it your own.
#### 04: Import a Classic Project
Move an existing Classic project into Elements. The [Import Classic Projects](/elements-docs/choosing-and-switching/getting-started/import-classic-projects.md) guide explains what carries over, what doesn’t and how to handle the remaining work.
### Take Your Time
**RapidWeaver Classic isn’t going anywhere.** Your existing sites will keep working, and you can continue using Classic while you learn Elements. Move at your own pace, one project at a time.
### Still Feeling Stuck?
If you are struggling to recreate a specific website or layout, [ask on the forum](https://forums.realmacsoftware.com/). Share a screenshot or describe what you need, and we’ll guide you towards a suitable solution in Elements.
### Frequently Asked Questions
Will my existing RapidWeaver Classic themes be compatible?
Elements doesn’t support Classic themes. This was a difficult decision, but Elements has been built around a new, modern design system.
Can I import my RapidWeaver Classic projects into RapidWeaver Elements?
Yes, but you'll need to do some work. 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. You can learn more about it in the [Import Classic Projects section](/elements-docs/choosing-and-switching/getting-started/import-classic-projects.md).
Is it possible to use RapidWeaver Classic and RapidWeaver Elements side-by-side?
Yes. You can install and run both applications on your Mac, allowing you to maintain older projects in Classic while migrating or developing projects in Elements.
Will RapidWeaver Classic be phased out and replaced by RapidWeaver Elements?
No, both versions of RapidWeaver will coexist as they cater to slightly different customer needs.
RapidWeaver Classic continues to serve customers who maintain and build websites using legacy plugins and add-ons. We will continue to develop and update RapidWeaver Classic to support this workflow. RapidWeaver Classic requires macOS 10.14 (Mojave) or later.
RapidWeaver Elements represents our vision for reimagining web design on the Mac. It makes building no-code websites easier and more powerful than ever.
Do I have to switch now?
No. RapidWeaver Classic isn’t going anywhere, so you can keep using it while you learn Elements. There is no switch-off date; move each project when you are ready.
Will my Classic add-ons and stacks work in Elements?
No, but Elements differs from Classic because it includes everything you need to build a complete website. If you need a feature that is not built in, a thriving community of third-party developers now builds and sells add-ons for a wide range of requirements.
---
# 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.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.