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

Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

Is it possible to migrate this scenario? If not what are the alternatives

Can you have 2 web apps each using their own Nintex content and config DB?

Labels: (2)
0 Kudos
Reply
7 Replies
Highlighted
Nintex Employee
Nintex Employee

Re: Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

Hi,

There should only be one Nintex configuration database.
Content databases can be separated via site collection so yes you can have two content databases and have all the site collections from one web application in one database and the site collections in the second web app in another database.
0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

@SimonMuntz Thanks, so how can the Nintex 2013 be migrated across?
We can't take the config DB by the sound of it, so is it possible to migrate Nintex WFs (and SPO content) in this scenario at all?
Will running WFs be maintained?
What about the references that Nintex has in the config DB? Will the WFs still work?
I haven't found documentation about this scenario, is there any?

0 Kudos
Reply
Highlighted
Nintex Employee
Nintex Employee

Re: Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

Hi,

Please se the backup restore document to answer these questions.
https://community.nintex.com/t5/Nintex-for-SharePoint/Nintex-Workflow-Backup-and-Restore/m-p/85524
0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

@SimonMuntz Thanks for the pointer but that doesn't answer my question, in fact there are at least two comments in the thread asking the same question. The article doesn't cover restoring to different Farms

0 Kudos
Reply
Highlighted
Nintex Employee
Nintex Employee

Re: Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

Q. Thanks, so how can the Nintex 2013 be migrated across?

A. Back up your databases (SharePoint and Nintex) in 2013 and detach them.

Attach them to your 2016 farm.


Q. We can't take the config DB by the sound of it, so is it possible to migrate Nintex WFs (and SPO content) in this scenario at all? 

A. Yes you can take your configuration database to the new farm.


Q. Will running WFs be maintained?

A. As per the linked document:

Running Workflows
When performing a Backup-SPSite / Restore-SPSite process, there is a limitation pertaining to running workflows continuing after a restore of a site collection. Once a site collection is restored, any workflows in a waiting state will error when they try to continue. The reason is that the workflow instance data references the ID of the site collection in which it was started. After restoring the site collection, the ID changes and when the instance data loads and uses the stored ID, it fails. Users will see the “Error Occurred” status.


Q. What about the references that Nintex has in the config DB? Will the WFs still work?

A. What references?

0 Kudos
Reply
Highlighted
Nintex Newbie

Re: Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

@SimonMuntz 

After some more research, for this scenario I found there are 2 options, which will take a site collection and its WFs and migrate them to the existing destination Farm

  1. MoveData
  2. ShareGate

In either case running workflows will not be maintained

 

Yes you can take your configuration database to the new farm.

I thought you can have only 1 Nintex config DB in a Farm. At least you said previously

0 Kudos
Reply
Highlighted
Nintex Employee
Nintex Employee

Re: Migrating to an existing Farm: 2013 Farm with Nintex WF to 2016 Farm with Nintex WF

Hi,

Yes you can only have one configuration database and that one configuration database can be the one that you migrate.
0 Kudos
Reply