Is the old way your business completed a process old and outdated-or even sometimes referred to as fragile? Take the time in your ERP move to evaluate custom solutions to determine if the customization is worth taking to your new ERP:

1. Does the new ERP provide a better, out of the box process that would work for your organization, even with a slight business process change?

2. What are the known issues of the old customization? Do the risks of moving the old process outweigh the benefits it may provide?

Has the business outgrown the processes and customizations of the past? Is it time to leverage this new ERP as a chance to redesign and reimagine how your organization can function? 

Just like furniture, moves can provide a fresh start. Adding more glue and tape to bring a broken piece of furniture to a new house doesn't make sense, so why would you do that in your ERP. 

Yes, you spent money on it, but it served its purpose for a specific period of time. Just like that coffee maker that just needs to be replaced, sometimes your customizations just become outdated and not worth fixing or adapting to the new ERP.

If end users insist a customization is needed, ask why. The answers may shock you. Some examples of what I have heard:

1. Because that is how we have always done it. 

2. So-and-so said we have to do it this way

And my all-time favorite---

3. I don't know, but we need it.

Why did I need 3 immersion blenders at my old house? I'm not sure. But I do know, I don't need 3 anymore. Sometimes when we customize environments, there are more customizations that are added over time to support (or even replace) the original customization, but just become clutter that takes up space and increases risk. We tend to hold onto these items "just in case" but fail to remove or toss them when the new change has proven to be reliable. Take the time to understand why it was done that way, and then ask if there is a better way or if it's even needed anymore.