*** Before you do anything, remember to make backups!!!!! *** 

Ok so this was a million times easier than I was expecting -- my site is completely migrated over and I'm running tests on everything.  So far, so good.  I'll go over how I did it (may not be the best way, but it worked).  I have ran into issues with the animation extender, but I'm working on that.

First I downloaded all 3 MS Ajax items -- the toolkit, the core items and the CTP, uninstalled the old atlas items and installed the new.

Next, I created a subdomain and created a new Ajax 1.0 CTP site via Visual Web Dev, mostly to get the new web.config file then re-created the site to get the toolkit add-ons.  There's only 1 line of code difference on the toolkit, so add this under <page><controls> after you copy the toolkit dll up to your bin directory (AjaxControlToolkit.dll).

One catch I found was I had to copy up the Microsoft.Web.Extensions.dll file for the site to even compile, so I copied that up, no sweat, site compliled and I got my blank page.  Since my home page and the usercontrols associated with it are not ajax-ed (yet), I started to copy items from the live site to the testing grounds -- all of it, excpet the web.config.

Now mind you, I have a lot of things going on in the web.config (error handling, themes, profiles, sql connections, sitemaps, etc) so I had to copy those over into the places necessary -- worked like a charm, no sweat, even the encrypted items copied over and didn't complain.

It was SUPER simple from here, with a few considerations.  First, if you use a lot of the extender controls (animations for instance) these have been switched up a bit -- so check the examples to see how much (less) code you have to do, which you can find here http://ajax.asp.net/ajaxtoolkit/.  For the most part, atlasToolkit needs to be replaced with ajaxToolKit and that should take care of most of those -- now for the usual things like update panels, control event triggers, those are stupid easy.  I searched for "atlas" and replaced with "asp" as the documentation calls for on each page that requests an Ajax control.  So search for atlas and replace with asp.  For the triggers, search for ControlEventTrigger and replace with AsyncPostBackTrigger, and that's all I had to do (again, most of my site is update panels and triggers, not a lot of extensions, so keep that in mind).

I'd highly recommend doing this one page at a time and not in mass, just in case and to keep your sanity.

Otherwise, this was a lot easier than I thought and later this evening (when I have a heck of a lot more bandwidth) I'll move my site into production with Ajax 1.0 Beta :-)