> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/upgrading/migrate-from-umarketingsuite.md).

# Migrate from uMarketingSuite

You cannot migrate directly from uMarketingSuite to Umbraco Engage 18. Because uMarketingSuite runs on Umbraco 13, the move requires two separate stages.

{% hint style="warning" %}
Migrate from uMarketingSuite to Umbraco Engage **17** first. Only then upgrade from Umbraco Engage 17 to 18. Do not attempt to move from uMarketingSuite to Umbraco Engage 18 in a single step.
{% endhint %}

## Migration path

1. **Migrate from uMarketingSuite to Umbraco Engage 17.** Follow the [Migrate from uMarketingSuite](https://docs.umbraco.com/umbraco-engage/17.latest/upgrading/migrate-from-umarketingsuite) guide in the Umbraco Engage 17 documentation. It covers the full process, including the prerequisite checks, package and namespace changes, and database migration scripts.
2. **Upgrade from Umbraco Engage 17 to 18.** Once your site is running on Umbraco Engage 17, follow the [Version Specific Upgrade Notes](/umbraco-engage/upgrading/version-specific-upgrade-notes.md) to complete the upgrade to Umbraco Engage 18.

{% hint style="info" %}
The upgrade from Umbraco Engage 17 to 18 requires the database schema alignment to be completed. See the [Version Specific Upgrade Notes](/umbraco-engage/upgrading/version-specific-upgrade-notes.md) for details.
{% endhint %}


---

# 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.umbraco.com/umbraco-engage/upgrading/migrate-from-umarketingsuite.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.