Skip to main content

My client has a SP site collection with a Content databases that is too big (over 800 GB). It contains many Nintex Workflows. Subsites need to be promoted into their own site collections with a new SP Content and Nintex WF database. What is the recommended approach for doing this in a manner that will not affect running WFs?

Here you will find different scenarios for migrations >>>  


Reply