Frequently asked questions
This section provides answers to frequency asked questions about the upgrade process and gives easy access to important links.
Nintex Workflow only supports upgrades from the most recent version of Nintex Workflow for SharePoint. To upgrade from an older version you must first perform an intermediary update. Nintex Workflow 2019 only supports upgrades from Nintex Workflow 2016. To upgrade from Nintex Workflow 2010, you must first perform an upgrade to Nintex Workflow 2013 and then To Nintex for SharePoint 2016.
The primary supported migration method for full content migration is the Database Attach method. Use the Database Attach method to ensure that running workflows continue. Any other method requires running workflows to cease during migration. For more information, see Introduction.
All active Software Assurance customers are entitled to version migrations (For example, upgrading from Nintex Workflow 2016 to Nintex Workflow 2019) or server migrations within the same version (For example, 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 process. 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 is completed. All migrations requesting to run parallel production environments will require the purchase of additional production licenses.
To check if you have a valid Software Assurance contract in place, navigate to SharePoint Central Administration, open the Nintex Workflow Management section, click on Licensing and check the expiry date of the Software Assurance or Premium Support. If the Software Assurance or Premium Support has not expired, you can perform the update.
If you wish to do your migration in stages and want to split databases, see Split databases for instructions.
When you perform an upgrade, changes are usually made to the database schema. Due to the database schema changes done, there is no easy rollback method that we can recommend or support.
Product upgrade will not remove any existing workflows and forms from your SharePoint environment.
Note: If you upgrade Nintex Forms and you have any custom controls and JavaScript which have been configured in your environment, we recommend testing them after you do the upgrade to ensure they have not been affected as functionality may have changed.