Tap a row for the reasoning.
The inventory
What was running.
A snapshot of the workflow estate before the consolidation question was asked. Illustrative figures in the spirit of one real review.
The decision
Keep, pilot or replace.
Choose a weighting. The same eight capabilities move between keep, pilot and replace as the priorities change. That is the point: the decision follows from the stated priorities, not from habit.
| Capability | Replace score | Verdict |
|---|
Each capability is scored 0 to 3 on four things: saving from replacing it, how much only it can do, migration risk and how much else depends on it. Weights change with the preset.
The pattern
Every workflow follows the same five steps.
- 1
Trigger
An event, a schedule or a message.
- 2
Condition
Is this case in scope and complete?
- 3
Wait for approval
A person approves anything that sends, spends or changes a record.
- 4
Action
The step runs under a service account.
- 5
Notify and log
The result and an audit trail, every time.
The migration
A governed transition.
- 30 days: pilot. Move one team and one external space. Measure what breaks.
- 60 days: roll out. After integrations and settings are validated.
- 90 days: read-only. Keep the old tool readable, then reduce licences.
- Archive properly. Restricted storage, chain of custody, retention rules. No default migration of private messages.