But businesses don't want "new". They want stability. They don't want to be constantly changing things because that disrupts their business and costs them a lot of money, with little or no benefit.
That is a big thing. Other departments that use systems hate any changes that disrupt their work. Learning new systems takes work and slows them down and often takes away what they see as advantages. On our old green screens, many users have key sequences memorized so they can carry out various actions (such as data entry) with only occasional glances at the screen. Forcing them to use a new tool takes that away that ability until they relearn it. Even if the new tool offers new feature or options, the user will consider it to be an inconvenience unless it benefits them, personally. If they can see how it benefits other departments, they will usually (grudgingly) accept the changes. If it only improves things on the back end (that only IT people see), they will avoid using it until we force them to use the new tool and take away the old tool.
Not only that, but many users will often use applications incorrectly unless it has checks to prevent this. If a new application implements something to prevent that misuse, the user will complain that the program has a "bug" because they can no longer do something. From their perspective, this is an inconvenience and a disruption because it forces them to change the way they do things without providing them with any benefits. For example, an old version of one of our apps lacked certain data entry checks. So the data entered by one department would often end up creating new data records because one of the users was too lazy to look up an existing record. This meant we would have multiple data records all representing the same supplier or multiple records representing the same customer. While this would occasionally affect other departments, it did not cause that department many (if any) problems... so they didn't see any problem with their way of doing things. When an updated tool was deployed, those users complained that it didn't work right or it was forcing them to do extra work (just a couple seconds), when in reality, it was preventing problems in other departments and saving another guy from spending time every week cleaning up data.