Shulou(Shulou.com)06/02 Report--

At present, many domestic enterprises gradually provide a modern office environment for their internal employees with the help of Microsoft 365 solution, which is not limited to improving the cooperative office efficiency between enterprise branches and meeting the needs of cross-platform mobile office, but also reduces the IT infrastructure investment and management costs for enterprises.

However, with the expansion of enterprise business model, many enterprises need higher standard Office 365to meet their business needs, so there will be a lot of Office 365Tenant to Tenant data transfer projects, but data migration is not an easy thing, there are many points to consider, at the same time, it is very important to make a reasonable analysis of the source data structure and develop efficient Migration Plan.

Here to share a real case, hope to help you in the future data migration work.

Case background: several months ago, Partner (Digital Star) contacted our company through Century Interconnection, hoping to help complete the cross-Tenant data migration of Office 365 of a domestic AI technology company. the immediate problem for customers is: the current Office 365 subscription license is about to expire within a month, and it is necessary to complete the data migration of 2500 User Seats OneDrive for Business and Office Groups in this period of time, so that the destination end is online and the source side is disabled to save cost.

Due to time constraints and heavy tasks, customers cannot affect end user's continued access to and use of the current Office 365 subscription platform during the migration process, so the challenges should be considered in advance to ensure a reasonable Migration Plan to complete the migration task within an effective time.

After confirming and collating the information with Partner and various engineers, the migration challenges are as follows:

In the process of data migration, end users access to the source side is not blocked, indicating that customers will always generate new data or changes to old data on the source side before the new Office 365 subscription is launched. Customer source contains many custom domain names + Microsoft default domain name data volume: 2.5 TB

To ensure efficient data migration, we will take 6 steps to complete the customer's 3-week relocation process:

Use AvePoint FLY to analyze the data structure of the current Office 365 data platform, as shown in the following figure:

Customize the Migration Plan based on the analysis results, as shown in the following figure:

To ensure the permissions and the correct transfer of Office 365 Groups, select the AvePoint FLY tool and complete the mapping of the custom domain name, as shown below:

Use the AvePoint FLY tool to complete all the data relocation and subsequent incremental relocation, as shown in the following figure:

Validation for data relocation.

In the project, other configuration instructions for FLY tools are as follows:

Supports batch generation of migration mappings, greatly reducing migration configuration time. 3-5 Job can be executed concurrently, greatly reducing the cycle of data migration. It is not a SasS tool. It can be deployed on a local Server without consuming the resources of Azure or other cloud platforms. Full Migration and Incremental Migration are supported. Support Migration job pause, continue, rerun. Where rerunning supports restoring only the files that failed last time. Support judgment processing when data conflicts occur, such as choosing whether to overwrite or skip processing according to last modified time. Support migration Dashboard function, migration status and migration progress at a glance.

If you are interested in the migration project, please feel free to contact me for details.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.