The migration is complete. The Hanselman Family has moved to Google Apps. Why? Here's why:
However, we had a complex setup, as I assume most families do. Or at least, most Geek Families. This includes not just my wife, but also parents, brothers, cousins, in-laws, etc. Being IT for the family is hard. I've changed the names to protect the innocent, but all the tech is real.
We've got Two Families here, we'll say the Hanselman's and the Smith's. I married a Smith, so I'm the Support Department for them as well.
At this point, we've got folks with Email stored ONLINE and folks with Email stored OFFLINE. Let's first do the switchover to Google Apps, then tackle each problem one at a time.
I have two domains, one for each family's last name. I could certainly create a separate Google Apps account for each last name, and you're welcome to do that. However, I chose to put Hanselman.com as the primary domain, and "Smith" as the Domain Alias. Everyone will be able to choose what last name they want their "From" to show, so it doesn't really matter.
Once you've signed up your first (primary) Domain go into the Domain Settings|Domain Names control panel in Google Apps and create a Domain Alias. When you "claim" ownership for a Domain, Google will give you a big long number and say "go make a text file with this big long number inside, and name it this big long filename. Upload it to your website, then come back and tell me about it, so I can go check to prove you own this domain." You'll need to do this for as many domain aliases as you set up.
First, after creating a Google Apps account, make a new Google Apps User for each existing Email User at your existing domain. This is important because you don't want anyone losing email. So, if you've got scott@ and fred@, then make accounts for each one. Google Apps will generate a password, but I set a default one for each person myself.
Second, have a plan as to how you want your subdomains to be laid out. We wanted it simple and obvious, so: home.mydomain.com, docs.mydomain.com, mail.mydomain.com, etc. Log into your Domain Name's Web Control Panel (nearly everyone has this, and Google Apps includes a Dropdown Help menu with detailed instructions on how to do this with most popular hosting services. My folks are used to logging into mail.mydomain.com but I wanted to allow access to the old mail, so I renamed that host address to oldmail.mydomain.com in case I screwed something up.
Notice all the CNames that are aliased to ghs.google.com. Each of those subdomains now is pointing to Google Apps. However, it's the MX Record that cause mail to switch over (nearly instantly). When you add those, then new mail starts getting delivered to Google. That's why it's so important you have a user account setup in Google for EVERY existing user ahead of time to catch new mail.
To switch over MX, delete all your existing MX records first, then enter in Google's. Make sure the priorities line up, at least in order. Google might say 1,5,10, etc, but your control panel only allows 10,50,90. That's OK, just make sure they are in the right order and the numbers are monotonically increasing.
After you change the MX records, note that all NEW email will be streaming into Google Apps for all mail to your domains. If you've setup a domain aliax, you'll need to change the MX records for that domain also.
OK, let's tackle each family member's email migration issue, one at a time.
Brother Hanselman as well as the Three Brothers-In-Law Smith are the easiest folks to transfer. They keep all their email online and they are keeping their email addresses.
Go into Gmail for Apps|Accounts and click Add a Mail Account. Note that the name of this account doesn't matter. Gmail will complain if you tell it your email is the SAME. For example, if you were firstname.lastname@example.org and now you've moved to Gmail, just tell it the name of this account is email@example.com. The only thing that matters is that the username for logging into POP is correct and the POP Server is correct. I chose to leave a copy of messages on the server in case of a problem.
If you have a LOT of email on your server, these emails will come in at a rate of about 100-200 per 10 minutes. It might take hours, or days if you have a many thousands. Be patient, it will happen, and you can keep using Gmail while it does.
I did this for Brother Hanselman and Three Brothers-In-Law Hanselman and they are all in business.
(NOTE: Gmail has been considering a built in Gmail Import process, so this section will likely be old some day. Check the manual first!)
I'll be doing this migration via POP, but you can also use the Free gXFER tool from LimitNone for Gmail to Gmail Transfers.
Hanselman Wife has an existing Gmail account and wants to keep all those emails. However, if you try the technique above and enter in pop.gmail.com, you'll get a complaint from Gmail for Apps that you can't import Gmail via POP. Lame.
The solution is two-fold. First, in the original Gmail account, make sure you've enabled POP Email in Settings|Forwarding and POP and selected Enable POP for ALL MAIL.
Then, logout, and login to your destination account in Google for Apps and from Add an Email Account, enter in the Gmail username and the POP Server as 184.108.40.206. Also, note the non-standard port 995. Don't select "Leave a copy" because Gmail won't let you anyway. However, don't worry, your emails won't be deleted in the source.
Again, this is a long running thing, so be patient (possibly days of patience.) Ok, so this gets Hanselman Wife her email archives. Now, from the source email account, create a Forwarding Rule to the new account so that emails to the original account are forwarded to the new one.
In the destination (now primary) Google for Apps Account make sure to add an Email Aliases for each email you want this user to be able to send as. Since we had two Domains, I setup email aliases per user as appropriate. This means Hanselman Wife can send as firstname.lastname@example.org as well as email@example.com from the same account.
The absolute easiest way to get your email into Gmail for Apps is if you have an IMAP server already. If so, just pay the money for a Google Premium Account and you've got migration tools available for you as seen below.
If not, and you've got a local client like Thunderbird or Outlook, go to http://mail.aol.com and get a free 2 gig account. Add it to your local mail client as seen below. Use imap.aol.com and smtp.aol.com. It's really a very nice service, truly.
Drag all your email over, folder by folder, into the newly configured IMAP store. FYI, it's WAY faster Thunderbird. Outlook 2007 is a pig for IMAP, so I've got another solution for that, but it costs $.
After the email is up, use the Migration Tools to bring that IMAP email into Google Apps.
There's lots of hacky ways that huge amounts of email can be moved from Outlook to Gmail for Apps. Believe me, Google knows this is a problem and I'm 99% sure they are working on it. Until then, you can do the IMAP trick above, or use a tool. Time is money, so I used gMOVE from LimitNone. It's a local app, licensed per computer for $29 ($19 for educational) that basically uses OLE Automation to take email out of Outlook, through it up to a "just in time POP server" at LimitNone, then it uses the GMail API to create a temporary POP account and suck the email back down.
The Good? It just works. Works fine in fact.
Each folder in Outlook becomes a Tag in Gmail. Your Inbox in Outlook is tagged "gInbox" so as not to mess up your actual Inbox.
The bad? You can only move 5,000 emails at a time, so I had to run it 7 times. Of course, there are privacy concerns as well, but you can work that out on your own. Gmail also imports messages VERY slowly, as I've said before.
Otherwise, a useful utility, and faster for me than using IMAP.
At this point, all Hanselman and Smith family members have email setup. They can use Gmail for Apps online, or if they prefer Outlook or Thunderbird, they can use the Gmail POP Troubleshooter or configure POP access to keep email in both places.
I miss anything? Works for me.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.
I trust them (more or less).
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.