Folder Mapping in MigrationWiz

Use the folder mapping support option to map a Source folder to a Destination folder. For example, when you want to map the "Inbox" folder on the Source to an "Old Inbox" folder on the Destination in a mailbox migration.

The folder mapping support option uses regular expression (regex) and is added to the Advanced Options screen for individual items or for an entire migration project, which applies to all items in the migration project. This article provides detailed information about using the folder mapping Support Option for mailbox migrations and some examples of how the folder mapping support option can be modified to work for you.

 

Add folder mapping for a migration project

Follow these steps to add folder mapping to a migration project, which applies to all items in the migration project:

  1. From the MigrationWiz dashboard, click on the migration project that will have the folder mapping added.
  2. From the migration project page, click Edit Project and then select Advanced Options.
  3. In the Support Option section, add this support option:
    FolderMapping="^SourceFolder->DestinationFolder"
    Note: Replace "SourceFolder" and "DestinationFolder" with the names of the folders in the Source and Destination environments.
  4. Click the "+" sign to add the folder mapping.
  5. Click Save.

 

Add folder mapping for an individual mailbox

Important: If you are migrating an entire mailbox into a single subfolder of a Destination mailbox, then you must add additional advanced support options for calendar and contact items. Otherwise, you'll experience problems accessing migrated items at the destination. Read the Can I migrate a Source mailbox into a single subfolder of a Destination mailbox? article for additional instructions.

Follow these steps to add a folder mapping to an individual item in a mailbox migration project:

  1. From the MigrationWiz dashboard, click on the migration project that contains the item that will have folder mapping added.
  2. From the migration project page, find the item that will have folder mapping.
  3. Click the Edit icon (pencil icon) on the right side for that individual item to open its Advanced Options.
  4. In the Support Option section, add this support option:
    FolderMapping="^SourceFolder->DestinationFolder"
    Note: Replace "SourceFolder" and "DestinationFolder" with the names of the folders in the Source and Destination environments.
  5. Click the "+" sign to add the folder mapping.
  6. Click Save Item.

 

Folder mapping examples

Here are a few examples of folder mapping commands and processes, along with special notes for those specific mappings.

  1. FolderMapping="^Sent Emails->My Sent Items" This maps the "Sent Emails" folder to a folder named "My Sent items". 
  2. FolderMapping="^Inbox->Managed Folder" This maps the "Inbox" folder to a folder named "Managed Folder".
  3. FolderMapping="^.*$->DestinationFolder" This maps all files across all source folders into a single folder on the Destination.
    Notes: 
    • Replace "DestinationFolder" with the name of the folder in the Destination environment.
    • ^.*$: Is the regex version of "Select All". (^) Match beginning of string; (.*) Any characters; ($) Match end of string. 
  4. FolderMapping="^Documents->Documents/DestinationFolder" When migrating to OneDrive there is a hidden root level folder titled Documents.  This mapping this will map everything being migrated to the defined Destination folder, which will appear as a top level folder within OneDrive
    Note: Replace "DestinationFolder" with the name of the folder in the Destination environment. 
  5. FolderMapping="^->DestinationFolder/" This maps everything from the root level down into a single folder on the Destination, while maintaining the folder hierarchy within the Destination folder. Be sure to add the / (forward slash symbol) at the end of the folder name to tell MigrationWiz to create a new subfolder under that Destination folder. Be careful with this, as it will map system folders as well as regular folders (such as Google Drive's "Permissions" folder). WARNING: If migrating a mailbox to a specific Destination folder, this command can cause items to become inaccessible due to the order of migration.  See the Can I migrate a Source mailbox into a single subfolder of a Destination mailbox? for the correct folder mapping for a Destination subfolder scenario.
    Note: Replace "DestinationFolder" with the name of the folder in the Destination environment. 
  6. FolderMapping="^Floor 5-A5-8-T4-\(AV\+TC\)->Calendar" This maps the "Floor 5-A5-8-T4-(AV+TC)" folder to the "Calendar" folder. The part to the left of "->" is regex, so special characters need to be escaped. In the above example, the special characters are escaped with a back slash before the special characters.
      

Additional information about folder mapping

The Source folders may be different (at the API level) from what is displayed in the user interface or Outlook. Therefore, when defining the folder mappings, pay special attention to the exact format of the folder name (e.g., [Gmail]/Sent for Sent).

We recommend that you use Regex Hero to test your regular expression code.

{%escape%}is a reserved word that must be avoided when creating folder mappings. If original folder names in the Source end with {%escape%}, they must be manually renamed before migration.

 

G Suite (GMail API) Limitations

For ‘GSuite (Gmail API) to GSuite (Gmail API)’ migrations only:

If you want to map multiple source labels into a single label on the destination, then the parent destination label must be created before starting the migration.

Example: If you wish to map three Source labels ('ABC', 'PQR', and 'XYZ') into one parent label ('DestinationLabel') at destination then you must create the parent label ('DestinationLabel') at destination mailbox before running the migration.

Was this article helpful?
0 out of 0 found this helpful