In Jan of this year we came out with tools to help migration IMAP mail to Exchange 2007. The tool can be found here: http://www.microsoft.com/downloads/details.aspx?FamilyId=35FC4205-792B-4306-8E4B-0DE9CCE72172&displaylang=en
Some tips for the tool. The first thing is to ensure you have permission for the mailboxes on the IMAP side. The Active Directory user used to perform the migration must have permission to impersonate the users to inject mail into their mailboxes. This permission can be set using an Exchange Management Shell command of the form:
Add-ADPermission –Identity 'DN_of_ClientAccessServer' ‑User 'domain\username' ‑ExtendedRights ms‑Exch‑EPI‑Impersonation
What the different parameters in the tool mean:
SourceIdentity: <This is the SMTP address of the person that is moving, and is used by the GUI to identify the row that is being processed and to find the target mailbox if you have not indicated another one in the CSV. >
SourceLoginID: < This is the login ID that is used to access the mailbox on the source system. >
SourcePassword: < This is used if a unique password is needed for each SourceLoginID >
SourceAdminCredential: <Note this cannot be passed through the CSV: This is used to open a mailbox based on the option 1 below >
How the different parameters are used for Admin Logins to an IMAP Server through the transporter:
Since different IMAP servers support administrative access to a user’s mailbox in different ways, it is important to understand how you support admin access to the user’s mailbox on the IMAP side. Here are the different options that we have found supported that work through the transporter.
1. Combined Admin/UserID Login Option
This is the default option in the tool and is based on how Exchange 2003 initially supported Admin login. Transporter will construct the login name for the source server based on SourceLoginId and the SourceAdminCredential as ‘AdminUsername/SourceLoginID’
For servers that support this login name format the user mailbox will be opened and can be migrated.
To configure this, the transporter needs just the following minimal set of data in the CSV
Your CSV will then be
And in the migration wizard, you can specify the Admin credentials.
2. Manually Combined Admin+UserID Login Option
We have found that other servers support a similar login with both the UserID+AdminName, however using a different format. In a IMAP sever, this login name combination worked ‘SourceUser*AdminUsername’. Since this is different the default way that the transporter combines the login IDs, this whole format needed to be included in the CSV for the source LoginID. In addition the admin password then had to also be provided in the CSV.
For servers where a combined Admin+UserID login was needed that was different than Exchange 2003 format the following worked.
Minimal CSV parameters
>> Note again that the SourceLoginID that the userID and AdminID was combined based on how the source IMAP server supports admin login.
When you run the migration wizard select “Use individual account credentials” since the admin ID/Password is already in the CSV
3. SourceRootFolder Option
Finally some IMAP systems allow administrative access by logging in as administrator and accessing mailboxes using the mailbox relative to the root folder.
To use this feature of transporter you can specify in your csv the AdminUserID in the SourceLoginId plus you then need to indicate what the SourceRootFolder is that you need to migrate. Note that NO passoword is required in this, since you can enter the password during the wizard. The SourceRootFolder should be the path to the mailbox you need to access and will be unique based on your server.
For servers using the SourceRootFolder Option
Sourceuser2@domain.com,CS050, AdminUserName , ~/mail/SourceUser02
And in the migration wizard, you can specify the Admin credentials. Again, please do ensure your administrator has proper access rights to the other user’s mailbox.
How can I determine the root folder path of my IMAP server? Thanks.
Any ideas on if this will work with Exchange 2003?
just wanted to shout out some thanks, I may be blind but your blog had the only reference I could find anywhere to the 3 different authentication types
If you want to avoid all these complex configurations, you should try: http://bit.ly/eskrY5
It solved my Exchange migration in a matter of minutes!