Every system migration I’ve been part of has been sold internally as a technical upgrade. In practice, the technical migration is the easy 20%. The other 80% is behavioural: getting a team that has always kept its own local documents to trust a shared, visible system instead.

The turning point for us wasn’t a training session on its own — it was removing the old way entirely, on a fixed date, with no fallback. Ambiguity is what kills adoption; a firm, well-communicated deadline is what forces it.

If I were advising anyone starting this now, I’d say: budget as much time for the conversations about why as you do for the technical rollout. The software will work on day one. The culture takes longer.