Preparing for migration
This topic describes how to prepare for the migration.
Whether you choose a complete cloud scenario or take a hybrid cloud approach, your applications, solutions and content require preparation to ensure that everything that should be migrated is ready to be migrated.
|
To learn more about migrating, complete the Migrating Nintex to Office 365 course on Nintex University. |
Contents
Before you start
Ensure that you have done the following:
-
Evaluate and thoroughly tested your workflows before moving content. For information, see Evaluate your workflows.
-
Understand the key concepts and migration process, so you can successfully complete the migration. For information, see Understand key concepts.
-
Understand the relationship between the workflow and its content. For each workflow, answer these questions:
-
How is the content structured around the workflow?
-
Where is the workflow located? Do you have administrator access?
-
Is this workflow a good candidate for migration?
For information, see Evaluate your workflows.
-
-
Obtain the appropriate tools to help you successfully complete the migration.
Note the following some important terms and the description:
| Term | Description |
|---|---|
| Migration | Nintex uses the term "migration" to define transitioning one or many workflows from one Nintex platform to another. |
| On-premise | A physical server stored somewhere not in the cloud. |
| Office 365 | Nintex for Office 365 shares the same architecture as standard SharePoint Online designer workflows. |
| .NWF | Workflow files for Nintex on the Office 365 platform. |
Evaluate your workflows
Evaluation of the workflows must be done before you start migration.
- Evaluate factors such as content, permissions, and processes.
- Consider security aspects, availability, scalability, and access because it will affect how your workflows are used and how users interact with the processes that are converted.
For related information, see the community article Know Your Workflow Script.
Understand key concepts
Nintex uses the term “migration” to define transitioning one or many workflows from SharePoint on-premises to Nintex for Office 365.
Key concepts:
-
Workflow migration paths: Defines the path of the workflow migration. For example, SharePoint 2013 to Office 365.
-
Workflow migration methods: Defines the method to perform a workflow migration. For example, exporting a workflow.
-
Workflow migration types: Defines the type of workflow migration. For example, the workflow context type.
-
Workflow migration scope: Defines the scope of the workflow migration. For example, a single workflow.
The following table shows how these key areas relate to each other.
| Migration path |
Migration method |
Migration type |
Migration scope |
|---|---|---|---|
| SharePoint on-premises to Office 365 | Third-party product | Workflow conversion | Single workflow and multiple workflows |
Use third-party migration tools
You can use a Nintex designed workflow script to evaluate your workflows within a given environment. For example, you can view reports that describe the number of workflows published, number of actions per workflow published, over a specific time period, and much more. For more information, see the community article Know Your Workflow Script.
In addition, our technology partners have developed products to help you identify your workflows, understand the user actions, and figure out how to move the workflows and actions between platforms. For more details, see Workflow migration methods.
Get started
Review the following best practices:
For additional guidance, review the following topics: