You can pass UAT and still lose the business on Monday morning. Planners reopen Excel because it is faster to be locally right than globally consistent. Change management for ERP is the work of retiring shadow systems without humiliating the people who built them.
Why spreadsheets survive
- They encode tribal knowledge the ERP workshops never captured.
- They make individuals indispensable.
- They forgive incomplete master data.
- They are available on a plane without a VPN drama (perceived, if not true).
A change plan that respects operators
- Inventory the critical 20 workbooks and what decision each one drives.
- Hire the spreadsheet authors as designers—paid time in the project, not after-hours heroics.
- Train in the user’s week, with their SKUs and customers, not generic demo data.
- Measure shadow-system usage (file opens, email attachments) as a KPI alongside tickets.
- Celebrate deletions. A retired forecast file is a go-live trophy.
Training formats that stick
| Audience | Format | Proof of learning |
|---|---|---|
| Executives | 30-min decision dashboards | They stop asking for the old PDF |
| Power users | Sandbox challenges | Complete a nasty scenario solo |
| Casual users | 90-second task clips | First-week ticket mix shifts |
| External warehouses | Joint dry run | ASN / receipt without calls |
Conclusion
Moving from spreadsheets to ERP is an identity project disguised as software. Capture the knowledge, train on real work, measure the shadow systems, and reward the global process. Do that, and hypercare gets quieter every week. Skip it, and you purchased an expensive reporting layer on top of Excel.