cancel
Showing results for 
Search instead for 
Did you mean: 
johnramos
Nintex Newbie

Nintex Workflow "Split" Upgrade

I am working on upgrading a SharePoint 2010 environment to SharePoint 2013, however, the upgrade is going to be done in stages - X amount of sites at a time - instead of all at once.  In that kind of situation, what is the best way to handle moving sites with Nintex Workflow activated?  Currently, all SP content databases are directed to use whatever workflow DB is available (there is only one at this time).  Would it be better to explicitly map all SP content databases to the current Nintex database and then when they are due to be moved/upgraded to the SP 2013 farm, map them to their own Nintex database for the upgrade? Any suggestions/help would be greatly appreciated.

 

Thank you!

Labels: (1)
0 Kudos
Reply