Just in case someone else may have run into this I found it not to be a migration issue but rather an issue with a couple modules not setting well with the introduction of a new namespace introduced in DNN .3.0 here is the answer I was looking for. Hopefully it will be a help to anyone else who ran into this problem.
------------------------------------------------------------------------------------------------------------------------------------------------------
Here was an answer from DNN community about the issue check it out
-----------------------------------------------------------------------------------------------------------------------------------------------
Of the error/warning messages you posted, there is only one error that is preventing the site code from properly compiling. The others are all warnings relating to use of methods that are now marked obsolete and can be safely ignored.
Regarding the error with the Chat module, DotNetNuke v 5.03.00 and v 5.03.01 introduced a new namespace DotNetNuke.Web which can conflict with the .Net namespace System.Web if class/method references are not fully qualified in code that is "just in time" compiled on the fly when the site is visited. Code most vulnerable to this problem is found in the App_Code folder. A similar issue exists with the DotNetNuke XML module.
To fix the problem:
1. If you are not using the Chat module but have it installed - remove all files from the folder App_Code\Chat. You should then be able to open the site and log-in as host user to delete the Chat module extension (including all files).
2. If you are using the Chat module, you can easily fix the issue by editing line 309 in the code file App_Code\DNNChatCodeHelper.vb. Change
Dim ctx As Web.HttpContext = Web.HttpContext.Current
to
Dim ctx As System.Web.HttpContext = System.Web.HttpContext.Current
note that I have added System. in two places in that line. Save the changed file (or re-upload it to your hosted site via FTP) and you should be good to go.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Another person commented about it in this manner
-------------------------------------------------------------------------------------------
Unfortunately there is a problem with some modules, you'll have to manually fix the source code for those modules by fully referencing System.Web.HttpContext in the files where the errors are pointed out.
here are a few blog posts about it
http://www.dotnetnuke.com/Community/B..." target="_blank" rel="nofollow">
http://www.dotnetnuke.com/Community/B... http://www.dotnetnuke.com/Community/B..." target="_blank" rel="nofollow">
http://www.dotnetnuke.com/Community/B... -----------------------------------------------------------------------------------------------------------