Migrating Email to Microsoft 365 - What You Should Know

When You're Migrated

Users are migrated in batches. Based on when you're migrated there may be some resources that you temporarily lose access to until other users are migrated, at which time those shared resources can also migrate. Things like shared calendars may disappear, and then have to be manually re-added. You can submit a helpdesk ticket for assistance with doing this.
After your mailbox is migrated you will need to remove your mail account from any mobile devices and then re-add them. Your mail will not work on these devices until you do this. Part of the migration process reconfigures your Outlook to point to the 365 servers, but mobile devices must be manually changed. Instructions for this process can be found at the links below:

Android devices: If you're not already using the Outlook app for Android, we recommend you do. Android devices are not all the same, so it's difficult to provide instructions. If you'd like to continue using whatever Android mail app you're currently using, you may need to work with support to do so. Otherwise, click here to learn how to set up Outlook for Android (instructions for those already using the Outlook app can be found at the bottom of the page):

365 - How do I setup Christman email on my Android based phone?

Apple devices: We recommend using the Outlook app for Apple devices as well (just to be standard), though it's not as important as for Android devices, and can require additional setup.

365 - How do I remove and re-add my Christman email account in the default Apple Mail app?

HELP! I Can't Get Into My Email!

If you have issues getting into Outlook after you've been migrated, please submit a helpdesk ticket and we'll take care of you as soon as we can. In the meantime you can always log into Outlook Web Access. Go to https://outlook.com, click the Sign In button at the and log in with your Christman email address and password. This can get you up and running right away so you're not dead in the water until we get to your ticket.

A common issue is Outlook not trying to log you into Microsoft using your email address--it tries to send Microsoft your christman\username instead, which won't work. This will result in you getting a screen like the one below:

As shown above, if you get this screen and see christman\yourusername, click on the Sign in with another account link. This should pull in your email address (type it in if it doesn't) and then you can continue normally.

After You're Migrated

Email Archiving: Email archiving is done differently using Microsoft 365. On our local server we used a product that would make copies of your emails and put them in a separate archive database, replacing the actual emails in your mailbox to shortcuts to that database. This helped keep mailbox sizes under control, and since it was done in the background without user intervention, you didn't have to think about it.

This will no longer be the case in 365. It's up to you to keep your mailbox size down. Your mailbox has a limit of 50GB. When you start approaching this limit you'll get emails from the server indicating as much. If you reach (or exceed) 50GB you won't be able to send or receive email until you bring your mailbox size down. For more information about this (including some tips on doing so), you can go to the following link:

Microsoft 365 - Archiving Email and Mailbox Limits - Christman Help Center (helpscoutdocs.com)

Junk Email Folder: The Junk Email folder was disabled by default in our on-premise system, and we relied solely on our Barracuda Email Security Gateway. While we're still leveraging this, Microsoft enables the use of the Junk Email folder in Outlook by default with all 365 accounts. We've not found a satisfactory way to disable this, so you'll need to keep an eye on that folder in case there's anything you're missing. We understand this can be cumbersome having more than one place to try to find missing emails (your Spam Quarantine Summary and this Junk Email folder) but we're looking into ways to mitigate (or remove) this functionality.