This question is pretty vague! Yes it is possible. Get the architecture of the application to work through the current site and develop a plan for the transition to MVC. I think this is a pretty bad idea to mix methodologies. As a rule, there are rough borders between the borders between them, and if your existing staff is used for web forms, you will inevitably βleakβ web methods to your MVC website. Consider the change or do not do it at all.
It's worth it? May be! Moving away from the classic asp is a good choice, so there is a point in favor. Other things that come to mind: what are the pain points for your current site? Is it unstable? Is your classic asp stuck in tons of included files? How modular is the site? Do you feel that your employees can train at MVC? What budget should you make for the transition? What is the timeline? If this fails, how much money will your organization lose? How much credibility? What opportunity do you create for your competitors if you fail?
source share