Postope Designer 2010 Workflow Engine Retirement
On 6th July 2020, it was suddenly announced that SharePoint 2010 workflow engine is going to stop working by November 2020.
For at least a few of my clients it will represent a catastrophe.
Our suggestion is to push back the retirement date to a more reasonable date. For example, match if with SharePoint Designer 2013 support lifecycle or with InfoPath support lifecycle.
Large organizations depend on clear sunsetting timelines. Announcement that leaves them only four months to react is completely unrealistic. Organizations need to plan resources, budget, hire SharePoint SME’s and involve business owners that rely on these workflows and much more.
Reasons for postponement:
- The clients were not properly warned about the Workflows retirement.
- There are SPO tenants with thousands SharePoint 2010 Workflows running with no direct path of quick replacement.
- Not all Workflow 2010 can be replaced with Workflow 2013 engine or Power Automate because of features differences.
- Many Clients do not have enough time and resources to replace the existing workflows.
- Pandemic is still not over and this announcement feels very out of place.
We’ve been working one on one with customers deeply impacted by this change and encourage people to reach out to support if they have special circumstances. However, we wanted to provide clarity that our policy will not be changing and our previously communicated timelines will continue. In that regard, we will be retiring 2010 Workflows on November 1st, 2020 in SharePoint Online. After November 1st, 2020, while existing 2010 workflows will stop to run, users can still open and view their workflows in SharePoint Designer. Please visit the following link to get the latest updates about the 2010 Workflows retirement: https://aka.ms/sp-workflows-support.
181 commentsComments are closed
Oz Techy commented
it's a P1 incident waiting for sure. please extend...
Three months is not nearly enough to plan and convert. This timeline is not acceptable. Please postpone.
Corne van Dyk commented
We have 22,000+ workflows that will need to be transitioned. Please postpone!
Jerry Stevenson commented
Providing such a short time frame for an enterprise with 50+ workflows, some complex, is insanity. We need one year minimum to make this kind of transition.
At a minimum, Microsoft needs to delay this for their government tenant customers. Even the current documentation indicates that feature parity has not yet been achieved for approval workflows within the government tenants. (https://docs.microsoft.com/en-us/power-automate/us-govt#power-automate-us-government-feature-limitations)
Also, please consider the current state of things. We recently migrated the Medical Examiners department for the largest county in our state to SharePoint online. They leverage SharePoint 2010 Approval workflows heavily. They are working on migrating them, but have been paralyzed since the onset of the pandemic.
A group of people in Microsoft who clearly don't understand the full power, capability and real world usage of SharePoint 2010 workflows created a "here's why you don't need SharePoint 2010 workflows any more" page.
It makes interesting reading - and if you only looked at this page (and knew nothing about how real customers used SharePoint 2010 workflows) then you might also make the dumb decision to murder SharePoint 2010 workflows with effectively no notice.
I recommend that everyone goes and submits additional feedback for the page (links at the bottom of it) with all the reasons that Power Automate still doesn't provide a viable replacement for SharePoint 2010 workflows, even if we did have a sensible time to do such a migration. After all, this specific page is Microsoft telling us why we don't need SharePoint 2010 workflows any more, and we need to tell them all the things they have forgotten that they built into this system.
Lori Kuebel commented
3 months notice is not enough notice, unless you plan to fund the transition for us and that will still be a stretch to get this work planned out. Why was this not on the Roadmap?
Miroslav Holub commented
I think that most of the people are expecting MS to clearly state things like these in their road map. 3 months advance notice is maybe enough time to communicate the need to migrate to stakeholders and nothing else. This is absolutely unacceptable.
Please we need postpone this change. At least, at the end of this year, because Microsoft has not notified it with enough time and we have a lot of workflows 2010 deployed in Sharepoint that are managing core process in the company.
We need more time to do this changes and migrate the Workflows to Power Automate.
@ Anonymous from 18. July: Word and Excel are how old? I would like to see the uproar, if Microsoft would introduce a new version that is not downward compatible.
And everyone had to recreate documents by hand.
The problem is not the retirement itself. The problem is that you can not use old workflow files with the new solution.
Kudos to Microsoft. How or why businesses still use 10 year old software is beyond me. They have time, money and resources to build workflows, but no time, money or resources to maintain a proper SDLC? That is on them for lack of planning. Retire it I say!
please postpone, not enough notice to convert all.
Support needs to be extended through the first 1/2 of 2021.
WTF we need more time to migrate! We are in the middle of a pandemic! DELAY THIS DELAY THIS.
This is unrealistic for Microsoft to drop this bomb on the SharePoint community as many organizations are struggling to promote and support the use of PowerAutomate and PowerApps.
This is really bad planning from Microsoft especially during a really tough year. There are hundreds of customers who are going to be hurt with this announcement and this is just not enough time.
Microsoft seriously needs to revisit this ASAP. It's giving all of us heart burns.
please postpone, not enough notice to convert all.
Microsoft persuades customers to migrate from their on-premise solutions into the cloud (Microsoft's private "sandbox"), but with this movement, we see that it leaves IT systems policies & stability into Microsoft's hands which is more dangerous than a monkey with a razor ....
Veronique Palmer commented
Microsoft is asking for a class action lawsuit with these actions. They don't care about their customers at all.