Home > SharePoint Online Migration > Migration to SharePoint Online > Supported and Unsupported Nintex Forms
Export to PDFSupported and Unsupported Nintex Forms
Refer to the table below to view the supported details of Nintex forms in SharePoint Online to to SharePoint Online Migration.
√ – Supported; × – Unsupported
| Object Type | Object Type | Object Type | Support Status | Comment |
|---|---|---|---|---|
| Classic designer | General | Border | √ | |
| Classic designer | General | Button | √ | |
| Classic designer | General | Calculated value | √ | |
| Classic designer | General | Choice | √ | |
| Classic designer | General | Date/Time | √ | |
| Classic designer | General | Geolocation | √ | |
| Classic designer | General | Hyperlink | √ | |
| Classic designer | General | Image | √ | |
| Classic designer | General | Label | √ | |
| Classic designer | General | Multiple line textbox | √ | |
| Classic designer | General | Page break guide | √ | |
| Classic designer | General | Page viewer | √ | |
| Classic designer | General | Panel | √ | |
| Classic designer | General | People | Partially Supported | If there are no user mappings configured for the source users, source users configured in the People control cannot be replaced with destination users. |
| Classic designer | General | Repeating section | √ | |
| Classic designer | General | Rich text | √ | |
| Classic designer | General | Single line textbox | √ | |
| Classic designer | SharePoint | List lookup | √ | Make sure the list where the Nintex form resides and the list that is associated via the List lookup control are migrated in one plan mapping. |
| Classic designer | SharePoint | Managed metadata | Partially Supported | Data related to the managed metadata control in the Classic designer cannot be migrated. |
| Classic designer | List columns | Title | √ | |
| Classic designer | List columns | Attachments | √ | |
| Classic designer | List columns | Name | √ | |
| Classic designer | List columns | Multiple lines of text | √ | |
| Classic designer | List columns | Choice | √ | |
| Classic designer | List columns | Number | √ | |
| Classic designer | List columns | Currency | √ | |
| Classic designer | List columns | Date and time | √ | |
| Classic designer | List columns | Lookup | √ | |
| Classic designer | List columns | Yes/No | √ | |
| Classic designer | List columns | Person or group | √ | |
| Classic designer | List columns | Hyperlink or picture | √ | |
| Classic designer | List columns | External data | × | |
| Classic designer | List columns | Task outcome | √ | |
| Classic designer | List columns | Managed metadata | √ | |
| Responsive designer | General | Button | √ | |
| Responsive designer | General | Calculated value | √ | |
| Responsive designer | General | Choice | √ | |
| Responsive designer | General | Date/Time | √ | |
| Responsive designer | General | Geolocation | √ | |
| Responsive designer | General | Hyperlink | √ | |
| Responsive designer | General | Image | √ | |
| Responsive designer | General | Label | √ | |
| Responsive designer | General | Multiple line textbox | √ | |
| Responsive designer | General | Page break guide | √ | |
| Responsive designer | General | Panel | √ | |
| Responsive designer | General | People | Partially Supported | If there are no user mappings configured for the source users, source users configured in the People control cannot be replaced with destination users. |
| Responsive designer | General | Repeating section | √ | |
| Responsive designer | General | Rich text | √ | |
| Responsive designer | General | Single line textbox | √ | |
| Responsive designer | General | Yes/No | √ | |
| Responsive designer | SharePoint | List lookup | √ | Make sure the list where the Nintex form resides and the list that is associated via the List lookup control are migrated in one plan mapping. |
| Responsive designer | SharePoint | Managed metadata | Partially Supported | Data related to the managed metadata control in the Responsive designer cannot be migrated. |
| Responsive designer | List columns | Title | √ | |
| Responsive designer | List columns | Attachments | √ | |
| Responsive designer | List columns | Name | √ | |
| Responsive designer | List columns | Multiple lines of text | √ | |
| Responsive designer | List columns | Choice | √ | |
| Responsive designer | List columns | Number | √ | |
| Responsive designer | List columns | Currency | √ | |
| Responsive designer | List columns | Date and time | √ | |
| Responsive designer | List columns | Lookup | √ | |
| Responsive designer | List columns | Yes/No | √ | |
| Responsive designer | List columns | Person or group | √ | |
| Responsive designer | List columns | Hyperlink or picture | √ | |
| Responsive designer | List columns | Task outcome | √ | |
| Responsive designer | List columns | External data | × | |
| Responsive designer | List columns | Managed metadata | √ | |
| New Responsive designer | New Responsive designer | New Responsive designer | × |
*Note: Nintex forms that are not published cannot be migrated.
*Note: The versions, created time, and Create by users of Nintex forms cannot be migrated to the destination.
*Note: After a Nintex form is migrated to the destination, if the Nintex form is updated in the source and is migrated to the destination again, you need to manually publish the Nintex form in the destination to ensure that the updated source settings can overwrite the destination form settings.
On this page