For example, you may want to upgrade from Nintex for SharePoint 2013 to Nintex for SharePoint 2016.
To prevent upgrade issues from third-party tools, read this first: Nintex Workflow Backup and Restore. Nintex requires that the destination environment (the environment you are migrating to) contains the same content as the source environment: GUIDs, content types and directory structure. Third-party tools can change this content, causing issues during upgrade.
The primary supported migration method for full content migration is the Database Attach method (see Nintex Workflow Backup and Restore). As long as that process is followed to a tee, all of your content should be migrated. Use the Database Attach method to ensure that running workflows continue. Any other method requires running workflows to cease during migration.
3) I am a Software Assurance customer, what migration licenses can I get?
All active Software Assurance customers are entitled to version migrations (e.g. Nintex Workflow 2010 to Nintex Workflow 2013) or server migrations within the same version (e.g. WFE101 moving to WFE202). Version migrations include Development licenses at no additional cost as long as the Software Assurance contract remains valid throughout the migration. Once the new version environment is complete on the development server, a 15 day temporary production license will be issued to complete the migration process. Nintex will decomision the previous server license once migration has been complete. All migrations requesting to run parellel production environments will be required to purchase additional production licenses.
4) Migrate to the next immediate version before migrating to the desired version.
Migrating directly from Nintex for SharePoint 2007 to Nintex for SharePoint 2013 / 2016/ 2019 is not supported. You must migrate to each succeeding version individually. For example, migrate Nintex for SharePoint 2007 to 2010, then to 2013, then to 2016. For more information, see Upgrading from Nintex Workflow 2007 to 2013 and Nintex for SharePoint 2016 Upgrade Guide.
If you're upgrading to claims authentication with your upgrade to Nintex for SharePoint 2013 or 2016, make sure you perform an upgrade to claims and confirm functionality before proceeding to the rest of the migration. For more information, see Claims based authentication for Nintex Workflow 2010 > 2013 migration and http://help.nintex.com/en-US/nintex2016/current/Default.htm#search-%22Upgrade%20web%20applications%2....
For SharePoint 2010, Microsoft recommends to convert SharePoint 2010 Products classic-mode web applications to claims-based authentication in SharePoint 2010 Products and then upgrade to SharePoint 2013. Additional information can be found in the following Microsoft article: http://technet.microsoft.com/en-us/library/gg251985(v=office.15).aspx.
If you wish to do your migration in stages, see Splitting existing SharePoint and Nintex Content Databases.
If upgrading to Nintex for SharePoint 2013 / 2016 / 2019, you may need to restart running workflows, such as workflows containing actions using credentials. We recommend testing your old designs in the new version of Nintex for SharePoint prior to migration.
Solved! Go to Solution.
The link to the external document "Nintex for SharePoint 2016 Upgrade Guide" refers to "http://help.nintextest.com/en-US/nintex2016/current/Default.htm#NW-Upgrade/aa-top-upgradeguide.htm" which is an internal domain for testing purposes and can't be reached from the Internet.
Thank you for alerting us of the broken link. The link is now updated as follows. http://help.nintex.com/en-US/nintex2016/current/Default.htm#cshid=upgradeguide
I am missing the information, about the best practice to migrate the both Nintex configuration databases (workflow and forms) from the old SP2013 to a new SP2016 farm. The SP2016 farm was build up from scratch, the SharePoint ContentDatabases are migrated via database attach method. Should the old Nintex Configuraton Databases be migrated, or it's better to use new configuration databases?
It is best to use existing Nintex databases. Oftentimes on the Nintex Workflow Configuration databases, there are site collections that have stored or store Workflow history. Besides that, Nintex Workflow Configuration database contains User Defined Actions, Workflow Constants and Workflow Schedules.
If you need more help on this, please feel free to open a case with Nintex Support.
We are planning to upgrade to SharePoint and Nintex Workflow 2016 from 2013 and currently have an upgrade testing lab where we installed a new SharePoint 2016 farm, I am facing some errors regarding Nintex Worfklow 2013 solutions and weparts during the Web application content database attach, we would like to know if we have to install Nintex Workflow 2013 first, to get rid of the errors, or if the errors will be solved just by installing Nintex Worfklow 2016
Also I would like to ask, if we use a new Nintex Workflow Configuration databases what will happen to the workflows we created in the 2013 environment, will they be available and work in the 2016 environment?
For SharePoint 2016, you will need to install Nintex Workflow 2016.
All workflows you create in Nintex 2013 will work on Nintex 2016 in SharePoint 2016.
If you need further help on this please let me know, or open a support case where I can also assist you.
Hi, We upgraded Nintex from for SharePoint 2013 and we ran issue with form are not loading, below are the details any help here: we upgraded Nintex Work flow from 3.0.8.03 to .2.5.0 and Nintex Forms from 184.108.40.206 to 220.127.116.11.
The error I can see as below: Object doesn't support property or method 'BubbleControlHeightChange'