The Tata Trusts have been pioneers in developing super specialty cancer hospitals in India since 1941. To strengthen cancer care in underserved areas and to promote prevention and early detection of cancers, the Trusts have embarked on a first-of-its-kind large scale public health program.
About:
Established in 2017, Tata Cancer Care Foundation (TCCF) is a Section 8, not- for-profit entity. TCCF has been set-up to implement the ambitious Cancer Care Initiative of the Trusts, ensuring affordable, high-quality healthcare to millions of Indians, closer to their homes.
With a burgeoning population of 1.3 billion, India has seen a rapid increase in cancer incidence in recent years. With an estimated 1.4 million cases reported in 2015, the number of patients is expected to rise in future.
In India, cancer has been characterized by; lack of awareness, late detection, lack of access to proper cancer care and high treatment cost. Even with under- diagnosis and under-reporting of numbers, the cancer incidence is growing at about 9% with every passing decade. India is expected to have 3.4 million cancer patients in 2050.
Phase 1: Assessment of Source Cloud Data
The first phase of an Office 365 migration plan is assessing the data with the company’s internal IT team needs to migrate. Here is a closer look at what this phase entails.
Identify the volume and type of data:
The first step in evaluating TATA TRUST ORG source cloud data is to determine 260 users’ data organization needs to migrate and what type of data it is. It includes identifying files, emails, contacts, calendars, OneDrive data, Teams Chat, SharePoint Online data, requirements.
Categorize data based on priority:
Once you have identified the data to migrate, the next step is categorizing it based on its priority. It will help you determine the order in which your IT team must migrate the data and the level of effort required for each category.
We started with exchange, contact, calendar, then OneDrive, Teams Chat, Teams Channels, SharePoint Online data.
Pre-migration analysis:
We have a cap of 20 users’ batches must migrate in a single day. This capping is given by Microsoft only. Accordingly, we created a migration batch of 20 users each.
Develop a migration strategy:
We had taken the first batch as IT users to check all migration aspects, after the confirmation from IT team, we are going to take other users to migrate.
Phase 2: Preparation
The second phase of the Office 365 migration plan is prepared the target environment. Here are the key tasks in this phase:
Account setup:
We were created users in target tenant, assign license and permission as per requirements.
Configuration:
Configured the target environment by defining policies and assigning security settings.
Pre-provisioning:
We were cross check all the users are created in target tenant, all groups, teams channels, SharePoint sites. If it is not the same replica as source tenant, we had done same aspects in target tenant.
Devise an email migration plan:
We were Developed a dedicated email migration project plan that includes filtering source emails and choosing the associated email attributes like attachments, calendars, events, contacts, tasks, etc.
Phase 3: Migration
The third phase of the Office 365 migration plan involves migrating the desired data to Microsoft 365. Here are the critical tasks in this phase:
Pilot run:
Conduct a pilot run to test the migration process with less data and identify any issues your IT team must address.
Actual data migration:
Once your team executes the pilot run without issues, migrate the entire source data to Microsoft 365 following the best practices.
Phase 4: Validation
The fourth and final phase of the M365 migration plan is to validate whether the migration was successful or not. Check out what are the essential steps to follow in this phase.
Post-migration validation through reports:
Examine the migration report to validate if the data transfer was successful and if the tool has migrated all records without any data loss.
User validation:
Validate the migration results with end-users to determine whether they can access and use the new Microsoft 365 apps as expected.
Training:
Provide training to end-users on how to use the new Microsoft 365 apps and how it differs from the previous source cloud platform.
Monitor and support:
Monitor the new environment to ensure it works as anticipated and supports users as needed.
Conclusion:
This migration taken time because client needs to set up users laptop or machine before go live with particular user with some device policy.
Migration has been done successfully and all the data are migrated 100%.