This is exactly what I have been doing for the last 4.5 months. I was hired on to port an application from Borland to VS 2005 with some C# sprinkled in there. To be more specific, I am porting from Borland OWL. Are you using OWL? Sorry, I am not familiar with Borland C++ Builder or the Borland tools. I'm just porting code and we use a makefile to compile the Borland code. I can give you some pointers if you are using OWL. A lot of the classes and methods transfer quite easily to MFC. Things like TDC is a CDC, TPen is a CPen. There are other portions of Borland which are nice and make you wish MFC had the same thing. For example, Borland has an actual color class (TColor). There is no equivalent in MFC so I had to use a COLORREF and the RGB macros in place of TColor. There are other helpful Borland classes which you just need to figure out how to do the equivalent in MFC. Since you will be working with MDI, you should be aware of Borland's window structure. Do you have a background in MFC and how the window classes relate? In MFC, a window contains a MainFrame which itself controls the MDIClient window. These are one-in-the-same when it comes to MFC classes. In Borland, you actually have two separate classes. A TMDIClient class and TMDIFrame/TDecoratedMDIFrame. You will need to convert the two classes into the one CMDIFrameWnd. Does the project use STL? The STL is different between the two and requires some minor name changes. A compile error will point this out and you can usually figure out the equivalent just looking it up on MSDN. Unfortunately, there is really no information on-line for Borland information. I use their OWL help documentation if I ever get stuck. This should at least give you a heads up. Let me know if you have any more questions or concerns. We can take this to e-mail if necessary.