If you've got a small business and want to move to Office 365 or to Google Apps, the main choice is whether you want 1TB of storage per user (Office 365) for $5/user/month or unlimited storage (Google Apps) at $10/user/month.
We are going to try Office 365 as we've not used this system too much and many people we advise are more likely to go with Office. We are assuming we don't need Office licenses for this, so this is just email and storage.
In any case here are the nuances of getting this working. I won't cover the simple sets which are basically signing up and then changing your DNS to point to validate you as it varies a lot depending on your DNS provider. And there are some good migration gotchas from folks like Infoworld
Office 365 let's you move a few users at a time so you can run in mixed mode. Perfect for having say the IT guy move, then move a few more and see how it goes. It also allows easy fall back if necessary as you can leave your old mail server running and just change the DNS if Office 365 has a cow. So first you need to logon to office365.com and then go to Admin/Exchange/Migration and click on the
+ so start one and choose migration to. There are many flavors, but we will use the simplest one which is IMAP migration since basically everyone supports it.
Tip. The strangest part of this is that it requires a CSV file with the user name even for a single user. So many people at Microsoft and there is no online form? When you click on the help, at least in Google Chrome, you get nothing, but the CSV is kind of what you would expect. If you have Windows domains, then you use
domain\user as the syntax. If you are using a hosted server, then it is probably more like
firstname.lastname@example.org, so the file needs to be like this with the headers exactly as shown. Of course the big problem here is that you need to know everyone's password (yuck!) or have an system-wide admin password that gives you access to every mailbox. The Exchange specific options assume that btw:
EmailAddress,UserName,Password email@example.com,contosoterry.adams,1091990 firstname.lastname@example.org,contosoann.beebe,2111991 email@example.com,contosopaul.cannon,3281986
This is probably the biggest reason not to use the small office versions of Exchange because you need active directory synchronization to allow things like sharing of calendars across the people who have migrated and people who haven't.
Directory Trap. But if you are (like us) already used to CalDav where you don't have those nice Exchange features you are in luck because the sync is client-side. Otherwise you get to spend a boatload of money for Azure sync to make it all work. Longer term, you have to ask if you want to be dependent on this feature of the Microsoft backend. It is way better to try to stick with CalDAV so you can move to Google to something else in the long term. So in a reasonable sized organization (say 100 people), if you don't need that much shared calendars, I'd say get off of the Exchange shared calendar view and live with CalDAV for the long term. Google actually does a good job of supporting this as do the Mac Mail and Calendar clients. I'll have to try to see how Outlook does.
Email Delivery Tip. The big question here is, do you want Office 365 to see the mail first and then hand if off to your legacy mail system and do it the other way around. If you are conservative, you leave your mail.