The information to migrate to or from a Dropbox instance is laid out in each of the scenario-specific guides in this section of the Help Center. However, this article provides some information and answers to general questions that may help you perform a smooth, successful migration.
Due to the latest Dropbox update, admin access is no longer automatic. Moving forward, to have access to a team folder by default, you will need to add yourself to the folder from the admin console. Admins will always have access to all team folders in the admin console on the Team Folders page.
Limitations & Requirements
- MigrationWiz does not support the migration of Dropbox Teams Folders at this time except through the use of advanced options. Please see the section below if you intend to migrate team folders.
- MigrationWiz currently does not support migration for new Team Space in Dropbox.
As per Dropbox help documentation, ‘Some teams have access to the new team folder structure. If you see a purple folder icon with one person on it on dropbox.com, you have the new team space.’ - Google Drive to Dropbox migrations do not support user mapping. Please ensure the user names of the source and destination users match for the correct permissions to be migrated accurately.
Migrating the Team Folders
Team folders are a feature of Dropbox Business that allows admins to create folders that are instantly shared with all members of their team or organization. However, unlike standard shared folders, team folders don't have an owner assigned to them in Dropbox, and so they are not migrated by default as part of a document migration project. Additional steps beyond the basic project configuration are required to migrate Dropbox team folders. Read the Team folders: an overview article from Dropbox to learn more about team folders.
Migrate team folders from the Source
Add the following support options at the project level to define a team folder owner for the document migration project.
ShouldMigrateSharedWithMeFolderAsSource=1TeamFolderOwnerEmail=AdminEmail
- Replace "AdminEmail" from the example above to the email address for an admin account, preferably the admin account used for the project's Dropbox endpoint.
The admin account (email address) defined as the team folder owner must also be an item being migrated within the document migration project.
Some team folders are not shared with an entire organization. Only team folders that the defined team folder owner has access to will be migrated. If you want all team folders within a Dropbox Business account to be migrated, then ensure that the defined team folder owner has access to all team folders for that account.
If you migrate team folders from a Dropbox Business account to another Dropbox Business account with this support option, the folders will be standard unshared folders at the Destination. If you prefer for the team folders from the Source to also be team folders at the Destination (i.e., when migrating from Dropbox to Dropbox), then use this support option with the FolderMapping support option outlined below.
Example: TeamFolderOwnerEmail=support@bittitan.com
Migrate into team folders at the Destination
Create the team folders in the Destination before starting the document migration project. Add the following support option at the project level to map a folder in the Source to a preconfigured team folder in the Destination.
FolderMapping="^{%escape%}//Folder1->{%escape%}//TeamFolder1"
- Replace the {%escape%} portion of syntax in the above support option with the root folder for the Source and Destination environments.
- Replace "Folder1" from the example above to the team folder name at the Source, and change "TeamFolder1" to the team folder name at the Destination.
Use this support option with the TeamFolderOwnerEmail support option outlined above. MigrationWiz needs to account for an owner even if the Destination team folders will not have an owner assigned to them when the migration is complete.
Dropbox Folders with Bidirectional Text
- Filtering the folder as described in this article.
- Renaming the folder to avoid any bidirectional text in the folder name.
Dropbox Folder Mapping
This guide covers folder mapping from Dropbox at the root level to a specific subfolder at Dropbox as a destination.
When you are migrating folders to or from Dropbox, a very specific syntax must be used. The full Advanced Option for folder mapping is to be entered as the following:
FolderMapping="^{%escape%}/(.*?)$->{%escape%}//newhome$1"
When you are discovering folders from a Source Dropbox root level to map to a new location at the Destination, the forced escape clause must be used:
"^{%escape%}/(.*?)$
This will capture any files from the root level, matching any string, while matching the end of the string. It is important to capture files at the root level of the Source Dropbox Account, as well as capturing the top-level folders together.
To map the files to a specific sub-older at a Dropbox Destination, use the following:
->{%escape%}//newhome$1"
This mapping allows a new folder "newhome" to be created while maintaining the folder structure from the Source, including mapping the files stored in the root folder at the Source to this subfolder at the Destination.
Rename the "newhome" part of the folder mapping to your desired folder name for the Destination.