SummaryHow to migrate a site or workflow to a new site or environment
SolutionWhen a site is migrated, the ID of the site collection can change. For example, if a site collection is backed up from one farm and restored to another, it will be assigned a new site collection ID. Nintex Workflow application pages and workflow instances use the site collection ID to find data in the Nintex Workflow content database. If the site collection ID changes, and the records in the database are using an out of date ID, the data for a workflow will not be found.
In this case, the NWAdmin.exe MoveData command allows the new site collection ID to be provided as part of the command. When data is written into the target database, it can be written with a new site collection ID, allowing the product to find the data when accessed from the restored site collection. The data for each workflow instance is moved one by one. If any fails to move, the tool will display error details and prompts the user either to retry moving the instance, skip the instance or abort the process, rolling back any changes.
Also of note, anytime you perform a site migration using the stsadm.exe export/import commands, you will need to use the NWAdmin.exe PrepareSiteForExport and FixSiteAfterImport commands to realign workflows. The PrepareSiteForExport command adds metadata to the site in the form of a file named SiteMetaData.xml stored in the hidden NintexWorkflows library on the site. This file is used when the site is imported to update the list ids used in the workflow. The FixSiteAfterImport command makes use of metadata in a file named SiteMetaData.xml stored in the hidden NintexWorkflows library on the site,
generated with PrepareSiteForExport.
All of these commands and further explanations are fully documented in our NWAdmin.exe Operations Guide here:
Also, the full Nintex Workflow Backup and Restore Overview Guide can be found here: