A client wants a heavily customized process that closely matches their legacy system. How do you respond?

I first understand why the current process works the way it does, then show how standard Salesforce functionality could meet the underlying need. I explain the long-term costs of customization, such as maintenance, upgrade risk and dependence on developers.

If customization truly adds business value, I support it with a clear design and documentation. The goal is a recommendation grounded in business value rather than replicating the old system screen by screen.

Look for a clicks-before-code mindset balanced with client value and change management. A pitfall is either refusing all customization or rebuilding the legacy system without challenge.