Learn what you need to know when upgrading to a later version of Nintex for SharePoint.
For example, you may want to upgrade from Nintex for SharePoint 2013 to Nintex for SharePoint 2016.
1) Make sure the destination environment has the same content. Are you using third-party tools?
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.
2) Use the Database Attach method for migration.
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) Migrate to the next immediate version before migrating to the desired version.
Migrating directly from Nintex for SharePoint 2007 to Nintex for SharePoint 2013 or 2016 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.
4) Upgrade to claims authentication (optional).
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.nintextest.com/en-US/nintex2016/current/Default.htm#search-%22Upgrade%20web%20applications%20to%20claims%20authentication%22.
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.
5) Considering running your migration in stages.
If you wish to do your migration in stages, see Splitting existing SharePoint and Nintex Content Databases.
6) Restart workflows containing actions that use credentials.
If upgrading to Nintex for SharePoint 2013 or 2016, 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.
7) Run NWAdmin commands using the command prompt.
Nintex for SharePoint 2016
Nintex Workflow for SharePoint (2013/2010/2007)
Nintex Forms for SharePoint 2013 upgrade