KEEP OR SWITCH
Keep or switch? Ten checks before moving automation
A migration should remove a named failure, not merely replace a familiar irritation with a fashionable one.
Keep the current tool unless the new option solves a Must after migration, retraining, duplicate running and rollback are included.
THE TEN-CHECK LEDGER
Make the switch earn its disruption
- FailureWhat current problem causes measurable harm?
- MustWhich condition cannot be met today?
- VolumeHow often does the problem occur?
- CoverageDo required apps, triggers and actions exist?
- DataWhat history, credentials and connections must move?
- ParityWhich workflows must run unchanged on day one?
- PeopleWho learns, documents and supports the new system?
- OverlapHow long must both platforms run?
- RollbackCan the team return without losing work?
- ExitWhat result would cancel the migration?
Three legitimate outcomes
Keep when dissatisfaction is real but the business failure is not.
Pilot when one workflow can test the decision boundary without moving the estate.
Switch when a Must is unmet and the migration cost is lower than continuing harm.
COST THAT IS NOT ON THE PRICING PAGE
Migration cost has a before, during and after
| Before | Inventory, access review, workflow mapping and test data |
|---|---|
| During | Rebuild, parallel running, training and incident coverage |
| After | Documentation, monitoring, cleanup and contract exit |
SMALLER MOVE