Workflow migration paths

Nintex recommends the following migration paths for Nintex for Office 365.

Following is the recommended migration path for Nintex for Office 365.

Migration path	Migration method	Migration type	Migration scope
Office 365 to Office 365	Export / import Third-party product	Workflow design Workflow context	Single workflow Multiple workflows

When you migrate Nintex within the context of Office 365, the following scenarios apply: Based on those paths, you can perform the following types of migrations:

• List/library to list/library

• Site/site collection to site/site collection

Based on those paths, you can perform the following types of migrations:

• Workflow design

• Workflow context

On major benefit of using Nintex for Office 365 is that you gain access to the latest interactive versions of Nintex Workflow without manual updates. Because of the automatic updates, the upgrade option is not mentioned here.

SharePoint on-premises to Office 365

Following is the recommended migration path for Nintex for Office 365.

Migration path	Migration method	Migration type	Migration scope
SharePoint on-premises to Office 365	Third-party product	Workflow conversion	Single workflow Multiple workflows

Migrating from SharePoint Server to Office 365 can be complex because the underlying SharePoint platforms behave differently, though our migration tech partners provide tools that make this easy to achieve.

When converting your Nintex workflows from one platform to another, the best approach is to evaluate the current workflow design. You can achieve 80 percent success for most workflows with the support of a Nintex tech partner product to convert the design for you.

When attempting to convert the workflow the following scenarios apply:

• List/library to list/library

• Site or site collection to site or site collection

Based on those scenarios, you can perform the following types of migrations:

• Workflow design

• Workflow context

If not planned appropriately, SharePoint on-premises to Office 365 migrations can be surprising, costly, and resource-draining to complete.

Considerations:

• Not every process – including those requiring high security – should be migrated. The more security required for a process, the less Office 365 should be considered – at least the public cloud version.
• Microsoft offers a private or dedicated cloud option that may be the right choice for your organization. We suggest you do your research before deciding – due diligence s better than hindsight.
• Before a migration, perform an inventory of what processes you have that should be migrated. Run the Know Your Workflow script to gather as much information as possible to help make smart transition decisions.
• Once you have decided which workflows to move prepare them by either replacing actions that are more compatible for Office 365 or assessing the benefits of rebuilding the process from scratch in order to take maximum advantage of Office 365’s platform functions. Remember, there is no wrong way to build a workflow, but there are more efficient ways for that workflow to run depending on the platform and functionality available.

Migration scenarios

To help drive the relationship between the migration scenarios, consider the following information:

Item (content type) based

• List/library to list/library with a similar content structure

• Site/site collection to site/site collection with a similar content structure

Version based

• SharePoint 2007 to 2010

• SharePoint 2010 to 2013

• SharePoint 2013 to 2013 (development farm to production farm)

• SharePoint 2013 to 2016

Platform based

Any version of SharePoint Server to Office 365 (SharePoint Online).