Flow Designer is the future, and ServiceNow has been telling everyone to migrate for years. But Workflow isn’t dead — it’s still in production at most large customers, and rewriting working Workflows just because Flow Designer exists is a waste of money. The honest answer to “which should I use” depends on three things.
First: is the process record-triggered or scheduled? Both tools handle both, but Flow Designer’s trigger configuration is cleaner and supports more conditions out of the box. New record-triggered work goes in Flow Designer. Second: does the process need to call subflows or actions that already exist in one tool? Don’t fragment your logic across both — if there’s a chain of existing Workflow activities you’d otherwise have to rebuild, stay in Workflow for that chain. Third: is the team comfortable with the visual editor? Flow Designer’s UI is dramatically better, but if your team has been writing Workflow script activities for years and your operational runbooks all reference the Workflow editor, the switching cost is real.
Default to Flow Designer for new work. Leave existing stable Workflows alone. Migrate only when you’re already touching the Workflow for another reason. That’s the boring, correct answer.