cancel
Showing results for 
Search instead for 
Did you mean: 

On-Prem Migration Frequently Asked Questions

 
Can we migrate directly from an old version of Sharepoint 2010 to Sharepoint 2019?

There have been many changes since the initial 2010 product release. Nintex recommends updating the 2010 environment to the latest and then migrate to 2013 -> 2016 ->2019. For instructions on upgrading to the latest version of Nintex Workflow 2010 refer to 

Nintex Workflow 2010 - Product Update Process

 

Can we do a partial migration of the farm to a later version? (Ex. A farm with 200 Site Collections, but only 100 will be moved)

Yes, migrations can be completed in stages. Much of this process is Sharepoint specific. For details on the Nintex process, please refer to the Site Collection Backup / Restore Method:  Nintex Workflow Backup and Restore 

 

Can we migrate without updating the Nintex Product version in production?

Yes, this can be done. However, Nintex recommends being on the latest build. Please check the product update guide for the Nintex Version you are currently on and the destination one (2010,2013,2016,2019) if there are any pre-requisites to update to the latest builds.  

 

Can we connect 2 different farms hosting Nintex to one SQL Instance? 

Two farms can be connected, however it is important the Nintex databases have different names. If you are using SQL Alias, make sure they are pointed correctly.  

 

Is it mandatory to move the Nintex configuration database while doing test migrations?  

It is important to take a copy of the Nintex configuration database and update the test environment. The Nintex configuration database has references to multiple pieces of workflow information.  

 

Do the workflows need to be stopped prior to migrating?  

For a production migration, you need to stop the SharePoint timer service prior to migration. For a test migration, you can take a backup of the content databases and then move it.  

 

Can we do an out of place migration?  

The Forms database has historic information for Mobile forms and Live forms. If you are not using external forms, you can skip the migration and create a new database 

 

What version of SQL is compatible with Nintex Workflow? 

Please refer to the release notes for the Nintex workflow product version you are referring to.  

For example, for 2019 refer to product release notes for Nintex workflow 2019:   

Nintex for SharePoint 2019 Release Notes 

 

How does the migration affect Nintex Live / External (forms/workflows)? 

During the Migration Live / External, it is important to stop workflow or forms, the ongoing requests will be queued and resume after the migration.  

 

Do we have to execute the PrepareForNewEnvironment stored procedure, and at what point do we run it? 

This should be run on the environment after the configuration database has been restored and before attaching the Configuration database in the environment 

 

What is the recommended approach to migrate User Defined Actions? 

If the configuration database is not migrated, you would need to manually export and import them into the farm.  

 

What is stored in Nintex Forms Database? 

Nintex forms database is necessary to use Nintex Forms for on-prem forms. XML for Nintex forms is stored in the Sharepoint Content databases. Nintex Live forms and Nintex Mobile forms historic information is stored in the Nintex Forms database.  

 

How to migrate Workflow Constants? 

Please refer to this article on how to Migrate Workflow Constants:

 Nintex Workflow Migrating Constants

Labels: (2)
Version history
Revision #:
4 of 4
Last update:
‎08-11-2020 08:53 AM
Updated by:
 
Contributors