On-Premises Exchange (versions 2007 and later) to Office 365 Migration Guide




  • Avatar
    Zack Adams

    this new check list is horrible bring back the old one!!!

  • Avatar
    MITC Support

    This is the guide?  What happened to the old one?  This is a joke!

  • Avatar
    Larry Kaye

    Hi, Zack and MITC Support Team:


    We recently started an effort to refresh our Migration Guides, based on customer feedback we commonly received when resolving technical support issues.

    We want to make sure that these documents, and all Knowledge Base articles, are as helpful as possible for our BitTitan customers.  To that end, we invite you to provide detailed feedback on needed and desired changes to this article in the Comments section.

    We pledge to review each comment and make appropriate updates as soon as possible.


    Thanks for your help,

    Larry Kaye

    Manager, Knowledge Management


  • Avatar
    Kris Rutz

    The documentation that used to be here had each step that needed to be completed and in which order it needed to be completed. 

    The current instructions simply state do x,y,z. 

    The old instructions stated step 1. Here's what to do with pictures. Here is step 2 with instructions. Etc.

    It was nice to be able to go to one page and be able to walk through all of the necessary steps.

    The instructions were so good that we simply created a link to the page and said do this.

    We are now regretting that decision and wish we would have copied out the old instructions.


    For example: 

    The old instructions (which we had a cached page of and grabbed ) said:

    1. Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948

    2. Set up accounts on Office 365 and assign licenses. These can be created in several ways:

  • Prepare the tenant to send and receive large mail items. KB005139
  • Contact Microsoft to ask to have the tenant EWS throttling limits raised for 60 days. Note: This step is only required if your Source environment will support migration speeds that are faster than the Destination. KB005493
  • The new instructions state.

    • A provisioned account that has application impersonation or delegation rights to all mailboxes.
    • Throttling policy on the Source. How do I disable the throttling policy on Exchange?
    • Global administrator account, or an account with full control, for the Destination.
    • All of the mailboxes for the Destination created.
    • You must have edit access to the DNS records.

    Instead of a link on how to do each individual thing just declarative sentences of what needed to be done.


    We really liked your product and praised the documentation throughout our office. Now not so much. Hoping you will go back to the ways things were. 

  • Avatar
    Larry Kaye

    Hi, Kris:


    Thanks for the detailed feedback.

    I will pass this along to our Migration Guide development team for review.





  • Avatar
    Tony Ciovacco

    I really wish this instructions page had more pictures. Had trouble finding the "Schedule Cutover " button.

  • Avatar
    Nicholas Humaciu

    Hello Tony,

    Thank you for the feedback! I will pas it along to our Knowledge Management team for review.


  • Avatar
    Sean O'Sullivan

    I have a little input. 

    1. I also had trouble finding the Schedule Now button, and altogether using DeploymentPro, it's a little confusing but its easy enough to figure out. A little nicer guides would make it seamless. 

    2. DNS Changes after migration? On-Prem exchange will cause all the work we've done to be meaningless. Competitors have that in their guides, somewhere. 

    On the creating a impersonation account, you are missing some steps for creating that role and assigning it to your 'admin' account. 

    Other little pieces missing here and there. 


  • Avatar
    Thornton Springer


    I have completed my migration and it all seems to have gone smoothly, however I am now left with an SBS Exchange server 2007 that I need to get rid of.

    Are there any special steps that need to be taken before I remove exchange?

    Do all the old on prem mailboxes have to be transferred to Mail Enabled Users as per this article?




  • Avatar
    Sean O'Sullivan

    @Thornton Springer - You don't SBS and Exchange are built-in and you will not have a good time. Simply disable/break down as much of Exchange as you can. I believe i deleted mailboxes, data store, and disabled services. Anything else you do will potentially need the SBS install disc for some crazy reason. For that reason, Anytime we have SBS, we leave Exchange on there, but broken as badly as we can manage.

    Not sure why you want to convert anyone else to your hosted exchange... If you need to create MEU, just build them manually with a CSV export. That's my 2 cents

  • Avatar
    Thornton Springer

    Hi Sean,


    That's the problem, I need to remove the entire SBS server.

    As we have ADSYnc running if I remove the mailboxes they then get screwed over on O365, so basically I need to get rid of SBS without damaging the mail attributes and then get a hybrid exchange up and running in it's place for management.

  • Avatar
    Sean O'Sullivan

    Ah. So you are syncing the MSEXCHGUID attribute up with ADSYNC? That is why, it thinks your mailboxes are local exch, and it's thinking you have a hybrid setup when you dont. 

    You might need to use ADSI edit to remove those attributes, then re-sync. Or potentially revert the sync from AD to cloud only, then re-setup AD sync but configure it to NOT sync the MSEXCHGUID. That was in bit titan documentation somewhere. 

Please sign in to leave a comment.