It’s very common to see, in Public Folder migrations, customers that want to migrate and transform that data. But how exactly is that done?
If you’re familiar with MigrationWiz, you’ll know that to migrate data all you have to do is follow some simple steps, like configuring access to source and destination, creating the migration project and defining, within the project, what’s the source and the destination.
The steps above are as simple as they sound, however, to transform data, you’ll need to do some advanced configurations. MigrationWiz gives you flexibility that probably no other tool does, by allowing you to filter or map (I’ll elaborate in a second), which are the foundation features to transform data, but to do so properly, you need to configure your project accordingly.
So how exactly should you configure a project, to migrate a Public Folder calendar into a mailbox calendar?
I won’t give you details about the basic steps to create a project, you can look for the migration guides in the BitTitan HelpCenter, but basically you need to create a normal Public Folder project and do some changes to it.
The first and more basic change you need to do is to set mailbox as a destination.
Within the advanced options of your MigrationWiz project, go to the Destination settings and select “Migrate to Shared Mailbox”.
Now that you have your destination defined, add the Calendar Public Folder that you want to migrate, to your MigrationWiz project, and the correspondent destination mailbox address.
So now that you have your 1:1 matching done in the project, can you migrate? The answer is no, but lets see what happens if you do.
What you are seeing above is the PowerShell output that lists all folders, after the migration, for the destination mailbox. So what happened?
Basically instead of putting all data into the default calendar folder at the destination, we created 2 new folders, of type IPF.Appointment (Calendar folders), in that mailbox.
What this means for the end user is that he will see 2 new calendars, “Folder1” that will be empty since it had no calendar data at the source and “MyCalendarFolder1” that will have all data. Additionally the default Calendar folder won’t have any migrated data.
The above is rarely the intended goal, so just migrating is usually not the solution. You’ll need some additional configurations. Lets get to it.
Edit the line item you added previously and in the Support options add a Folder mapping.
The regex in this folder mapping basically moves all source data to the destination folder called “Calendar”. Since the mapping is in place and it has a defined destination, we no longer create any folders in the destination. It’s also the mapping that makes all data be copied into that destination folder.
So with the configuration above all data will be into what eventually would be the folder you want. If you adjust the filter you can put it in whatever folder you want, having in mind that if the folder doesn’t exist we will create it.
Hope that helps and happy migrations!!