Box and Dropbox for Business Migration

CloudM Migrate can be used to migrate Box or Dropbox for Business files to Google Drive, Microsoft OneDrive or SharePoint.  Folder structures, files, timestamps and file ACLs can be transferred to the destination system along with many other features. The sections below describe how to migrate files from Box or Dropbox for Business to Google Drive or OneDrive/SharePoint.

First choose Box/Dropbox as the migration source platform.

To migrate files to Google Drive, check the Drive checkbox for each user.

All of the files within the specified folder will be migrated into the user’s Google Drive.  Various choices are available as to how folders are migrated: files and folders can be migrated to the same folder structure as the file system; files can be migrating into a single collection; a combination of both can be done; or no structure at all can be applied.  See the settings in the Google destination platform settings for more information.

To migrate files to OneDrive/SharePoint, check the ‘Drive’ checkbox for each user.

If migrating to ‘Team Sites’ see Migrating SharePoint Team Sites

One other setting is required before migrating to OneDrive, which is the ‘SharePoint Admin URL’ setting in the destination platform server settings. This URL is required to determine the location to perform the required admin tasks as part of a migration.

All of the files within the specified folder will be migrated into the user’s OneDrive or Team Site. The folder structure of the file system will be preserved during a migration.  See the Office 365/OneDrive destination platform settings for more information about other options.

It is possible to migrate file/folder ACLs and this should be turned on via ‘Box Document Sharing’ in Box migration settings or ‘Dropbox Document Sharing’ in Dropbox migration settings. Note that when migrating to OneDrive, email notification is not available.

Box permissions (ACLs) are always stored on the file as email addresses. To migrate them to either destination system, CloudM Migrate must map them to email addresses. If an ACL cannot be mapped to an email address (by any means) then no ACL is added in the destination account.

Various ways are provided to map Box/Dropbox for Business permissions to email addresses:

• When the ACLs are processed, CloudM Migrate uses the address replacement schemes to map to possible email addresses:
  • If an entry has explicitly been specified in the ‘Address Replacements (File)’ option in the Address Replacements settings then it will be explicitly mapped according to the provided mappings. 
    • For example, if you want to map an permission of john@example.com to another email address, the CSV file should contain an entry of john@example.com, steve@example.com
    • Groups should be replaced as follows (without quotes) 'Dropbox Group Name', destinationgroup@example.com
• If the resolved permission is an email address and not been explicitly mapped via a CSV then the domain name will be replaced according to the ‘Address Domain Replacements’ options and the name part of the email will be mapped according to entries on the user tab.
  • For example: The original ACL is john@domain.com
  • ‘Address Domain Replacements’ included a mapping from domain.com to example.com
  • On the user tab there was a row with an export name of john and an import name of john.smith
  • The final ACL email address will be john.smith@example.com