We actually went through this exact journey last year, so I can share a bit of what it was like. We had a fairly large CRM tool written in old .NET Framework, and while it kept doing the job, the cracks were showing — long load times, complicated dependencies, and difficulty finding developers who even wanted to touch that codebase. When we finally decided to migrate to .NET 6, it was definitely not a “click and done” process, but the results were worth it. We managed to clean up a lot of old code, containerize the application, and move some parts into microservices. It was painful in spots (testing especially), but now the app runs faster, is cloud-friendly, and can integrate with modern APIs. It also made hiring easier because new developers didn’t have to learn outdated tech. I’d say if your systems are business-critical and you plan to keep them around, modernization is a good long-term bet. By the way, if you want to see a breakdown of how companies approach .NET migration and modernization, I came across this useful page: https://blackthorn-vision.com/technologies/net-development-services/. It gives a good overview of the process and areas where modernization really makes a difference.