This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrating from a shared Exchange hosted platform to Office 365

Could someone please advise me if this is possible using the Quest migration manager for Exchange product? I am using a shared platform that is hosted by a provider and i want to migrate to Office 365. The limitations around hybrid configurations for multiple tenants has lead me to consider using 3rd party migration tools but i cannot seem to get any pre-sales assistance from Quest/Dell so i am hoping someone on the forums can help answer this query.

  • You really have two options depending on whether or not coexistence plays a part in your scenario:

    Migration Manager for Exchange requires that its agent(s) have good access to the source and target environments and thus typically would require a dedicated VPN or an on-prem presence.

    Through its directory synchronization & calendar synchronization capabilities, MMEX does allow for a period of coexistence - i.e. you don't have to cutover everyone at once in a "big bang".

    There's a fair amount of complexity in getting MMEX setup and Quest will generally want you to use some form of qualified professional services provider (either their's or a certified integrator) to perform the work as the Support team is not resourced to handhold customers through a project.

    The other option is On Demand Migrator for Exchange - a SaaS solution that allows you to do basic content migration in batches but doesn't really provide any coexistence solution. It's a great content forklift.

    You haven't told us about what the source platform version is so that might have some influence on which solution on you can use.

    'Hope this helps a bit.
  • Thanks Johnny, That is useful.
    The source environment is Exchange 2010 and co-existence will be a requirement so i suspect the more complex MMEX configuration would be required. I have always thought that Quest needed agents installing on the source and target systems so i am kind of intrigued as to how this would work with Office 365.
  • You don't need any agents on source and target systems per se but you will require hosts (virtual are fine) to host the agents. These "agent hosts" are how you are able to send data into Office 365. Obviously data going to Office 365 is going to transit the internet so benchmark testing your internet connection is going to be important to determine how long this is going to take. The documentation for the product explains all of this very well so I would suggest you give that a good read as you plan this exercise.

    support.quest.com/.../release-notes-guides