The following article will outline the necessary steps for migrating from Box to Microsoft 365.
Create your project
The following steps will guide you through the process of creating your project and establishing the necessary connections where applicable.
- From the Projects page, click on "Create project".
- Enter a name for your project, and click on "Continue".
- Select Box as your source platform or choose an existing Box connection.
- Follow the instructions in the article below to complete the setup of your source Box connection.
- Once you have completed the source setup, you will be prompted to select your destination.
- Select Microsoft 365 as your destination platform or choose an existing Microsoft 365 connection.
- Follow the instructions in the article below to complete the setup of your destination Microsoft 365 connection.
- Upon completing the destination setup, you will reach the summary and project finalisation page. This page will provide a summary of the project you are about to create.
- Click on the "Create project" button to create the project.
- You will now be presented with the Project page where you can begin adding your migration batches.
Additional information on creating projects can be found in the article below.
Licensing your project
If you are using Migrate Self-Hosted, once the project is created, you will need to ensure it is licensed. To do this, follow the steps below.
- Click on the license pill in the top right hand corner.
- Enter your license key and click on "Apply".
- Once you have validated the license, click on the "Close" button. The pill should then show as below.
The license key provided should relate to the domain name of your destination connection.
Adding your migration batches
Once you have created your project and ensured it is licensed, the next step is to add a migration batch.
The below article explains how to add migration batches.
When migrating from Box to Microsoft 365, the User entity type is the sole available option. This entity type facilitates the migration from a designated user within the source Box tenant. Generally, during migration to Microsoft, files are migrated to either a User or a SharePoint site. The below articles explain in more detail how to configure a batch for these scenarios.
Migrating Box Users to Microsoft 365 Users
Migrating Box users to Microsoft 365 SharePoint Sites
Configuring your migration batch
Upon adding the items you intend to migrate to your batch, clicking 'Next' will advance you to Step 2, the configuration stage of the migration batch. At this stage, you can adjust the General, Source, Destination, and Advanced settings for your batch.
For more detailed information on each of the settings pertinent to your project, please refer to the articles listed below.
Microsoft 365 - Destination Settings
The necessary settings may vary based on the entity type and the stage of the migration process. We recommend reviewing the links in the previous section to identify the specific migration scenario you are encountering and ensure the settings are appropriately configured.
Readiness Scan
Unfortunately, the readiness scan is not supported when migrating from Microsoft 365 to Microsoft 365. You may skip this step to continue with the migration process.
For further information regarding the functionality of the readiness scan, please refer to the article below.
Summary
Upon completion or bypassing of the readiness scan, you will be directed to the migration batch summary page. This page provides a comprehensive overview of the migration batch you have configured.
The summary will encompass the following details:
- The source and destination platforms.
- The source and destination domains.
- The number of items being migrated.
- The date filters selected for various data types.
- Status of the readiness scan.
- Details of your license. If a license has not yet been added, you may click here to add one.
If you are satisfied with the information presented on the summary page, you may click on Start to initiate the migration.
Additional options are available in the Start dropdown menu:
- Schedule migration.
- This option is available exclusively for self-hosted environments and allows you to schedule a migration to occur at a specified time.
- Start migration for failed users.
- If you have previously executed this migration batch and encountered user failures, this option will initiate the migration for only the users who failed.
Progress
During the migration process, you may monitor its progress through the progress page. This page provides an overview of the migration status as well as the status of each individual item selected for migration.
The article below offers more detailed information about the data available on this page, along with the actions that can be taken.
Upon completion of the migration, you can access the report history from this page by clicking the "View report history" button. This feature allows you to download reports and review the progress of both current and previous migrations for this batch. Further details are provided in the aforementioned article.
Delta Migrations
In the majority of instances when executing a migration project, it is necessary to perform a delta migration. The Migrate tool permits the execution of multiple delta migrations for the licensed items within your batch as required.
To execute a delta migration, you must ensure that the configuration aligns with your requirements and start the migration process once more. To enhance the performance of these delta migrations, Migrate retains a migration history. The following article offers further details on this subject.
Reporting
In addition to accessing the report history from the progress page, you can also access migration archives within the view of your project. To do so, click on the ellipsis located on the right-hand side of the migration batch, then select the "View archives" option.
This action will redirect you to the migration archive page. Here, you can view statistics and download reports for previous migration passes. Additionally, you have the option to modify the labels of these archives or delete them if necessary.