Complex Workflows: A manufacturing company had a complex approval workflow built using SharePoint Designer for their on-premises SharePoint. This workflow involved multiple approval stages, conditional logic, and integration with their ERP system. During migration to SharePoint Online, they found that this workflow couldn't be migrated directly and had to be recreated using Power Automate. The process was time-consuming and required a deep understanding of Power Automate's capabilities.
Lack of Functionality: A financial institution had a workflow in their on-premises SharePoint that used certain actions which were not available in Power Automate. For example, the workflow used the "Loop with Condition" action, which doesn't have a direct equivalent in Power Automate. They had to redesign the workflow to achieve the same functionality using available actions in Power Automate.
Integration Issues: A retail company had a workflow that integrated with a third-party system using a custom web service. During migration to SharePoint Online, they found that Power Automate couldn't connect to the web service due to security restrictions. They had to work with their IT department to allow Power Automate to connect to the web service.
Training and Adoption: A non-profit organization had numerous workflows created by different departments using SharePoint Designer. During migration, they found that their staff had difficulty adopting Power Automate due to its different interface and functionality. They had to invest in training for their staff to get them up to speed with Power Automate.
These examples highlight the importance of thoroughly assessing your current workflows before migration and planning for potential challenges. It's also crucial to provide adequate training for staff to ensure smooth adoption of the new tool.