Up to now we have been using the Microsoft method for migrating existing SBS 2003 to SBS 2008. For all intents and purposes, this method has worked quite well for us.
We are now in a position with one of our clients, yesterday’s recovery (previous blog post), where we need to expedite their migration, but need to do so with minimal interruption to their operations and our own.
So, we are looking to run a Swing Migration for this particular case. We are doing so because the Swing method allows us to run most of the migration here in the shop while our client remains totally productive.
This in turn allows us to work on the processes as time permits and then insert the newly migrated SBS 2008 into their production network with minimal impact on their productivity and minimal need for on-site time.
From migrating SBS 2003 onto new hardware or off existing hardware and back on again, the Swing method is an awesome way to bring about change on a production network with minimal impact on our clients.
The Swing method has also been instrumental in providing the resources and abilities to bring back SBS catastrophic failures seemingly from the dead and most importantly providing us with the _confidence_ to bring those networks back.
We strongly recommend that any IT technician working with SBS have an SBSMigration.com subscription to augment the needed skills to migrate and recover SBS networks.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book