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
POOR FORM MICROSOFT, COME ON!!!!! OK, rant over for now. It takes time and money and resources to convert processes. Currently you cannot do everything with power automate that you can do with workflows - even if I had the time and expertise to do it.
This is very unreasonable. MS should extend the timelines at least by a year or 2.
Abul Huda commented
This type of sudden notification is the reason we are still holding up our decision to move completely to SharePoint online. We don't want to be forced to use PowerAutomate over SP Designer Workflow and Infopath unless the new tool has same or more features. Also, it will need complete rewrite of hundreds of workflows and involve resources as well. I agree with others. SP Designer 2010, 2013 and InfoPath should be supported till 2026. That will give enough time to redesign and rewrite the existing apps and workflows while Power Platform become more feature-rich as well. Also, it will be awesome to include feature to convert existing workflows, InfoPath Forms to Power platform. That will definitely encourage many to move forward.
During the Covid-19 time frame teams managing remote connectivity in the workplace and assisting the workforce to become familiar with these new remote tools, don't have the time needed to deal with the overwhelming task of recreating hundreds of 2010 workflows in a new technology many of us don't know well enough ourselves. Please consider postponing this for everybody until sometime in 2021. Thank you.
We are a global 3B organization with over 14000 employees across the globe. Sunsetting this capability on this short of notice will be highly disruptive to our organization.
Denis Molodtsov commented
One of our clients has also received an extension until March.
Kim Roetman commented
FYI - I've received an extension on our tenant to March 1, 2021.
how can you do that when we are working through Covid issues - no time!
Naveen Goutham commented
Microsoft should provide atleast 1 to 2 years of time to upgrade all the existing workflows which are highly critical for business needs.
Norman Bercasio commented
MS gave us 6 years to retire or convert Infopath but 4 months to convert 2010 SharePoint Workflows to Flow? No way, Microsoft, please give us more time!
DHC Ryuu,Kokuri commented
I believe Microsoft should provide the tool to convert SP2010 workflows to Power Automate and then set the EOL for SP2010 workflow. With a short notice its hard for any organization to put all the efforts on this. We are not talking about 1 or 2 workflows to convert, its 1000s of workflows. Hope Microsoft understands their customers.
Kindly postpone this plan, as it needs lot of time to do the analysis
Eduardo Palma commented
It'd be appropriate to postpone its retirement, the features of Power Automate don't replace all the features of Workflow designer 2010 as neither its successor 2013 in every way .
It'd be important to reconsider this decision due to the limited margin of time and functionality that we can choose. an adequae time I agree that it would be to standardize them with the life cycle of sharepoint 2013 or infopath.
we have customers using 2010 based WF's that cannot be migrated to Power Automate since it doesn't support the features of recursiveness they need in order to keep their solutions alive
Debraj Roy commented
It will be very difficult for large organizations to lift and shift their many more functionalities easily in the hard time of this pandemic.
We need more time to address that.
Andy O, yes.
Jay Nebben commented
We're all under extra load due to extenuating circumstances of pandemic. The timing seems out of touch with the community and insensitive to customers at best.
Andy O commented
Has anyone gotten an extension already by MS?
Dhirendra Kumar commented
Please give us more time..