cancel
Showing results for 
Search instead for 
Did you mean: 

Migrating Nintex Workflow: A High-Level Overview for SharePoint On-Premises

Identify Source and Destination Environments.  

 

  • Taking note of your current SharePoint Environment and where you intend to migrate to will help you identify any special requirements or considerations. 

 

 Identify Migration Method 

 

  • Database Attach Method (as defined by Microsoft) 
    • Nintex Workflow and Forms databases are migrated alongside SharePoint. 
    • A sequential upgrade as there is no direct upgrade path between SharePoint versions. 
    • Requires more effort but is the most thorough. 
    • More information from Microsoft can be found here: 

https://docs.microsoft.com/en-us/SharePoint/upgrade-and-update/upgrade-and-update 

 

 

Database Attach Method Overview with Nintex Workflow 

 

SharePoint 2010 to SharePoint 2013  

 

  1. Preparing SharePoint 2010 
    1. Upgrade Nintex Workflow and Forms 2010 to their latest releases. 
      • Ensure that Nintex Databases are upgraded during this process. 
    2. Stop the SharePoint Timer Service and IIS on all servers. 
      • This prevents any workflows from writing new data to the Nintex Databases 
    3. Backup Nintex Databases using SQL Server Management Studio 
  2. Arriving in SharePoint 2013 (Nintex Workflow 2010 to 2013 Upgrade Guide) 
    1. Ensure that the SharePoint 2013 installation and configuration are complete. 
      • Web Applications that will host your migrated content have been created. 
      • Migrated SharePoint Content Databases have not yet attached. 
    2. Disable the Workflow Timer Job
    3. Install Nintex Workflow and Forms for SharePoint 2013 
    4. Disable the Nintex Workflow Scheduler 
    5. Stop the SharePoint Timer Service on all Servers 
    6. Attach SharePoint Content Databases 
    7. Restore Nintex Databases in SQL Server Management Studio 
    8. Execute “_PrepareForNewEnvironment” stored procedure on Nintex Configuration Database. 
      • This stored procedure deletes database mappings and references that were used in the previous environment. 
    9. Add existing Nintex Configuration Database in Central Administration. 
    10. Add existing Nintex Content Databases in Central Administration or by using NWAdmin AttachDatabase command 

Note: If any Web Applications are migrated from Classic to Claims-Based Authentication as per Microsoft’s guidance, please see additional steps for Nintex Workflow:

 

Migrate Nintex Workflow to Claims-based authentication 

https://help.nintex.com/en-US/nintex2019/current/#sp2019/NWSetup/ClaimsAuth.htm?Highlight=claims 

 

SharePoint 2013 to SharePoint 2016 

  

  1. Preparing SharePoint 2013 
    1. Upgrade Nintex Workflow and Forms 2013 to their latest releases. 
      • Ensure that Nintex Databases are upgraded during this process. 
    2. Stop the SharePoint Timer Service and IIS on all servers. 
      • This prevents any workflows from writing new data to the Nintex Databases 
    3. Backup Nintex Databases using SQL Server Management Studio 
  2. Arriving in SharePoint 2016 (Nintex for SharePoint 2016 Upgrade Guide) 
    1. Ensure that the SharePoint 2016 installation and configuration is complete. 
      • Web Applications that will host your migrated content have been created. 
      • Migrated SharePoint Content Databases have not yet attached. 
    2. Disable the Workflow Timer Job 
    3. Install Nintex for SharePoint 2016 
    4. Disable the Nintex Workflow Scheduler 
    5. Stop the SharePoint Timer Service on all Servers 
    6. Attach SharePoint Content Databases 
    7. Restore Nintex Databases in SQL Server Management Studio 
    8. Execute “_PrepareForNewEnvironment” stored procedure on Nintex Configuration Database. 
      • This stored procedure deletes database mappings and references that were used in the previous environment. 
    9. Add existing Nintex Configuration Database in Central Administration. 
    10. Add existing Nintex Content Databases in Central Administration or by using NWAdmin -AttachDatabase command 

 

SharePoint 2016 to SharePoint 2019 

 

  1. Preparing SharePoint 2016 
    1. Upgrade Nintex for SharePoint 2016 to the latest release. 
      • Ensure that Nintex Databases are upgraded during this process. 
    2. Stop the SharePoint Timer Service and IIS on all servers. 
      • This prevents any workflows from writing new data to the Nintex Databases 
    3. Backup Nintex Databases using SQL Server Management Studio 
  2. Arriving in SharePoint 2019 (Nintex for SharePoint 2019 Upgrade Guide) 
    1. Ensure that the SharePoint 2019 installation and configuration are complete. 
      • Web Applications that will host your migrated content have been created. 
      • Migrated SharePoint Content Databases have not yet attached. 
    2. Disable the Workflow Timer Job 
    3. Install Nintex for SharePoint 2019 
    4. Disable the Nintex Workflow Scheduler 
    5. Stop the SharePoint Timer Service on all Servers 
    6. Attach SharePoint Content Databases 
    7. Restore Nintex Databases in SQL Server Management Studio 
    8. Execute “_PrepareForNewEnvironment” stored procedure on Nintex Configuration Database. 
      • This stored procedure deletes database mappings and references that were used in the previous environment. 
    9. Add existing Nintex Configuration Database in Central Administration. 
    10. Add existing Nintex Content Databases in Central Administration or by using NWAdmin -AttachDatabase command

 

Note: If any Web Applications are migrated from Classic to Claims-Based Authentication as per Microsoft’s guidance, please see additional steps for Nintex Workflow:

 

Migrate Nintex Workflow to Claims-based authentication 

https://help.nintex.com/en-US/nintex2019/current/#sp2019/NWSetup/ClaimsAuth.htm?Highlight=claims 

 

Post-Migration

 

Restart the following Timer Jobs and Services 

  • Workflow Timer job 
  • Nintex Workflow Scheduler job 
  • SharePoint Timer Service 

 

Test Functionality 

  • Nintex Workflow Inventory 
    • Ensure that this page opens properly 
    • Ensure that workflows are not missing 
  • Schedule a Nintex Workflow 
    • Ensure that the workflow starts on time 
  • Publish and Execute a Workflow with a Pause and Flexi Task 
    • Workflow should publish without any error 
    • Workflow should successfully enter and enter the Pause 
    • Workflow should enter and exit task successfully upon Task Outcome (Approve/Reject) 

 

Additional Resources:

 

Help Documentation:

 

Nintex Workflow 2010 to 2013 Upgrade Guide 

Upgrade to Nintex for SharePoint 2016 

Upgrade to Nintex for SharePoint 2019  

Labels: (1)
Version history
Revision #:
3 of 3
Last update:
3 weeks ago
Updated by:
 
Contributors