# Migrating from another provider

### We've got you covered :-)

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, to [extensive sample code](https://docs.beefree.io/beefree-sdk/getting-started/sample-code) 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

Your customers' existing designs will not need to be recreated from scratch in the Beefree builder. You can leverage the [HTML Importer API](https://docs.beefree.io/beefree-sdk/apis/html-importer-api) to take standard HTML emails and turn them into our proprietary JSON format.&#x20;

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

### 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.&#x20;

Please [reach out to our team](https://devportal.beefree.io/hc/en-us/requests/new) to learn more about the process.
