With the latest release of CloudMigrator, we’re excited to introduce coexistence for tenant migration scenarios. Bringing our customers and partners greater flexibility in long-term tenant migrations while minimizing the impact of this transition for end users.
Migrations between Office 365 tenants are common during an acquisition or divestiture where a business or individual units are being combined or separated. Due to the sizable nature of these projects, IT professionals and partners often choose to migrate end users in batches, meaning users are now split between old and new tenants, creating significant communication challenges. For example, scheduling meetings between users who are in opposing platforms will often be unsuccessful due to users being unable to see the availability of users within the opposing environment. Coexistence enables the two groups of users to seamlessly communicate for the duration of the migration without data loss, delays or calendar discrepancies.
Coexistence Configuration is a great addition to the latest CloudMigrator release:
“We’re excited to be adding Coexistence Configuration to the recent CloudMigrator release, it’s a must-have feature for large tenant migrations, and will really help out our users.”
“Using coexistence will reduce impact to end users and allows your users to operate normally while the migration takes place, ensuring staff and teams can carry on as normal.”
As the Office 365 ecosphere grows, and cloud-based companies in Office 365 experience mergers, splits, or re-branding, or simply out-grow the functionality of their current tenant - more and more Office 365 to Office 365 (O to O) migration opportunities are presenting themselves.
CloudMigrator is constantly adding new useful features to allow the most successful migrations. Find out what else has been updated in the latest CloudMigrator release here.
If you would like more information and pricing on CloudMigrator, please click here or speak to our cloud team to get some advice and best migration practices at email@example.com
6th August 2018
Find out more