How We Move D365 Automations Off Legacy Workflows Without Breaking Operations
Every Dynamics 365 environment we open has the same drawer. Inside sit classic workflows built years ago, a SharePoint approval nobody owns, a bot that still logs into a desktop app every night, and a dozen flows tied to the account of someone who left. Nobody planned this. It built up one quick fix at a time.
We see this most often a few years after a Dynamics 365 implementation. The project went live, the partner moved on, and the automations kept running without anyone reviewing them. If that sounds familiar, our Dynamics 365 consulting team starts exactly here.
Power Automate modernization is the process of moving legacy automations, including classic Dataverse workflows, SharePoint workflows, aging RPA bots and unmanaged personal flows, onto governed, solution-based Power Automate flows. AI actions are added only where a decision needs judgment. The goal is automation your team can monitor, support and change safely.
Three things make this urgent in 2026. Microsoft has frozen the classic workflow designer, older SharePoint workflow engines are being retired, and the 2026 release wave changes how flows are built, monitored and licensed. Waiting adds risk without adding value.
Microsoft's documentation tells teams to build flows instead of classic workflows for new automation. Microsoft support guidance describes the classic designer as a legacy component on a deprecation path, with no fixes or improvements planned. Existing workflows still run. A problem you hit next year has no fix coming.
Microsoft removed SharePoint 2010 workflow services from Microsoft 365 tenants on November 1, 2020. The 2013 engine followed, with a cutoff of April 2, 2026. Once an engine is gone, migration tools cannot read the old definitions. Convert first, then migrate.
Microsoft's 2026 release wave 1 plan (April to September 2026) includes self-healing for desktop flows, video logs of the 60 seconds before an unattended run fails, Copilot Studio actions inside cloud flows and process mining. These features pay off on flows built cleanly in solutions. A tangle of personal flows gets little from them.
From April 21, 2026, up to 25 cloud flows can share one Power Automate Process license, and the 250,000 daily action allowance is shared across the group. A tidy inventory can use that. A messy one cannot.
Legacy automation is any workflow that runs on a retired or frozen engine, depends on one person, or fails without anyone noticing. In Dynamics 365 environments, that usually means five asset types, each with a different modern target.
| Asset | Typical symptom | Modern target | Effort |
|---|---|---|---|
| Classic background workflows | Run late, cannot use approvals or modern connectors | Cloud flows in a solution | Low to medium |
| SharePoint 2010/2013 workflows | Engine retired, definitions unreadable | Cloud flows, plus Power Apps for old InfoPath forms | Medium to high |
| Legacy RPA bots | Break when screens change, costly to run | Desktop flows with self-healing, or API-based cloud flows | Medium to high |
| Personal flows | Stop when the owner leaves or a license changes | Solution-owned flows with a shared service account | Low |
| Unmonitored approval flows | Fail silently | Flows with run-after error alerts | Low |
Microsoft's own migration tooling converts the simple SharePoint cases. Complex or InfoPath-dependent workflows need a manual rebuild, and that is where our Power Apps development work usually comes in.
Every legacy automation gets one of three outcomes. Retire it if nobody uses it. Migrate it as is if the logic still fits. Redesign it if the process itself has changed. We score each one on business criticality, failure cost, run frequency and dependencies.
Nobody uses it. Switch it off and delete it. There is less to monitor and less to license.
The logic still fits. Rebuild it as a governed flow that does the same job.
The process has changed. Rework the steps before you rebuild, so old mistakes stay behind.
What breaks if this stops tomorrow?
Moving every workflow like for like carries old mistakes onto the new platform. So we ask the owner of each automation that one question. If the answer is nothing, we retire it. If the answer is month-end close, it gets a careful redesign and a long parallel run.
We modernize Power Automate in six steps: inventory, classify, design the target state, rebuild with dual-running, cut over, then govern. Microsoft’s RPA modernization guidance follows a similar order, starting with simpler desktop automations and moving to API-based cloud flows.
We pull every classic workflow, SharePoint workflow, desktop flow and cloud flow across your tenant and Dataverse environments. For each one we record the owner, trigger, last run and connected systems.
We score each automation and assign retire, migrate or redesign. You see the list before anything is built.
We set the environments, solutions, connection references and naming rules. We also decide which processes stay on cloud flows, which need desktop flows and which are real candidates for AI.
We build in a development environment, then run old and new versions side by side through at least one full business cycle. For finance flows, that means a month-end.
We switch off the legacy version only after the outputs match. Deleting the old asset is part of the project.
Monitoring, alerts and named owners are in place before we hand over.
Use standard flows for rules and AI steps for judgment. If a process follows the same steps every time, a cloud flow is cheaper and easier to audit. If it needs to read, classify or decide, an AI step earns its cost.
| Flow type | Best for | Billing basis | Main risk |
|---|---|---|---|
| Cloud flow | Rule-based steps across Dynamics 365, Microsoft 365 and other systems | Per-user or Power Automate Process license | Silent failures without error handling |
| Desktop flow | Systems with no API, legacy screens | Premium or hosted process license | UI changes break it |
| Agent flow or AI action | Reading documents, classifying requests, drafting, decisions | Copilot Studio capacity (Copilot Credits) | Cost drift and unclear ownership |
Gartner predicts that over 40% of agentic AI projects will be canceled by the end of 2027, citing rising costs, unclear business value and weak risk controls. It also warns about “agent washing,” where vendors relabel older automation as agentic.
We agree with the caution. Modernize the plumbing first, then add AI to a flow that already runs cleanly and has an owner. When you are ready, our agentic AI automation and AI agent development teams take it from there.
Modernization lasts only if ownership, environments and monitoring are set before go-live. We start with Managed Environments, data loss prevention policies and managed solutions in production, and add the Center of Excellence Starter Kit where scale demands it. Microsoft itself recommends starting with the admin center and Managed Environments.
Development, test and production never share a space.
They control which connectors can touch which data.
Nobody edits a live flow by accident.
Every critical flow gets a “configure run after” branch that messages a named owner when it fails.
Every flow has an owner and a backup.
Platform updates tend to expose silent failures. A failure alert catches them before your finance team does.
Licensing decides whether modernization saves money. Four questions matter: what your Dynamics 365 license already covers, whether flows need Premium or Process licenses, whether flow groups apply, and which agent flows will draw Copilot Credits.
What does your Dynamics 365 license already cover?
Do your flows need Premium or Process licenses?
Do flow groups apply to your estate?
Which agent flows will draw Copilot Credits?
Microsoft's documentation says every Dynamics 365 user is entitled to use Power Automate. It also notes that flows triggered from Dynamics 365 or Dataverse run in near real time through webhooks, with no polling. Those use rights cover specific scenarios, so we check each design against Microsoft's current licensing guide.
Desktop automation typically needs separate licensing, and agent flows draw on Copilot Studio capacity. We model licensing cost before the rebuild starts, because it can change which design is the right one.
Bring in a partner when the inventory is bigger than your team can review, when automations touch finance or customer data, or when your original Dynamics 365 implementation partner has moved on. A good partner starts with an inventory, not a proposal.
Our Power Automate consulting team works alongside whoever already supports your Dynamics 365 environment. If you are weighing that arrangement, read how we approach being the enhancement partner on an existing D365 build and how Dynamics 365 and Power Platform co-delivery works in practice.
Power Automate modernization is moving legacy automations, such as classic Dataverse workflows, SharePoint workflows, older RPA bots and unmanaged personal flows, onto governed, solution-based Power Automate flows. It includes retiring unused automations, redesigning outdated processes and adding monitoring, ownership and AI actions where they add value.
Microsoft tells teams to build Power Automate flows instead of classic workflows for new automation, and its support guidance describes the classic designer as a legacy component on a deprecation path with no planned fixes. Existing workflows still run. We found no published end date as of October 2026, so check Microsoft's current notices.
Yes. Microsoft's modernization guidance starts with simple desktop automations and moves to API-based cloud flows later. Bots that still work and have an owner can stay while you migrate the fragile ones first. Prioritize bots tied to applications that change their screens often, since those break most.
A cloud flow follows fixed steps and runs under a Power Automate license. An agent flow is a cloud flow built inside Copilot Studio, where AI can read, classify or decide between steps, and it is billed through Copilot Studio capacity. Use cloud flows for rules and agent flows for judgment.
Microsoft's documentation says every Dynamics 365 user is entitled to use Power Automate, with use rights tied to Dynamics 365 scenarios. Premium connectors outside that scope and desktop automation typically need separate licensing. Confirm your design against Microsoft's current licensing guide before you build.
Timeline depends on how many automations you have and how many need redesign. A small, documented set moves faster. A tenant with hundreds of undocumented flows and legacy bots takes longer, because inventory and dual-running come first.
Legacy automation does not announce itself. It runs quietly until a connector changes, an owner leaves or an engine shuts down. We would rather you find it on your schedule than on the Monday after a failed month-end. Start with the inventory. Everything else follows from it.
Last updated: October 2026Book an automation inventory review
We will map what you have and tell you what to retire, migrate and redesign first.
Book your reviewDynamics 365 consulting works best when Power Platform ships…
Dynamics 365 implementation and enhancement are different jobs, and…
Two Microsoft-adjacent automation tools, two very different answers to…
Canvas Apps and Code Apps solve different problems on…
Power Apps and Power Pages are two tools of…