This guide will show how to configure Box as a source configuration
For Box this is defined by the following requirements:
- Creating a Box Application for a Client ID and Client Secret Key
- Box Application Source Steps
- Migrating to Google Workspace Section
- Migrating to Microsoft 0365 OneDrive/SharePoint Section
- Address Replacement Reminder
Creating a Box Application for a Client ID and Client Secret Key
- Log into your Box account as an administrative user for your organization: https://app.box.com/developers/console
- Navigate to Dev Console.
- Navigate to My Apps.
- Select Create New App.
- Select Enterprise Integration.
- On the Authentication Method screen, select Standard OAuth 2.0 (User Authentication).
- Give your application a name such as ‘CloudM Migration’.
- In the section OAuth 2.0 Credentials copy the Client ID and Client Secret Key values.
- Update the Redirect URI field with the below URL: https://oauth.pingone.com/ocs/ppm/rest/v1/oauth/oastempcredresponse/
- Select Save Changes.
Enabling Enterprise FeaturesAfter creating a Box application, you will be required to email Box support to enable the following features:
- Box Notifications
- Go to the Box support area of the website and create a new ticket.
- You will be prompted to login if not already logged in and you should sign in using a BOX Admin account.
- A dialog window may appear. Click continue.
- In the support form that you now see, enter the following details:
- What can we help you with? - 'Developer/API Issue'
- Briefly summarize your issue / question? - Suppress Notifications scope.
- API Key - In this field, enter the client_id you made a note of when creating a Box.com application.
- Give us more details - Please enable the Suppress Notifications scope for our app.
- Priority - Normal
BOX Developer Console
- Ensure that the "Make API calls using the as user header" checkbox is checked.
Box Application Source Steps
Steps to take and enter account details in the source platform area.
- Client ID - the client id that is generated by Box when creating a Box application.
- Client Secret - the client secret generated by Box.
- Redirect Uri - https://<domain_you’re_using>/api/boxexport/callback
- Admin Email - the Box Enterprise administration email address used to login into Box.
- Test User Name - login email address of a non-admin user within the system to test. This user must have the active status in Box.
- Authorization Code - the authorization code is generated when following the OAuth2 process.
Migrating to Google Workspace Section
When migrating files to Google Drive, check the Drive checkbox for each user. Please refer to the Google Tenant Configuration
Select on Add items to migrate and select Add Shared Drive from the dropdown menu. Specify the ID of the Shared Drive to migrate from in Export Name. Also specify any folder within a Shared Drive. This is done by specifying the folder ID in the Documents Path field. Make sure the migrating account has Manager permissions for any Shared Drives that are being migrated.
To migrate files to a Google Workspace Shared Drive.
Either select the item you wish to migrate and select Migrate as Shared Drive from the actions menu, or specify the import type as Shared Drive when adding an item. Specify the ID of the Shared Drive in the Import Name field or the name of the Team Drive in the Given Name field. If the Shared Drive specified doesn’t exist, then it will be created.
- Enter a unique ID in the Import Name field to identify the Shared Drive across multiple migrations.
- Enter a specify a specific folder to migrate from in the Documents Path field, and this will migrate only the specified folder and all subfolders.
- Enter specify a specific folder to migrate to in the Documents Destination Path field. Documents will be migrated to the specific subfolder in the Shared Drive.
Ensure the account has Manager permissions for any Shared Drives that are being migrated. Configure multiple Managers to perform the migration with the configuration settings. To improve performance to Shared Drives success.
Migrating to Microsoft 0365 OneDrive/SharePoint Section
When migrating Microsoft as the destination, Please follow the 0365 Configuration
Migrating files to Microsoft 365 OneDrive/SharePoint, Only use the Sharepoint Admin URL. The URL will look similar see example.
https://tenant-admin.sharepoint.com.
To input the URL, click Advanced Settings and locate SharePoint Admin URL under the One Drive for Business/SharePoint settings. Once entered and configured in Platform settings, click on Next. CloudM Migrate will now perform a small connection test to verify that the details entered are correct which check in green.
If this fails validate the information has been entered correctly.
Address Replacement Reminder
If changing email addresses as part of the migration verify that the domain names are correct. Also specify Address Replacement in the respective section of the advanced settings.
Target Audience permissions can also be migrated but must be replaced using Address Replacements in order to migrate successfully. If present on the source but not migrated to the destination platform, any items shared with it will be shared back to the source Target Audience.