I understand that MVC is usually a better overall model from what I know of it so far [...]

I know MVC has some really big advantages for any normal site [...]

It seems like you've read somewhere that ASP.NET MVC is the future, and ASP.NET should die. While, indeed, some blog authors claim that, this is only their personal opinion.

This is not even the official position of Microsoft. ASP.NET was maintained until 2015, and ASP.NET 6, also called ASP.NET Core—a mix between ASP.NET, ASP.NET MVC and Web API, is on its way. There was never a mention from Microsoft that ASP.NET is a technology of the past.

Like any other technological choice, the one between ASP.NET and it's MVC variant should be done based on your specific requirements and preferences.

If you like Razor, you'll better go with ASP.NET MVC (although, this is not mandatory).

If you like MVC pattern (and its .NET variant, since other frameworks don't necessarily use MVC in the same way), you'll better go with ASP.NET MVC.

If you have a working web app written in ASP.NET, there is no reason to rewirte it in ASP.NET MVC.

If you have a team of developers who are skillful in ASP.NET and never worked professionally with ASP.NET MVC, go with ASP.NET, unless this is an experimental project and your team wants to try a new technology.

In all cases, it's up to you to make the choice. If there are no strong elements towards one or another technology, create a simple app in both, and compare your experience. Take in account the familiarity bias, that is the fact that the unfamiliar technology will appear as a poor alternative because (1) you don't know it much and can't be particularly productive, and (2) you try to apply the patterns from the familiar technology to the unfamiliar one, and this rarely ends well.

I understand that MVC is usually a better overall model from what I know of it so far [...]

I know MVC has some really big advantages for any normal site [...]

It seems like you've read somewhere that ASP.NET MVC is the future, and ASP.NET should die. While, indeed, some blog authors claim that, this is only their personal opinion.

This is not even the official position of Microsoft. ASP.NET was maintained until 2015, and ASP.NET 6, also called ASP.NET Core—a mix between ASP.NET, ASP.NET MVC and Web API, is on its way. There was never a mention from Microsoft that ASP.NET is a technology of the past.

Like any other technological choice, the one between ASP.NET and it's MVC variant should be done based on your specific requirements and preferences.

If you like Razor, you'll better go with ASP.NET MVC (although, this is not mandatory).

If you like MVC pattern (and its .NET variant, since other frameworks don't necessarily use MVC in the same way), you'll better go with ASP.NET MVC.

If you have a working web app written in ASP.NET, there is no reason to rewirte it in ASP.NET MVC.

If you have a team of developers who are skillful in ASP.NET and never worked professionally with ASP.NET MVC, go with ASP.NET, unless this is an experimental project and your team wants to try a new technology.

In all cases, it's up to you to make the choice. If there are no strong elements towards one or another technology, create a simple app in both, and compare your experience. Take in account the familiarity bias, that is the fact that the unfamiliar technology will appear as a poor alternative because (1) you don't know it much and can't be particularly productive, and (2) you try to apply the patterns from the familiar technology to the unfamiliar one, and this rarely ends well.