• Imapsync – migration of e-mails ideal for implementing a two-phase migration of e-mails needs to track on which server the first migration tool place, so imapsync cache information is present! - imapsync cache implies one file for each mail(!) XFS with inode64 mount option no “/” in mail folder names those are invisible to IMAP.
• Finally, consider that imapsync will be a heavy load on your CPU and memory; the system running the migration will be less responsive. Imapsync may run faster and consume less CPU with larger I/O buffers, but no benchmarking of this has been performed.

• Imapsync Massive Migration Update
• Imapsync Massive Migration Download
• Imapsync Massive Migration Tool
• Imapsync Massive Migration Software

Imapsync is a tool for facilitating incremental recursive IMAP transfers from one mailbox to another. It is useful for mailbox migration or backup, and reduces the amount of data transferred by only copying messages that are not present on both servers. Read, unread, and deleted flags are preserved, and the process can be stopped and resumed.

I've got about 2500 users from about 40 UNIX mail servers to be migrated to a couple of beefy Dell Servers running RHEL5. It is not feasible to reset their passwords. We are scripting the moving process. For the migration, we've got boxes set aside that will do all of the crunching. The Zimbra servers just have to accept the incoming imap connections from imapsync.
On the UNIX boxes, we are manipulating the shadow file, so we can get in there and get the mail, no problem. The new Zimbra boxes are authenticating off of our AD. We have to do our migration in stages (just because of the sheer numbers here, I'm talking TB, not GB of mail between the new servers). After the first migration, the first box will be live with users while we import in more (I know, crazy, but we are under a gun here). We have to minimalize the impact to the users.
I can not manipulate the authentication once Box1 goes live, so we can't just turn off the AD authentication to can use local authentication. As we know, Zimbra will not allow for multiple authentication sources (local and AD, etc.)
Because we have a mixed environment, our users can, and usually have, separate passwords for the UNIX world and the Windows world, so shadowing their login's on the UNIX boxes won't necessarily work. (this will be coming to an end soon too)

Imapsync Massive Migration Update

Here's what I have discovered:
If I set an account to be an administrator, it can use both local and AD Auth, so I know it has kept the password that I set when I batch created the accounts using zmprov.
Here's what I want to know, can I:

Imapsync Massive Migration Download

Batch change accounts to be administrator accounts (dangerous, but needed) and then batch change them back. I haven't found this documented anywhere.
or
On the command line force Zimbra to look at either the local password store or AD Auth until our migration is over and then we will turn it back to AD only.

Imapsync Massive Migration Tool

Our only other option is to sit at the admin web gui and hit clicky boxes on every account before and after the migration.
Please help me Obi Wan Kenobi, you are my only hope. (yeah, I know, we are probably screwed)

Imapsync Massive Migration Software

Thanks in advance!