Back
Step 1: Migration Overview
What’s New?
We have introduced two new field types — Markdown and Rich Text (v2) — to store rich text content in Yext. These new field types are more powerful than Legacy Rich Text, offer a wider array of support, and are more transparent to debug.
We have also introduced the Fork Fields flow in Yext Content to migrate your existing Legacy Rich Text fields over to one of the new field types.
Any existing Legacy Rich Text fields will still exist in Content, and can still be edited manually as well as read and wrote to by any integrations. However, you can no longer create new Legacy Rich Text fields.
What Do I Need to Do?
We recommend all users migrate (or “fork”) their Legacy Rich Text fields and field types over to either the Markdown or Rich Text (v2) field type. This can be done using the Fork Fields flow in Yext Content.
The whole process, outlined in this guide, involves:
- Forking any custom field types using Legacy Rich Text to a new type
- Forking any custom Legacy Rich Text fields to a new type
- Updating any references to your Legacy Rich Text fields in Pages, Search, or other integrations
Forking only needs to be done for existing fields. We have shifted all new fields and field types to the Markdown or Rich Text (v2) field type, and Legacy Rich Text is no longer available as a type to create any new fields moving forward.
Keep following along to learn more specifics about the Rich Text (v2) and Markdown field types, and how to fork your existing Legacy Rich Text fields and field types.