swing kit- 2003 standard r2 conversion to sbs2011 standard

You don't need a swing kit.  Follow my migration guide here: https://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_2465-Migrate-Windows-2003-with-Exchange-to-Small-Business-Server-2008.html

It's for SBS2008 but the process is identical to go to SBS2011

I have not used either the Swing kit or Demazter's guide, but I've heard nothing but good things about both.  My understanding of the kit is that it provides you a way of doing things that is completely off-line so if you make a mistake, it does not affect ANYTHING in your existing domain.  And if gives you plenty of time to do it.

When I've done migrations, I've followed Microsoft's recommended paths and not had issues.  (Just follow closely).  Items NOT on your existing server should be skipped.

I have not used the swing kit before, but the offline method seems very handy, along with the ability to roll back if needed. Would I be able to use the swing kit and do a good portion of the server conversion offsite?

Yes once AD, DNS, etc replicate the majority can be done offsite

At one point, Microsoft had a document on migrating from Std to SBS in the technet library...can't find it there now...I'm going to check with Microsoft SBS Support and Sustained Engineering, when I'm in Redmond at the end of the month for the MVP summit

I think one of the keys in making your decision on which method to use, is simply your technical comfort level.   If you're fairly new and feel like you may need some support during the process...the swing migration tool kit is great because you get access to Jeff for 90 days after purchase.

If you're an old pro..then it may not be required

Once the conversion is done, the old system is it offline, or demoted and available to be reused on the network as a member server?

I am fairly new and think the swing kit would give me that support/help I need for this conversion.

Is Jeff the only person, or does he have a team of people answering support calls? I'm only wondering about getting in contact with someone when there could be an issue.

Have you looked at my guide I posted in my first comment?  It's step by step.  It's been used many a time by many a people here on EE including some of the top experts.  The difference is my guide uses a standard process that most are familiar with.  The swing migration guide does not.

You don't need to do anything with the old server other than remove Exchange.  It can stay as a secondary domain controller within your SBS network.

because you are converting from Std Products, The standard server currently holding the FSMO roles, could take the role of addtional DC or just a member server   the original exchange server would be gone

The other thing worth considering, as you are an EE user, is there are a number of excellent SBS experts here on EE.  And, I'm not aware of many of them using the swing kits.  Whereas I know a few of them use my guide.

I'm not aware of a Microsoft version of this guide which is why I wrote my own a few years ago.

demazer- it is for 2008 and I'm using 2011. nothing against your guide at all. It is very well written process. with my comfort level being a bit green and the version difference I'm concerned about following along with a guide for 2008 when I'm installing 2011.

With the conversion I do need to migrate exchange from the old to the new, any major problems with that, or is it just as procedural as the rest of the conversion

The process is identical for 2011 as it is for 2008 which is why I haven't updated it.

The biggest difference is SBS2008 uses Exchange 2007 whereas SBS2011 uses Exchange 2010.  The process of migrating from Exchange 2003 to either of these is the same.

Even the SBS wizards are the same in SBS2008 as they are in 2011.

Actually a number of the top people in this forum have used the swing migration kit either for themselves or their customers.  I know them personally.   I'm sure there are other top people in this forum who have either used demazter's  guide or some other methodology.

I was more referring to it as the ability to readily get support.

We often see "anyone used the swing kits" and not many pipe up and say they have.

When I see those questions, the first thing I do is refer them back to Jeff, because, after all, they get 90 days of support from Jeff when they purchase the kit.   Now you can get most of the material on Jeff's site (or used to be available) without a purchase, but then you did not get the support if you ran into an issue.  I suspect that's where a lot of those come from

So the difference then between the 2 offerings is one is offline and rollback potential, the other is not. Support will be limited to swings staff or the group who has used demazter write-up

'I'm in a real pickle, probably one of the toughest decisions of my life!' ...anchorman Ron Burgandy.

I really appreciate all the feedback.

Look at it this way.  The swing is proprietary and although it is supported by Jeff (I don't think he has a team) the methods used are non standard and I'm not sure they are supported by Microsoft.

My method uses standard practices so even if people are not aware of the guide itself they will have no doubt used the steps if they have performed any type of migration in the past not using a swing kit.  That's a lot of the experts on this forum.  And would include experts from the Windows Server, Exchange Server and the SBS zone.  I perform migrations ever day either live or in my lab.  When I wrote that guide I did at least 9 virtual migrations just writing it.  When we find things that don't work, it gets updated.  It's used a lot on these forums by question askers and experts to grea success.

Don't get me wrong, I'm not knocking the swing kit, I've never used it.  I don't see the benefit of paying for something you can do for nothing.  I think, the swing kit even adds an additional layer of complication judging my some of the questions we see here on EE.  Neither has at least one of the other experts posting in this thread, I've no idea if Cris has?

Sadly, not being an MVP I don't swing in those circles (excuse the pun)

Like I said before I'm not knocking Jeffs guides, I've never used them.  I am just defending mine :-) I don't know why, but I feel the need to :-)

not unreasonable to defend something for which you spent a lot of time on, and hopefully the discussion helps the author make a decision on the right method for his situation.

Exceptional contributions in forums like EE, is what results in one being awarded with the MVP recognition, so you never know ;-)

Having performed many migrations using Demazter's guides (not the Microsoft guides) and never encountering a problem, I would use his guides every time.

I haven't used the swing migration method before but can see the benefits if you are not 100% confident in performing a migration.

Both methods will result in the same outcome.  One methods involves extra hardware and will take longer and if you have the hardware and the time and lack the confidence, then the swing method might work better for you.

If you want a one-step migration, have good backups and are safe in the knowledge that Demazter is usually available on EE (most of the time), you can expect to get support from him if you need it for free with your EE subscription, so you could save the cost of the swing kit.  Also, if you are on a tight budget, swinging will cost you more.

Ultimately it's your call - both methods work and work well.

I can vouch for the numerous migrations performed to generate the migration guide as I was on the receiving end of the YIM comments when he was writing the article!! ;)

none