no need to cross post in all 3 CRM groups. The other observations are
Hope this helps
CRM Certified Professional - Developer
Check for unsupported customisations in script code.
Unsupported, you'll probably have to re-create these after upgrade.
Firstly, I'd redeploy CRM 3 into the test environment and upgrade there.
Secondly, BACKUP. Both server and databases.
The only sensible option is in-place upgrade.
For supported customisations you'll have to retest everything, I'm seeing
some minor glitches reported here and there.
For unsupported - well, you are on your own. If in luck, you'll have them
documented and "recreated" on CRM 4. Not everything is possible - filtering
lookup dialog is a good example.
There is *always* a chance :-). Lost data - very remote chance. Structures -
not sure what you mean. Reports - unlikely. Pages - unlikely. Unsupported
customisations, e.g. stored procs and views - very likely.
Depends. If you need multitenancy, this is your only option (me think). If
not, you can go for a separate site. In any case, you might need to adjust
code connecting to CRM to get correct security context.
If they compile under 2.0 then you should be fine. ASP.NET is extremely good
as far as backward compatibility is concerned. If you're using external
assmeblies or controls, you'll have to rebuild those using 2.0 framework or
get the updated version.
If they're using documented features then they should work fine against
default organisation. May have minor hiccups in permissions area but nothing