Best fit for SharePoint Designer workflows
- • Temporary continuity while discovering legacy dependencies.
- • Low-value workflows that will be retired with the source site.
- • Processes awaiting business owner decisions.
Legacy workflow comparison
SharePoint Designer Workflows vs Power Automate
SharePoint Designer workflows are frequently undocumented and business-critical. Power Automate is a common modernization target, but workflows should be assessed and redesigned rather than blindly recreated.
Decision guidance
- ✓Map workflows to business processes, not just technical definitions.
- ✓Retire duplicate and stale workflows before rebuilding anything.
- ✓Use Flow Migrator for repeatable workflow discovery and modernization planning.
Factor
SharePoint Designer workflows
Power Automate
Horton Scientific recommendation
Visibility
Often hidden in sites, lists, libraries, or content types.
Can be inventoried and monitored through Power Platform admin capabilities.
Start with discovery across site collections before migration waves.
Support ownership
Frequently owned by former admins, site owners, or no one.
Can have explicit owners, service accounts, backup owners, and support runbooks.
Treat ownership as a migration requirement.
Business logic
Logic may be fragile, old, or difficult for stakeholders to validate.
Can be redesigned into clearer flows, approvals, and exception handling.
Translate logic into stakeholder-readable process maps before rebuilding.
Governance
Limited modern governance and monitoring patterns.
Requires DLP, environments, monitoring, connection strategy, and ALM decisions.
Use migration to establish Power Platform standards.
Risk
Breakage risk rises when old sites are migrated or retired without dependency mapping.
Can reduce risk if designed, tested, and monitored correctly.
Do not cut over content without workflow dependency checks.
Best fit for Power Automate
- • Critical approvals, notifications, and business processes that need modern support.
- • Processes moving to SharePoint Online, Teams, Dataverse, or Microsoft 365.
- • Workflows that need clear error handling, monitoring, and ownership.
Product accelerator
Move Nintex workflows with Flow Migrator
For teams moving Nintex and legacy workflow estates into Power Automate, Flow Migrator helps turn discovery, mapping, and rebuild planning into a repeatable migration motion.
Where Flow Migrator fits
- ✓Identify workflow candidates, dependencies, owners, triggers, approvals, and failure points.
- ✓Separate direct rebuilds from processes that need redesign, governance, or integration architecture.
- ✓Accelerate migration planning from Nintex into supportable Power Automate patterns.
FAQs
Do SharePoint Designer workflows have to be rebuilt?
Not all. Some should be retired or replaced by standard Microsoft 365 features. Critical workflows usually need a modern replacement.
Can this run during a SharePoint migration?
Yes, but discovery should happen early so workflows do not become late-stage blockers.
Is Power Automate always the right target?
Usually for Microsoft workflow modernization, but some processes may need Dataverse, Azure Logic Apps, custom apps, or retirement.