Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Collaborate all in one place by migrating your Box documents, data, and users to OneDrive, SharePoint, and Teams in Microsoft 365.
How does it work?
- Step 1: Connect to Box. Sign in to your Box account and add the Microsoft 365 migration app to your Box account custom apps.
- Step 2: Scan and assess. Add tasks for scanning. Once the scans are complete, download Scan reports to investigate any possible issues that might block your subsequent migration. You can skip this step in Box migration.
- Step 3: Copy to Migrations list. After a Box user is scanned and determined to be ready, add them to your migration list.
- Step 4: Review destination paths. Review destinations before migrating as destinations can't be modified once migration starts.
- Step 5: Map identities. Align your domain, users, and groups in the source with those domains, users, and groups in Microsoft 365 to ensure accurate migration of file metadata and permissions.
- Step 6: Migrate and Monitor. After reviewing your migration setup, migrate your Box accounts and monitor the progress.
Get started
To get started:
Navigate to Microsoft 365 Admin Center Home - Setup - Migration and imports. Select Box to create a migration project. Make sure that you have:
Access to the destination: You must be one of the following roles in the Microsoft 365 tenant where you want to migrate your content:
- Global admin
- OneDrive/SharePoint admin
- A user granted the "Microsoft 365 Migration Administrator" role
Important
Microsoft recommends that you use roles with the fewest permissions. Using lower permissioned accounts helps improve security for your organization.
Access to the source: Have Box account credentials that have Read access to any Box user account you plan to migrate.
Prerequisites installed: Make sure you have the necessary prerequisites installed.
Once a migration project is created, you can start connecting to the source as described in the next step.
Note
There are file size limitations and unsupported files in Migration Manager.