Migration of "Text", "Long text" and "Long text and summary" fields with both "Plain text" and "Filtered text" instances are now skipped

Conflicting text processing settings in Drupal 7

In Drupal 7, the text processing settings are defined on Field instance settings. In other words, the same field can be used on two (or more) content types and the text processing settings can be Plain text on one content type and Filtered text on another.

Drupal 8 has separate field storage types Text (plain) and Text (formatted). There's also Text (plain, long) and Text (formatted, long). The important part here is that this selection is done on field storage level. In other words, the plain / formatted selection can't be changed per content type. 

The migration system makes no assumptions. If the migration system detects conflicting text processing settings, these fields are skipped with a log message. The site builder has two options:

1. The text processing settings can be harmonized on Drupal 7 site so that all content types that use the text field have the same text processing setting.

• Pay attention when selecting which way to harmonize the processing settings to avoid possible cross site scripting (XSS) security issues. 
• If your field was set to Plain text in Drupal 7 and untrusted users were able to post content to this field, it is possible that the fields contain malicious input. This was not leading to an XSS on your Drupal 7 site because the field was set to Plain text and thus the malicious input was not executed. If you now change the field now to Filtered text, make sure that the Text format is not Full HTML or similar which would allow the malicious input.

2. If you need to have two different formatting settings in Drupal 8, you need to develop a custom migration which splits the Drupal 7 fields into two separate Drupal 8 fields.

Text with summary + plain text formatting setting in Drupal 7

Drupal 7 has a field type Long text and summary. The corresponding field type in Drupal 8 is Text (formatted, long, with summary). In Drupal 7 it is possible to configure on field instance settings that the text processing is Plain text. The Text (formatted, long, with summary) fields are always formatted text in Drupal 8.

The migration system makes no assumptions. If the migration system detects a Long text and summary field with Plain text formatting settings, the field is skipped with a log message. The site builder has the same two options as above:

1. Change the field formatting setting from Plain text to Filtered text in Drupal 7.

• The same remark described above about cross site scripting applies. 

2. Create a custom migration path and build your own logic how you want to migrate the fields to Drupal 8.