Customization vs. Adaptation
Whenever a company considers implementing a new system, the question arises whether to use the vanilla version or customize it.
The advantage of the vanilla version are that it is quick and easy to install, and that the version has been tried and tested by many other customers. This leads to a robust system, one which the vendor knows inside and out and can easily maintain and support. The downside is that it requires the users to adapt themselves to a new system, and history tells us that most people don't like changes. This will lead to a long adaptation process, and high support costs.
Customizing the system on the other hand can allow for a reasonably short adaptation period, but will most likely create many bugs that will frustrate both users and supporters. Also the infrastructure may not be designed to support the changes, and this is another possible pitfall of any new system.
It has been my experience that it easier to change the company to fit the needs of the new system, rather than changing the system to fit the needs of the company. The best experience was when we clicked on "Next" when installing a new system, and then learned to work with it.