Future of Nintex O365 Forms: Migrating from Add-ins to SPFx
Introduction
We're excited to announce that as of today, our Nintex Forms for Office 365 customers can now publish and use forms in either the Nintex Forms add-in or the Nintex Automation Cloud SPFx apps. For those who aren't already aware, Microsoft is moving away from add-in apps, and you'll need to transition to SPFx apps. For more details, check out this link. This important feature follows the completion of the final features for our Form Upgrade tooling, which helps customers upgrade to New Responsive forms. This is the next crucial step in this transition.
Open the New App and you should see "Customize SharePoint list forms" as an option. Click on that.
If it is your first time opening List Forms in SPFx, you will also need to grant consent for the app, so each user doesn’t need to login. This will need to be an Admin who has permissions to grant consent.
If you already have a New Responsive Form published on the list, you will see it as a draft for review.
Publish this form, and you've successfully moved the form to SPFx.
What's Next?
You might be wondering, "That's great for one form, but how do I move all my forms?"
Rest assured, this isn't the end of our assistance in helping customers and their forms migrate to SPFx. We're currently working on finishing the remaining parity features to ensure we provide the functionality you're used to and more. We're also developing scripts to assist with bulk movement, such as bulk republishing and identifying form locations, versions, and the app they're currently using. This will help streamline the migration process. Keep an eye out for another post later this quarter when these tools become available to help customers with bulk migration.
FAQ
If you have any additional questions not listed, please respond to this post and we will get it answered and added to the FAQ.
What if the form on the list is a responsive or classic Form?
You will not see legacy forms in the new SPFx app. The recommendation is to upgrade the Form in the add-in app before moving to SPFx.
Alternatively, you can import a legacy form definition directly into the New Responsive designer.
What if I use multiple content types?
Each content type is treated separately, so you can have one published in the old and one in the new app.
You will only see new responsive published forms in SPFx. So, you will need to upgrade the Form in the old add-in app before you will see a form for that content type in the new app.
What about if I don’t have the add-in and we are going straight to SPFx?
You can import your old classic or old responsive forms directly into the designer to upgrade these forms
Can I remove the old app after upgrading and publishing in SPFx?
Yes, however you will not be able to rollback after removing the old app and would be recommended you complete your testing before removing the old app.
From the sharepoint list missing clicking on the Nintex button on the command bar first, then clicking on ‘Customize SharePoint list form’
Also the first time I accessed this I had to consent a new application in Entra for ‘Nintex Forms for SharePoint Lists’. I could find this app consent referenced in the install documentation pages.
@Gavin-Adams Thanks for the feedback.
The help was updated to add a note about needing to grant consent on first use for Forms. Just let us know if you have any further feedback or this is unclear after the update.
Hello. So I’m a bit confused on item #4.
What does this mean exactly? We have tons of new responsive forms in Nintex Forms for Office 365 application. Are you saying we still have to open and “republish” the form in the new SPFx app?
@brandiwoodson We will be looking to provide a script to enable customers to bulk republish but at this stage it would be manual republish if you want to have that existing Form in SPFx.
Hi, like @brandiwoodson I’m also confused by #4. Specific example: I’m going into a list that has a new responsive form last modified 8/26/2024. Via the new app I click on “Customize SharePoint list forms” and the form just loaded up, there is no “you will see it as a draft for review”. Does that mean everything is all set with it? Is there some subset of new responsive forms we will have to republish using the new app? Put another way: Do we have to do anything with forms that have always been new responsive?
I also have the following questions:
1) Will legacy forms stop working completely after this transition in 2026 or will we just lose the ability to modify/design them?
2) Will links to old forms break? I'd assume old links to legacy forms will break once upgraded? Will any links break with new responsive forms created in the old app? Any other link breaking stuff to be concerned about?
3) Legacy forms could be embedded into SharePoint pages via the Nintex webpart. As far as I know that was never possible with new responsive. Any thoughts on the best way to replace that aspect of legacy forms?
4) Is it possible to turn off the ability to create new legacy forms via the old app while retaining the ability to modify them during the migration period?
Thanks so much!
@rossk All new responsive forms will need to be published to move them to SPFx, as they would be referencing the odd app and would stop working once the old app goes away unless they are republished.
They will stop working completely.
Links will break if you are using a direct link to the form url. If you use newitem.aspx link for the SharePoint list it will not break, as it generic and will work regardless of the form in use.
At this point it would be a feature request(https://ideas.nintex.com/), or the other alternative would be using an NAC form which can be embedded.
Not at this stage, we looking at options to restrict creating old forms in future release.
Please let us know if you have any additional questions or need further clarification.
Thanks @leighburke! Is there a way to see which new responsive forms in our environment have been republished and are currently using the new app? I thought it might be here: https://analytics.nintexcloud.com/analytics/forms, but when I go there the Form type column is empty for all of our forms.
Thanks again.
Thanks @leighburke! Is there a way to see which new responsive forms in our environment have been republished and are currently using the new app? I thought it might be here: https://analytics.nintexcloud.com/analytics/forms, but when I go there the Form type column is empty for all of our forms.
Thanks again.
I put alot of thought into this. Best approach we have come up with is going through ALL forms and manually publishing them in the new app, then uninstalling nintex forms apps once we have done this on all the forms on that site, so users can't go back it the old app and republish.
For us, it's challenging cause we can't uninstall apps until we add the site to our exception list for retention policy. We will have an extra step prior to doing anything per site.
For us we can only do this for sites that ONLY have forms in new responsive. We would have to wait for the responsive and classic forms to be rebuilt by the owners before messing with those sites.
Id love to hear a better or alternative approach so following this thread.
@leighburke i assume if a form is republished in new spfx app, then later a new version is published later in old app by a user on accident or lack of understanding of the apps, that we will lose the last version after april 2026?
If so, i assume uninstalling of old app is best practice after republishing a version in the new app?
Thanks @leighburke! Is there a way to see which new responsive forms in our environment have been republished and are currently using the new app? I thought it might be here: https://analytics.nintexcloud.com/analytics/forms, but when I go there the Form type column is empty for all of our forms.
Thanks again.
@rossk We have a PowerShell script we will be providing along with some instructions that can tell if a form was published in the old or new app and can be run against your tenant. Targeted for either the end of December or early January. I will link on here when this is available.
@leighburke i assume if a form is republished in new spfx app, then later a new version is published later in old app by a user on accident or lack of understanding of the apps, that we will lose the last version after april 2026?
If so, i assume uninstalling of old app is best practice after republishing a version in the new app?
@brandiwoodson Correct, I would recommend removing the old app from sites if no longer needed. We have also had some requests to restrict publishing of legacies forms, so would be interested if you have any feedback on this as well.
@leighburke i assume if a form is republished in new spfx app, then later a new version is published later in old app by a user on accident or lack of understanding of the apps, that we will lose the last version after april 2026?
If so, i assume uninstalling of old app is best practice after republishing a version in the new app?
@brandiwoodson Correct, I would recommend removing the old app from sites if no longer needed. We have also had some requests to restrict publishing of legacies forms, so would be interested if you have any feedback on this as well.
Honestly that would be ideal. Force owners to republish when they can't publish in the old one. Maybe provide more details to them to republish in the new app or contact an administrator for help.
Thanks @leighburke! Is there a way to see which new responsive forms in our environment have been republished and are currently using the new app? I thought it might be here: https://analytics.nintexcloud.com/analytics/forms, but when I go there the Form type column is empty for all of our forms.
Thanks again.
@leighburke Can you look into what @rossk mentioned above with empty form type? Or am I missing something that changed that now requires a script to pull this information that was easily accessible through Insights before?
Our report is EMPTY as well, as of this morning. I pull reporting monthly and save them to our team site. Last months was ran on 11/16/24. So, something has happened since then with reporting.
Report from 11/16/24:
Report from today:
Here is the ticket I just created for this bug. 00667977
@brandiwoodson Thanks for raising the bug, it should be showing the forms types there. The script is because it won’t differentiate between a new responsive in the old app and new app in Insights. Also not all customers have Insights.
@rossk If possible can you raise it as well and the Insights team will be able to investigate.
@brandiwoodson Thanks for raising the bug, it should be showing the forms types there. The script is because it won’t differentiate between a new responsive in the old app and new app in Insights. Also not all customers have Insights.
@rossk If possible can you raise it as well and the Insights team will be able to investigate.
Checked this morning and it’s back now.
Thanks @leighburke! Is there a way to see which new responsive forms in our environment have been republished and are currently using the new app? I thought it might be here: https://analytics.nintexcloud.com/analytics/forms, but when I go there the Form type column is empty for all of our forms.
Thanks again.
@rossk We have a PowerShell script we will be providing along with some instructions that can tell if a form was published in the old or new app and can be run against your tenant. Targeted for either the end of December or early January. I will link on here when this is available.
Is there an updated timeline of when the PowerShell script will be available? Thanks! Keith
@KeithKoerner Sorry for the delay, the scripts will be available this month. Just finalising a couple of things and we will look to make them available.
Hi @leighburke Do you have some new on this script ?
@nico Sorry again for the delay, the scripts are ready, just finalising the documentation and then I will make them available.
Introduction
We're excited to announce that as of today, our Nintex Forms for Office 365 customers can now publish and use forms in either the Nintex Forms add-in or the Nintex Automation Cloud SPFx apps. For those who aren't already aware, Microsoft is moving away from add-in apps, and you'll need to transition to SPFx apps. For more details, check out this link. This important feature follows the completion of the final features for our Form Upgrade tooling, which helps customers upgrade to New Responsive forms. This is the next crucial step in this transition.
Open the New App and you should see "Customize SharePoint list forms" as an option. Click on that.
If it is your first time opening List Forms in SPFx, you will also need to grant consent for the app, so each user doesn’t need to login. This will need to be an Admin who has permissions to grant consent.
If you already have a New Responsive Form published on the list, you will see it as a draft for review.
Publish this form, and you've successfully moved the form to SPFx.
What's Next?
You might be wondering, "That's great for one form, but how do I move all my forms?"
Rest assured, this isn't the end of our assistance in helping customers and their forms migrate to SPFx. We're currently working on finishing the remaining parity features to ensure we provide the functionality you're used to and more. We're also developing scripts to assist with bulk movement, such as bulk republishing and identifying form locations, versions, and the app they're currently using. This will help streamline the migration process. Keep an eye out for another post later this quarter when these tools become available to help customers with bulk migration.
FAQ
If you have any additional questions not listed, please respond to this post and we will get it answered and added to the FAQ.
What if the form on the list is a responsive or classic Form?
You will not see legacy forms in the new SPFx app. The recommendation is to upgrade the Form in the add-in app before moving to SPFx.
Alternatively, you can import a legacy form definition directly into the New Responsive designer.
What if I use multiple content types?
Each content type is treated separately, so you can have one published in the old and one in the new app.
You will only see new responsive published forms in SPFx. So, you will need to upgrade the Form in the old add-in app before you will see a form for that content type in the new app.
What about if I don’t have the add-in and we are going straight to SPFx?
You can import your old classic or old responsive forms directly into the designer to upgrade these forms
Can I remove the old app after upgrading and publishing in SPFx?
Yes, however you will not be able to rollback after removing the old app and would be recommended you complete your testing before removing the old app.
How do we do this? I’m wondering if this is why some of our external users can’t login.
Is it something to do with Site collection app permissions? If so, how do we grant permission?
@brandiwoodson No it is not using site permissions, it uses an Enterprise Application. If you check in Azure you should be able to see the List Forms app if it has already been added.
@brandiwoodson No it is not using site permissions, it uses an Enterprise Application. If you check in Azure you should be able to see the List Forms app if it has already been added.
Is it this one?
@brandiwoodson No it is not using site permissions, it uses an Enterprise Application. If you check in Azure you should be able to see the List Forms app if it has already been added.
Is it this one?
And just to be clear on the help documentation, users should not have to login to load a form (new, edit or display mode) if we properly granted consent, correct? Regardless of if they are member or guest in our tenant, is that correct? We are experiencing issues with guest users going to a site (logging in) and then when attempting to click new or view an item in a list - they are then re-prompted to login again through “sign-in options” that is available.
@brandiwoodson Correct, there was an issue identified with guest/external user which are working on resolving. If you have raised a ticket they will be able to keep you in the loop on it’s release.
