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

Guidance about Migrating Nintex Workflow Content Database data from 2010 to 2013 twice to get the most up-to-date data

Jump to solution

We are planning a 2 phased migration from SharePoint 2010 to 2013. In phase 1 we are migrating all content from 2010 to 2013, to test everything is functioning and fix any issues. In phase 2 we want to update the 2013 content with the latest version of content from SharePoint 2010. What I want to know is, when the 2010 Nintex Workflow Content Database is migrated for a second time to 2013, will this cause any issues such as duplication..? Would it be best to wiped the data from the Nintex Workflow Content Database in 2013 and then migrate the 2010 database?

Labels: (1)
0 Kudos
Reply
3 Replies
Highlighted
Automation Master
Automation Master

Re: Guidance about Migrating Nintex Workflow Content Database data from 2010 to 2013 twice to get the most up-to-date data

Jump to solution

If there was no progression in 2013 that had any meaning then overwrite would be fine. But make sure you also migrate the sites that would be effected too. If history lists do not match, could cause status confusion.

Reply
Highlighted
Nintex Newbie

Re: Guidance about Migrating Nintex Workflow Content Database data from 2010 to 2013 twice to get the most up-to-date data

Jump to solution

I've had a response from a call I raised with Nintex and the advice they gave me is to delete the Nintex database from our 2013 production servers, copy over the 2010 database and rerun the migration. There is no need to remove and reinstall the WSPs.

View solution in original post

0 Kudos
Reply
Highlighted
Automation Master
Automation Master

Re: Guidance about Migrating Nintex Workflow Content Database data from 2010 to 2013 twice to get the most up-to-date data

Jump to solution

Agreed, there would be no reason to remove the SharePoint features and solutions for Nintex.

Reply