Whichever version of Exchange you’re running, you already know that Sherpa’s Mail Attender is a powerful tool for managing an Exchange environment. Were you aware that Mail Attender can also be used to perform public folder migrations? While Microsoft offers a mechanism for migrating public folders, Mail Attender simplifies the process while also adding versatile filters enabling  the user to set conditions over what content is actually moved.

Access to public folders (both legacy and modern formats) is accomplished by initiating a MAPI session. In Mail Attender, the first task in the migration process is to define the various profiles that will be used to access the public folder tree. Typically, there will be two of these profiles for each user – one for the user’s ‘old’ public folder tree and one mapping to their Ex2013 public folders.

rick1
After the access account is defined, the migration process is controlled by creating a Mail Attender rule. Presumably, there is at least one rule for each user. In this example,  a profile mapping to an Exchange 2007 public folder tree is selected as the ‘source’ for the data transfer.
rick2
On the ‘Folders’ tab, the rule can either default to ‘All Folders’ (the entire tree), or the ‘Browse Public Folder’ button can be used to select a portion of the tree to migrate. In this example, the selected option accesses only a specific folder labeled ‘Accounting’ (along with its subfolders):
rick3
The ‘Rule’s Conditions’ tab allows you to specify message selection criteria – for example, choosing the option for the program to disregard any message in the folder  more than five years old. Of course, this added condition is optional.
rick4
The action that all qualifying messages will take is defined on the Actions tab. In this example, the option to copy qualifying messages to another public folder has been  selected (there is also an option to move these files). By clicking the ‘Edit’ button, we see the properties of the operation. Also in the above example, we see a profile that maps to an Exchange 2013 modern public folder tree, specifying the Exchange Server and folder path (what folder the messages will be placed in when they are copied). A variable picks up the current  folder (in this case Ex2007) and copies the message to an identical location in the output public folder.
rick5

At this point, the rule is prepared- it would then typically be scheduled to run, and the messages would be copied from the source Exchange 2007 public folders into the modern Exchange 2013 public folder destination.

[hs_action id=”4086″]