Getting it running on Windows is going to be tough enough, when you consider that the version of Windows / IIS it was developed on are probably no longer supported.
Does your application have extensive auto tests? I'd hazard a guess at probably not.
The best bet for getting it working is to (If your ops team will permit it) buy licences for the ancient version of windows it was built for, and run that on VMs on whatever OS you want to use on your hardware.
The old version of Windows your app was written for (e.g. Windows 2000 server) probably won't work on modern hardware, or at best will be unsupported by your hardware vendor. Therefore you have no option but to either run the app on a newer Windows (Bad; this will introduce subtle bugs that you cannot test) or run it on a legacy Windows in a VM.
If the application is to be exposed to the internet, running an old version of Windows (even fully patched) is not really a good idea.
Rather than trying to put a round peg into a square hole, try to work out the minimum-risk way of continuing to run the legacy app while your development team fix it, develop auto-tests etc.