GodaddytoOffice365

15
Jun
2021

GoDaddy Office365 to Microsoft Office365 Migration- Part 3

Planning

Once assessment phase is over, Its the time for Migration to plan on how the migration should be executed.

The key points to be answered here is

  • What all services needs to be migrated?
  • What all data needs to be migrated?
  • How data needs to be migrated?
  • Is it going to be a cut over migrating or a staged migration with co-existence?

Service migration is comparatively easy as its only the configurations to be migrated. For example, if the GoDaddy Office365 tenant has configured to use Teams, Teams as a service needs to be configured and made available to the end users for chat, calls as well as collaboration platform.

Data migration is more complex. Data needs to be migrated from Source to the Target Office365 tenant. Beyond that, Data should be made available on the same location from the end user perspective to ensure that user experience is good. For example, if the Finance team is using a private channel in teams and has a SharePoint storage used as document library, Users expect the same document library available in teams once they start using the new Office365 environment.

The next point is on how the data needs to be migrated. Multiple options are available to migrate the data. Third part tools offer much more flexibility and more coverage with an additional cost overhead. Custom Scripts and free tools are available from Microsoft if there is a budget constrain to spend on third party tools, however has lesser flexibility and coverage. If no data transfer is required or end users can take care of their own data backup/restore, the service migration is going to be a straight cutover - however user experience will not be that good and has a risk that some data can get missed.

The final point is on the migration approach. Cut over migration is much more straight approach where the service will be migrated along with the data on a prescheduled cutover window. During the cutover window, services will be unavailable and once done, Users can access their services as well as data from the new Office365 tenant. Another approach is to perform migration in multiple batches, keeping both environment active. Once all users are migrated to the new environment, GoDaddy environment can be deleted. This require co-existence, where a partial set of users will be on the target tenant and will be using services from the target tenant once users are migrated.

Migration strategy is purely depending on the total number of users to be migrated and the volume of data to be migrated. I suggest that if the environment has more than 500 users, Staged migration will be better. If the users are less than 100, Definitely go for a cutover migration.

Lets make a plan for a small environment with less than 50 users and see how we can do a cutover migration with minimal downtime in the next part.

Posted by Shabarinath in Office365Migration, 0 comments
14
Jun
2021

GoDaddy Office365 to Microsoft Office365 Migration- Part 2

Initial Assessment

This should be the starting point for Migration Team.

On a high level, Migration team should have clarity on what all needs to be migrated and what volume of data needs to be migrated. The different segments and the respective areas are listed below.

Azure AD

  1. User Objects
  2. Groups and Group Memberships
  3. Azure AD Register Devices
  4. Azure AD Joined Devices
  5. Policies on Password expiry, Lockout, MFA etc
  6. External Identities
  7. Enterprise Applications using Azure AD for authentication
  8. External Applications using Azure AD for authentication
  9. On-premise AD Sync

Exchange Online

  1. User Mailboxes along with SMTP domains used
  2. Any delegation on user mailbox
  3. Shared Mailboxes along with SMTP domains used
  4. Shared Mailbox Access and Send As Access
  5. Resource Mailboxes
  6. M365 Groups with membership details
  7. Distribution Groups / Security Groups with membership details
  8. Any Application Integrations
  9. Mailbox size of User Mailboxes as well as Shared Mailboxes
  10. Policies specific to email address
  11. Transport Rules
  12. Accepted Domains
  13. Inbound and Outbound email routing
  14. Mx Records

SharePoint Online

  1. SharePoint Sites with URLs and Size
  2. OneDrive for Business URLs and Size

Teams

  1. Teams with membership details
  2. Team Channels on each Team
  3. Private Team Channels with membership details
  4. SharePoint URL for backend SharePoint document library - For Teams as well as each private channels
  5. Any additional applications used within Teams channels

DNS

  1. How public DNS is hosted
  2. Who can update the DNS records

This is the minimum list and team can expand further.

Once the assessment phase is over, We can move on to the planning phase.

Posted by Shabarinath in Office365Migration, 0 comments
13
Jun
2021

GoDaddy Office365 to Microsoft Office365 Migration- Part 1

Is it possible to migrate?

One of my friend was asking if its possible for migrate Office365 services availed from their hosting provider - GoDaddy to a direct Microsoft Office365 tenant. Since I had an opportunity to work on multiple Office365 migration projects including cross tenant migration, I thought of writing a series on how to migrate from one tenant to another, with minimal downtime. Most importantly, How to migrate from one tenant to another without using paid tools.

An Overview on Office365 Service

Office365 Service Includes a wide spectrum of services and is rapidly expanding. In this context of migration, lets differentiate the services into two segments. Services which doesn't have any user data and services which has user data. Services without user data is comparatively easy to migrate as its just the configuration to be migrated. End users can avail the service from the new tenant as if moving from one taxi to another. However, services with user data is different as the data is important as moving the service and the data should be available in the new tenant for the user to user once the service is getting migrated. Its like travelling on a connected flight, where our baggage will also get moved as we move from one flight to another. And at the destination, We expect that the baggage will be ready to collect at the pickup point to resume the journey.

The key services in Office365 which has user data are listed below.

  1. Azure Active Directory - Holding identities, groups etc
  2. Exchange Online - Emails
  3. SharePoint Online - SharePoint Sites and document libraries
  4. Microsoft Teams - Collaboration System with SharePoint and Exchange Online as the key data storage location

I will be detailing on each of these section in the upcoming posts. With an objective of having the critical data migrated to a new tenant, You should be in a position to handle at least these four components to make the migration successful.

Defining Migration

Migration can be defined as the process of moving from one environment to another for a reason. As part of the initial assessment, The project team involved in migration will definitely look at the data to be migrated if any. Services which are getting migrated will resume from the new environment for sure. The question is - Is that really enough? From an end user stand point, Migration experience will be great only if the migration team can give everything as is. Be it an email, SharePoint document, teams channel or even an item kept of Outlook Draft folder for sending at a later stage. The data laying at different places from Source Tenant needs to be migrated to the Destination tenant. Just migrating to the new environment is not enough, it should should be available to users at the same location they used to access earlier. To be more specific, if the users are accessing a document library through teams channel which has multiple documents with different level of access restrictions, The destination tenant also should have the same teams channel, with all the documents and their respective access restrictions. Instead, If the data is only getting migrated to a different location without metadata and asking users to copy the data back will not provide a good user experience.

Is it possible to migrate from one Office365 tenant to another with out using any third-party paid tools?

My answer to that question is a partial YES.

When I say partially yes - The fact is that we have options to migrate the data to certain extend. However, some other data can be migrated but cannot be restored to the same location or make it available on the same interface in the exact way it was on the source tenant. However, the most critical user data of any organization is Email and SharePoint document library - which can be moved without loosing data or user experience.

Posted by Shabarinath in Office365Migration