How to judge the work involved in migrating a website from ColdFusion to .NET

I am trying to judge the work involved in migrating our website from Coldfusion to .NET. At this stage all we want to do is create an exact replica so scope creep should hopefully be avoidable.

Does any开发者_如何学编程one have any suggestions for judging the volume of work required?

It's pretty much impossible to know this without knowing exactly what your application does and how it works, how big is it, what database systems and external resources does it consume? etc.

Also the biggest factor is going to be the programmers you have working on the migration. I would be looking for very experienced .NET programmers who are very familiar with ColdFusion. Are they hard to find? Are you hiring? I don't know.

Without knowing your application - or your programming pool skills and talents - it is really impossible to answer your question I'm afraid.

You could perhaps ease your transition to .net by using New Atlanta's BlueDragon. It's ColdFusion, but implemented in .Net.

Migrating from CFM to .net isn't much easy. Because some core CFM functions ain't much easy to migrate to .net like . need to know more scope of your website.

Gartner estimates 160 lines of code converted per man day for roughly similar languages. That plus the size of your code base gives you a rough estimate, if you assume the ColdFusion is "like" C# (e.g., all the Coldfusion constructs translate easily, which probably isn't the case; then the conversion rate goes down).

See also discussion at Things to keep in mind during Application Migration: ColdFusion to Spring

Our web page on migration provides more details including discussion of pitfalls and alternatives.