Considerations for Migrating or Upgrading Nintex for SharePoint
What considerations should be made when upgrading to a later version of Nintex for SharePoint?
Ensure the destination environment has the same content.
To prevent upgrade issues from third-party tools, read this first:Nintex Workflow Backup and Restore. Nintex requires that the destination environment contain the same content as the source environment: GUIDs, content types and directory structure. Third-party tools can change this content, causing issues during upgrade.
Use the Database Attach method for migration.
The primary supported migration method for full content migration is the Database Attach method. For more information, seeNintex Workflow Backup and Restore. This method ensures migration of all content and ensures that running workflows continue. Any other method requires running workflows to cease during migration.
Migrate to the next immediate version before migrating to the desired version.
Restart workflows containing actions that use credentials.
If upgrading to Nintex for SharePoint 2013 or 2016, it might be necessary to restart running workflows, such as workflows containing actions using credentials. Test old designs in the new version of Nintex for SharePoint prior to migration.
Run NWAdmin commands using the command prompt.
NWAdmin commands must be run in the command prompt. NWAdmin comments are not PowerShell friendly. For more information about NWAdmin, see the NWAdmin Guide (2016|2013|2010).