Have piece of mind by discovering your on-premises Nintex Workflow MP Score today.

The Migration Probability Score was created to help you identify the workflow actions in the workflow as well as the probability or likelihood of that workflow successfully being converted (migrating) to an Office 365 Nintex Workflow. This is the first iteration of that project and I hope you find it valuable.

Use the form below and see if your Nintex workflow has what it takes to successfully migrate to Office 365.

Step 1: Upload your workflow

[contact-form-7 id=”680″ title=”Workflow Upload Form”]

Step 2: Results

There are no results to display. Please upload a valid Nintex for SharePoint Server workflow first.

Step 3: Understanding the results

How to read the results?

The score is based on a special formula I derived from trial and error. In theory it will give you a basic gauge on what actions you have in your workflow and the likelihood of them being converted.

Probability Scoring

  • Low risk – this means your workflow contains few to no actions that should present issues when being converted
  • Medium risk – this means your workflow contains one or more actions that may need a configuration change or be replaced with a different more compatible action
  • High risk – this means your workflow contains more than one action that is either not supported or has potential configuration issues
  • Start from scratch – if you see this, document your workflow as best as you can and start building a new workflow in Office 365. Don’t attempt to migrate it unless you’re bored

You may also notice comments underneath your action count. I created short codes to help interpret the comments.

  • Find and replace (F&R): These are actions that may or may not work well in Office 365 and you look for a similar action and replace that if possible or if you do migrate, understand that replacing that action may help.
  • Find new functionality (FNF): These actions have compatible functional actions in Office 365. You should be able to migrate most of these and reconfigure them as necessary.
  • Start from scratch (SFS): This means that action isn’t supported at all and you will need to find another action or set of actions to achieve similar functionality in Office 365.

Below are three migration partners that I recommend you check out and use to help you with converting your workflows correctly. Because of my position with Nintex, I cannot actively endorse or suggest one above the other and copied statements below from their websites. What I can say is that if your workflow is 70% or higher, it should migrate with minimal errors and configuration challenges. This is no guarantee, and I will be updating the criteria over time. My goal is to help you understand what may not migrate so you can either correct it and increase your MP score, or migrate it and replace it once its uploaded into Office 365.

Sharegate  –  www.en.share-gate.com

We built the tool with simplicity in mind. We make sure to simplify every task for less hassle, more control, and to save you more time.

Metalogix  –  www.metalogix.com

Metalogix moves, manages and protects content that lives within and around Microsoft SharePoint, Exchange and Office 365. We ensure that your business has the freedom to collaborate without the risk of information loss, no matter what platform, on-premises or in the cloud.

AvePoint – www.avepoint.com

Accelerate Your Migration, Management, and Protection of Office 365 and SharePoint

Project notes

This project was started because I wanted a quick an easy way to determine if my Nintex for SharePoint Server workflows could be converted to Nintex for Office 365 workflows. What I check for: Basic conditions, actions that aren’t supported in Office 365, and complex logic that may error out. Please note that this is not a guarantee, but can give you a general idea if your workflow can be converted.

Note* I do not and cannot guarantee that your workflow will successfully migrate. This is to give you a better idea and as we continue to improve on it and I’m hoping to get to that point to provide more accuracy on whether your workflow will or will not migrate successfully.