Workflow Studio is the unified canvas for flows, subflows, decision tables, and AI agents. Flow Designer is not deprecated, but every new pattern lands in Workflow Studio first. Teams that try to migrate everything at once burn out by week three. Sequence matters more than speed.
Inventory before you migrate
Run a sys_hub_flow query and group by active=true, last execution date, and average run time. Flows that have not executed in 90 days are migration candidates only if a stakeholder confirms they are still required. Roughly 30 to 40 percent of legacy flows in mature instances are dead weight. Delete those first. The migration backlog shrinks before you write a single line of new logic.
Move triggers, then logic, then UI
Workflow Studio supports record, scheduled, inbound email, and Connections triggers natively. Start by re-pointing triggers in a sandbox copy, leaving the body identical. This proves the trigger surface works without changing behavior. Once triggers are stable, refactor the body into Workflow Studio actions. Save UI improvements (status panels, error views) for last.
Action equivalence is not perfect
Several Flow Designer actions have different parameter shapes in Workflow Studio. Specifically, Look Up Records accepts a richer query builder, Update Record defaults to optimistic concurrency, and Call a Subflow returns a typed object instead of a generic map. Build a translation table for the top 20 actions you use, then have one engineer review every conversion against it. Inconsistent conversions show up months later as null pointer errors.
Decision Tables replace nested if branches
If your flow has more than three nested if-then branches, convert it to a Decision Table during migration. Decision Tables version cleanly, support business-user editing, and execute in roughly half the time of equivalent flow logic. The migration is also a good moment to rename ambiguous conditions like condition_1 to business terms like high_priority_vip_customer.
AI agents need explicit handoff points
Workflow Studio expects AI agents at decision points, not as wrapper logic. If you plan to add Now Assist agents, mark the handoff points in your migrated flow with a “human-or-agent” decision step rather than embedding the agent invocation deep in a subflow. This keeps governance reviewable and lets you toggle agents off without breaking the flow.
Test with real volume in a clone
Workflow Studio’s execution engine handles bursts differently than Flow Designer. A flow that processed 500 records per hour in Flow Designer may saturate semaphores in Workflow Studio if the action mix is heavy on Look Ups. Run a clone with 24 hours of production volume replayed before promoting. The Flow Execution Details table tells you whether you have a hot spot.
Retire on a schedule, not on a hope
Set a deactivation date on every legacy flow the day you migrate its replacement. Without a deadline, both versions run in parallel and someone eventually edits the wrong one. Two weeks of dual-run is enough for confidence; longer than that creates drift.
What to do this week: pull your flow inventory, mark dead flows for deletion, and pick one trigger-only migration to prove the path.
