> 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/cms/online-cms-editor/upgrading-and-downgrading-plans.md).

# Legacy Licenses and Upgrading to Pro

Elements CMS now offers one paid plan: **Pro**, purchased through FastSpring as a one-time payment. Solo and Studio are legacy plans that were previously sold through Creem.

Existing Solo and Studio licenses were not migrated to FastSpring. They remain valid and can continue to be used with the features and domain coverage included when they were purchased.

## Upgrade a legacy license

Upgrades from a legacy Solo or Studio license to Pro are handled by Realmac support. [Contact Realmac support](https://www.realmacsoftware.com/support/) and include:

* The email address used for the Creem purchase.
* Your current plan, if known.
* The domain where the license is active.

We will explain the next steps for your existing license and the FastSpring Pro purchase.

{% hint style="info" %}
There is no lower paid plan to downgrade to. Pro is the only paid plan available for new purchases.
{% endhint %}

## Move a legacy license to another domain

If you only want to move an existing Solo or Studio license without changing its plan:

1. Open the Online CMS Editor on the currently licensed site.
2. Go to **Workspace > License**.
3. Select **Deactivate domain**.
4. Open the Online CMS Editor on the new domain and enter the existing license key under **Already have a license key?**.

See [License Keys](/elements-docs/cms/online-cms-editor/license-keys.md) for license recovery and domain coverage details.


---

# 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/cms/online-cms-editor/upgrading-and-downgrading-plans.md?ask=<question>&goal=<endgoal>
```

`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.