Guide, 8 Nov 2026, read 8 Nov 2026
How to migrate sixty workflows to a new system
The inventory
One row per workflow: name, trigger, owner, last run, number of runs in twelve months, the tasks, the approvers, the documents. The last two columns decide the rest: a flow with zero runs in a year is retired, and a flow whose owner has left is reassigned before it moves. In the sixty behind this guide, a third had not run in a year.
The collapse
Group the rows by process. Four onboarding flows for four entities become one onboarding flow with a conditional branch on the entity; three leaver flows become one. The collapse needs conditional tasks on the new platform, which the map documents on Shapes, Rippling, Workday and Humaans. Without them the sixty stay sixty.
The rebuild
Write each process as a paragraph: the trigger, the steps, the approvers, the documents, the branches. On a platform with AI-generated flows (Shapes, Rippling, Humaans on the map) the paragraph is the build; on the others it is the specification for the builder. Keep the paragraph; it is the documentation nobody wrote the first time.
The parallel run
- Run the new flows beside the old for every live starter, leaver and request for two weeks.
- Compare the task lists each morning; a missing task is a bug in the rebuild.
- Switch the trigger to the new system on a Monday; keep the old system read-only for a quarter.
- Delete nothing until the audit log of the new system shows a full cycle.
Sources
- Shapes: Workflows 2.0, read 8 Nov 2026
- Shapes: conditional tasks in workflows, read 8 Nov 2026
Last reviewed 8 Nov 2026.