Cloud Commander enables collaboration between Office 365 tenants and delivers a systematic, structured approach for migrating data between tenants. Cloud Commander currently offers Exchange Online and OneDrive migrations, with additional workloads, like SharePoint Online coming to the tool very soon.
Cloud Commander is installed in your Azure, delivering security and speed. Your data doesn’t leave the confines of your environment, ensuring privacy and control. It also allows for the update of both source and target on-premises Active Directories objects, and this facilitates the migration and coexistence for those in a hybrid deployment. The same feature set is available for those who have a cloud-only deployment.
The secondary benefit is speed. The fastest migrations are those closest to the data, and by deploying in Azure, the solution can leverage this proximity and command top speeds for your data transfer. The migration is orchestrated in a modern user interface, that’s clearly presented, and easy to use.
A. Once deployed: Cloud Commander matches source and target mailboxes, and they’re entered into a migration wave. These migration waves are then scheduled to move mailbox data.
Once enabled for migration: Quadrotech’s AIP technology facilitates the fast transfer of data.
Once data has been migrated: Mailboxes are completed or “switched”. This means that Cloud Commander will adjust Active Directory, Azure AD, or Exchange Online objects to complete the migration, and enable coexistence.
Finally: a workstation agent will be triggered to update the end user Outlook profile.
A. There are a couple of key differences. Microsoft’s MRS functionality is only able to move mailboxes, whereas Cloud Commander can migrate additional workloads, and is expanding to include even more. Cloud Commander also has various management features to help you simplify and automate the entire process, including: who gets migrated, when, and how the migration is orchestrated. The Microsoft cross-tenant solution requires a much more manual approach and is not as equipped to deal with the complexities that large organizations face during these projects.
A. Cloud Commander was designed as cloud-based solution and runs primarily in an Azure environment. If required, the solution can provision Azure resources. The resource requirements for Cloud Commander are directly correlated to the total number of users and the respective data volume for these users. As it is possible to change resources in Azure relatively easily, you may choose to start with lower requirements, and ramp up as the project grows.