One reason these types of projects fail is that they are asking the people running the system today to do the migration and put themselves out of jobs. It's rar

One reason these types of projects fail is that they are asking the people running the system today to do the migration and put themselves out of jobs. It's rare for people at the individual level to deny there is better tech, but as a group they know their situation. This was the same for migrations of ancient eRoom deployments to SharePoint in the mid-2000s. It's a pattern of working in big organizations. The way many do this type of migration is to bring in another set of people (or outsource the system.) These new people have no attachment to the old system, but you lose the knowledge of the people you are replacing. This ends up being worse a lot of the time, but if it's too late then the organization won't rollback, and just spend a lot of time fixing their mistakes. It's rare to get partnerships on the level that is required to change these big systems. In smaller projects, I've had the pleasure of working with some old-timers to update their technology, but it needs to be a collaborative effort.