diff --git a/docs/migrating/migrating_from_ez_publish_platform.md b/docs/migrating/migrating_from_ez_publish_platform.md
index 84f67f128e..1b5ead04af 100644
--- a/docs/migrating/migrating_from_ez_publish_platform.md
+++ b/docs/migrating/migrating_from_ez_publish_platform.md
@@ -362,6 +362,33 @@ When you are ready to migrate your eZ Publish XmlText content to the eZ Platform
 
 `php -d memory_limit=1536M bin/console ezxmltext:convert-to-richtext --export-dir=ezxmltext-export --export-dir-filter=notice,warning,error --concurrency 4 -v`
 
+**Custom tags**
+
+eZ Platform now supports custom tags, (including inline custom tags), and limited use of custom tag attributes.
+After migration to richtext, you'll need to adapt your custom tag config for eZ Platform and rewrite the custom tags in twig
+
+See [eZ Platform custom tag documentation](https://doc.ezplatform.com/en/latest/guide/extending/extending_online_editor/#custom-tags) for more info.
+If you in legacy as configured custom attributes in OE using [ezoe_attributes.ini](https://github.com/ezsystems/ezpublish-legacy/blob/master/extension/ezoe/settings/ezoe_attributes.ini#L33-L48), please note that not all types are supported.
+Below is a table of what is currently supported, and their corresponding name in eZ Platform.
+
+| [XmlText](https://github.com/ezsystems/ezpublish-legacy/blob/2019.03/extension/ezoe/settings/ezoe_attributes.ini#L33-L48)        | [RichText](https://github.com/ezsystems/ezplatform-richtext/blob/master/src/bundle/DependencyInjection/Configuration.php#L17)           | Note  |
+| ------------- | ------------- | :-----: |
+| `link`        | `link`        |  Treated as a string, no special UI provided by eZ Platform editor |
+| `number`      | `number`      |  |
+| `int`         | `number`      |  |
+| `checkbox`    | `boolean`     |  |
+| `select`      | `choice`      |  |
+| `text`        | `string`      |  |
+| `textarea`    | Not supported |   Use `string` as workaround |
+| `email`       | Not supported |   Use `string` as workaround |
+| `hidden`      | Not supported |   Use `string` as workaround |
+| `color`       | Not supported |   Use `string` as workaround |
+| `htmlsize`    | Not supported |   Use `string` as workaround |
+| `csssize`     | Not supported |   Use `string` as workaround |
+| `csssize4`    | Not supported |   Use `string` as workaround |
+| `cssborder`   | Not supported |   Use `string` as workaround |
+
+
 ###### 3.2.2 Migrate Page field to Page (eZ Enterprise only)
 
 **If** you use Page field (ezflow) and an eZ Enterprise subscription, and are ready to migrate your eZ Publish Flow content to the eZ Enterprise Page format, you can use a script to migrate your old Page content to new Page, to start using a pure eZ Enterprise setup. See [Migrating legacy Page field (ezflow) to new Page (Enterprise)](#migrating-legacy-page-field-ezflow-to-new-page-enterprise) for more information.