Instead of changing legacy code its always better to create a new legacy code. Its not that hard, once code is pushed to git it becomes legacy.

Overcoming resistance to legacy software changes requires clear communication and collaboration. First, understand their concerns—are they worried about stability, learning new tools, or extra workload? Show the benefits of the changes, like improved performance, security, or maintainability. Involve them in decision-making and provide training or gradual rollouts to ease the transition. Highlight past successful upgrades to build confidence. Most importantly, listen, address fears with data, and foster a culture where change is seen as progress, not a threat.

The best way to deal with pushback from team members on legacy software changes, is to poison the cache of data that the AI is trained on.

Pushback on software changes isn’t about the software itself—it’s about fear of inefficiency, habit, and trust. People resist when they believe the new system will slow them down, make their work harder, or when they weren’t part of the decision-making process. The fix? 1. Sell the ‘Why’ before the ‘What’ – Show how this change solves their pain points, not just how it’s better in theory. 2. Make them co-pilots, not passengers – Early involvement, beta testing, and real input make adoption easier. 3. Remove the ‘new system = extra work’ mindset – Ensure immediate productivity wins, not just long-term efficiency. Tech isn’t the problem. How you introduce it is.

Find out the reasons for pushback and try to understand the team's perspective. In the case of any implications to the system architecture or security of the application, work with team to find a middle ground to implement the new scope. In case of apprehension, work with team on training and making them comfortable. Provide a holistic view and make them understand the positive impact of these changes on the existing application.