> For the complete documentation index, see [llms.txt](https://docs.beefree.io/beefree-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/beefree-sdk/getting-started/readme/migrating-from-another-provider.md). # Migrating from another provider to Beefree SDK If you are thinking of moving from a different content creation platform to the Beefree SDK, know that you are in good hands. Thousands of applications have been using our embeddable content builders since 2014, which means that our team has encountered a large variety of scenarios and guided customers like you through all sorts of migrations. We're here to help. ### Expert support We're known for providing a high level of support, which includes everything from the detailed technical docs that you are reading on this site, [extensive sample code](/beefree-sdk/getting-started/sample-code.md), and all the way to dedicated Slack channels for [Enterprise customers](https://developers.beefree.io/enterprise). We will learn about your business with an initial consultation followed by meetings with solution engineers, and set you up with an extended proof-of-concept period that allows you to get everything ready for your migration. ### Importing existing designs If your users have created a library of designs in your legacy tool, we know one of the key questions is always: "How do I get existing designs into Beefree without having to ask my users to recreate them from scratch?" We've got you covered here: #### Migrate any email HTML to the Beefree SDK with the HTML Importer API Your customers' existing designs will not need to be recreated from scratch in the Beefree builder. You can leverage the [HTML Importer API](/beefree-sdk/apis/html-importer-api.md) to take standard HTML emails and turn them into our proprietary JSON format. For a quick introduction to the benefits of this handy tool, see [HTML Importer API: From HTML to Beefree-ready JSON in seconds](https://developers.beefree.io/blog/html-importer-api-from-html-to-beefree-ready-json-in-seconds). #### Migrate MJML templates to Beefree SDK If you have legacy email designs created with MJML, our team can help you convert them into Beefree SDK JSON for loading in our editor. [Reach out to our customer support team](https://devportal.beefree.io/hc/en-us/requests/new) to learn more about the migration process. #### Migrating designs from Unlayer The process of switching content creation platform is particularly easy for those migrating from Unlayer. We have developed a tool that can help bulk-import your customers' designs: simply provide us with the Unlayer JSON files, and we'll convert them on our end to Beefree-compatible JSON documents, which your customers will be able to edit with the Beefree editor. Please [reach out to our team](https://devportal.beefree.io/hc/en-us/requests/new) to learn more about the process. --- # 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.beefree.io/beefree-sdk/getting-started/readme/migrating-from-another-provider.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.