Moving from SBS 2003 to Server Essentials 2012 R2 without a swing migration for a tiny domain not using Exchange

We're looking to replace an SBS 2003 server with one running Windows Server Essentials 2012R2. It's got 5 users and the users are not using the SBS Exchange - they are using a POP email hosted by godaddy.

I did a swing migration a few years ago to 2008 and that was tedious.

For such a few number of users, no exchange store, etc.   I'm envisioning another simpler way than a swing?

Create the same users that are in the old box to the new box.  
Create the same shares (nothing fancy about permissions - any shares let everyone access the shares).
Backup the old box's data
Take it off the network
Connect the new box with the same server name, same domain name (but yes, different SIDs from the old box / domain).
Restore the data to the new box
Now the windows 7 machines are on the old domain.

>>>> is that all that's needed before the next question?

How do you easily leave the old domain and join the new domain and keep user profiles so outlook is all the same, same PST, same favorites, same desktop layout and wallpaper appearance, etc.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
You don't. That's the tipping point between migrating and rebuilding. If you want to keep that stuff, migrate.

BTW, not all migrations are "swing" migrations. And migrating fro SBS to essentials isn't exactly what I'd call tedious. Same basic install process. Same basic wizards. A minor change in how you move data and shares. Migrating can save a ton of time. Even for small environments, if you want to preserve user profiles, migrate. The MS documented method (which is not a swing) works fine.
David AtkinTechnical DirectorCommented:
Have a look at the profwiz tool here:

It will move the domain account to a local and then onto the new domain. Its not automated but I've used it once - It worked alright.

Your other option is to do it all manually (copy and past the profile folders).

Cliff is correct though. The MS procedure is there to remove this as a problem. Yes you have to do a little server side work and tweeking but its well documented.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BeGentleWithMe-INeedHelpAuthor Commented:
thanks david. That app looks like what I need!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.