The much-acclaimed 5-part approach that Mismo Systems is known for was as followed:

Step 1: Assessment 

The current working environment of all the companies was assessed. Since this was not an onsite project, it was important that the team from Mismo had enough information to put together a project plan and timeline.

A detailed assessment questionnaire was sent out to all the respective IT managers which helped the Mismo team with the required information. A Microsoft Teams meeting was also held with the respective IT managers to let them know of the project and also answer any queries that they might have. It also served the purpose of letting the respective parties get acquainted with each other.

A SharePoint site was created and shared with the project management team so that the documents relating to the project can be shared on a single platform without the need for sending dozens and email back and forth.

Step 2:  Design

Once the assessment phase was completed and all the required information was collected, the project moved on to the next phase, the Design Phase.

The design phase comprised of the Mismo team soaking in all the information and creating a design in accordance with the business requirements received from our client. A Design Document was created for the same which broke down the various aspects of Office 365 tenant configuration

The document was then shared with all the IT managers to get a final response from them before the project moved on to the next phase.

A project plan was created detailing the timeline of the project. A detailed project plan was created for each company detailing the steps that would be carried for the migration to take place. Owners for each task were mentioned with expected completion dates. This helped make sure that all the involved parties knew what was expected of them and make sure that the project was completed as per the timelines.

Since this was a multi to single platform migration, the use of a 3rd party tool was recommended to make sure we could migrate most of the user data to the new system. Mismo suggested the use of BitTitan as a 3rd party tool not only because it is one of the most popular 3rd party tools out there but also due to Mismo’s past experience in using the tool.

Step 3: Pilot 

Once the assessment and design phases were completed, the project was kicked off. A comprehensive user communication was sent to the users of all the companies along with the scheduled dates on which they will be migrated to make sure that they had a smooth migration experience.

To kick off the migration for each company, a group of users were selected who were the first ones to be moved to the new service as part of the pilot. This was done to ensure that any challenges that the end-user might face were documented and accounted for beforehand. This ensured that the migration team took the required steps to make sure that there were no surprises once the migration moved into the deployment phase.

An extensive user communication was drafted and sent out to all the users detailing all the changes that were going to happen as the migration progress. It also contained a high-level view of the new tenant to help users understand the main reason as to why the migration was happening in the first place.

The user communication also contained the escalation matrix so that users could get in touch with the migration team in case they were facing some issues.

Step 4: Deployment 

• Once the pilot phase was completed, the project then moved on to the actual migration phase where the remaining users were migrated. Since this was a “multi to single platform” migration, we had to take a different approach for all the companies.
• One of their companies which were using legacy Exchange On-Prem email systems were the first one to be migrated. This migration consisted of setting up a hybrid environment in which users were migrated in batches. BitTitan wasn’t used as native options from Microsoft to migrate from On-Prem exchange to Office 365 were quite powerful. A hybrid was set up between the On-Prem and Office 365 using Exchange Hybrid and Azure AD Connect.
• Another company that was using G Suite for their email systems was migrated. We decided to go with the coexistence mode so that the users could be migrated in batches so as to make sure that there was no overload on any system, either G Suite or Office 365, owing to the large amount of data that was to be migrated. BitTitan was used to migrate the users so that Google Drive, Google Calendar data, and other stuff could also be migrated which was not possible with the native migration method.
• Since four of their companies were using Office 365, we had to use BitTitan for migration since Office 365 tenant to tenant migration is not yet possible with native Microsoft tools.

For one of the companies, it was decided that the users will receive brand new mailboxes on Office 365. It was decided that there is no need to migrate any user data as they used to keep all their email data on-premises.

Step 5: Transition 

After all the users were migrated to the new platform, the project moved on to the transition phase. Once the migration was done for each company, a user training workshop was conducted wherein the users were let know of how the new systems work.

Also, the day to day work was handed over to the IT managers of the respective companies. Mismo team was present during the transition phase to help the IT managers if anything came up.

The documentation for the project was also created during the transition phase and shared with the project management team.

Documentation for day to day admin work was also created and shared on the project SharePoint site for admins so that they can look up anytime they have any doubts about any of the services in Office 365.

Documentation on how the admins/users can take advantage of the new platform to increase their productivity was prepared as value adds.