When migrating from Nintex Workflow 2007 to Nintex Workflow 2010, we recommend running the Pre-upgrade Check tool, to identify any workflows which may have an issue when upgrading to Nintex Workflow 2010 and SharePoint 2010. The Pre Update Check tool is attached to this article.
Please read the Loop disabled in SharePoint 2010 article for more background on the issue with upgrading workflows.
The tool scans the Nintex Workflow databases and the SharePoint sites to check for a workflow that contains an obsolete activity. A report file called NWUpgradeReport.html is created in the same directory as the tool executable.
NW2007ToNW2010PreUpgradeCheck.exe [-verbose] [-grid]
Both parameters are optional and can be specified in any order:
If the tool is unable to access a site or list, this option will show details of the error in the report. If this option is not specified, access errors are skipped over
When this option is specified, the output is formatted as a grid which can be opened in Excel.
The upgrade tool needs access to all sites and lists in SharePoint to check the workflow data. Therefore it is strongly recommended that the tool is run as the farm service account.
The default output format lists each workflow that will have an issue after upgrading.
The information section outlines what causes this workflow to be marked as an upgrade problem. The above explanation contains:
If any workflows contains obsolete actions and is currently set to allow new instances, the workflow must be republished in Nintex Workflow 2007 build 11002 or later.
If any currently running workflow instance contains an obsolete activity then either the workaround described in the “Loop disabled in SharePoint 2010” must be implemented or an upgrade should not happen until running instances with the obsolete actions have completed (and therefore any running instances have been started since republishing the workflow in 11002 or later).