Hi Tom,

take a look at this document Splitting SharePoint and Nintex Databases and also Nintex Workflow Backup and Restore.

You can have a NW content database per site collection, like you can with SP Content Databases.

Then, it's easier to move one or a few site collections at a time from 2010 to 2013.

The steps to split a single NW content/configuration database, into multiple content database is quite straightforward and will make it easier to do bit by bit migration.

cheers,

Vadim

Thanks so much for your response, Vadim!  I am pretty clear on splitting out the Nintex content by site collection and remapping the databases.  Where I was a bit unsure was specifically with the Nintex configuration db.  Rereading some of the linked articles which I've been working with, the situation seems a bit more clear.  Maybe you can tell me if this is a true statement.  When I first begin migrating to the Dev 2013 farm and bring over and upgrade the Nintex 2010 configuration database, that obviously becomes the new configuration database in 2013.  The important bit I think, is that at that point, I am all set with my Nintex Workflow 2013 configuration database.  Is that accurate?  I can then move forward with bringing over the 1 to 1 matched SharePoint and Nintex content dbs over the following days or weeks without concern about the configuration database?

Thanks again for your help,

Tom,

You are correct.  The Nintex config DB is farm specific, not content db specific.  Therefore you will have a config database for each farm both 2010 and 2013.  You will also need a separate license for each farm as well so I would ensure that is planned out well.

I would first work to get that established and get Nintex working then migrate a web app, content database and nintex db.  This should bring over and update all the proper mappings for that content.  The content in this case will be mapped to the content database and the nintex database simply retains the workflow information pertinent to that content.

You can then repeat this for each content database and nintex database as you desire.

Hope that helps.

Thanks so much Ed; I appreciate you taking the time to respond and confirm.  We do have a NIntex Development license for our development farm and will be sure to have our production licensing needs planned with Nintex well before our production migration.