Difference between revisions of "User Migration"

(Add details on pop2imap)
Line 33: Line 33:
  
 
I used imapsync to migrate from a Cyrus IMAPd to Zimbra. The [http://www.linux-france.org/prj/imapsync/README ReadMe] lists a number of other IMAP servers compatible with imapsync.
 
I used imapsync to migrate from a Cyrus IMAPd to Zimbra. The [http://www.linux-france.org/prj/imapsync/README ReadMe] lists a number of other IMAP servers compatible with imapsync.
 +
 +
=== SSL ===
 +
 +
You can also do SSL version of imapsync, by calling the "imapsync-ssl" and providing "--ssl1" and/or "--ssl2" for each of the accounts you wish to migrate.
  
  
 
== Migrating from POP3 ==
 
== Migrating from POP3 ==
  
 +
pop2imap is a tool used to get a pop inbox and syncronise it to an IMAP folder. You can get it from [http://freshmeat.net/projects/pop2imap/]
 +
 +
It is very similar to imapsync above.
 +
 +
    pop2imap  \
 +
    --host1 some.pop.com.au --user1 yourAccount --passfile1 yourPasswordFile \
 +
    --host2 zimbra.imap.com.au --user2 yourZimbraAccount --passfile2 yourZimbraPasswordFile \
 +
    --folder MyOldPOPMail
 +
 +
Will copy the INBOX on your pop account to MyOldPOPMail folder.
 +
 +
There are some problems with pop2imap though.
  
 +
* It will not create the folder, you must have that manually created
 +
* It does not support SLL, however this is easy to do with "stunnel" - providing the SSL tunnel to the server
 +
* It downloads all of the messages first to get headers, although some pop servers do this well, many do not and this is a very time consuming operation. Modifications to the script are simple to skip this step and force a copy of the mail (technically no longer a sync, but a straight copy).
  
 
== Migrating from Exchange ==
 
== Migrating from Exchange ==

Revision as of 01:47, 4 April 2006

Migration from one mail system to another is often painful. It can result in a user having to look in two different places to find mail, or in the worst case mail disappearing.

Copying the contents of one mail system to another often seems like a good idea, that way if anything goes wrong at least the old mail is still available. Ideally you know exactly what you are going to do at the start, you move everything across, and then you kill the old mail system (or at least make it not visible from mail clients). That way users are not confused by having two sets of identical folders.

In reality you may have to learn on the job. After user data has been migrated to Zimbra, users can access their mail via the web client without any additional setup until their mail client has been configured to access the Zimbra server.


Bulk Creating the Accounts

The first step in migrating users is to create the accounts, this is a topic of its own at BulkCreate

Migrating from an existing IMAP server

Currently, the recommended method for migrating users to Zimbra from an existing IMAP server is with the imapsync tool written by Gilles Lamiral. The following guide to imapsync was originally posted to the forums by GertThiel:

Before you can use imapsync you must have both the source IMAP message store and ZCS up running and accessible to user accounts via IMAP. You can check that using an email client before starting the migration. You will need the login names (i.e. email addresses) and passwords for the users to be migrated. In addition, imapsync will not be able to authenticate to the Zimbra server until you enable clear text login for the IMAP service. You can set that option under the IMAP tab of the Global Settings or individual Server settings in the Zimbra Admin Console UI. Finally, consider that imapsync will be a heavy load on your CPU and memory; the system running the migration will be less responsive.

For this example my existing IMAP server is running on server.gtds.lan and I set up Zimbra on a new machine named zimbra.gtds.lan.

   imapsync --nosyncacls --syncinternaldates \
   --host1 server.gtds.lan --user1 yourAccount --password1 yourPassword \
   --host2 zimbra.gtds.lan --user2 yourZimbraAccount --password2 yourZimbraPassword

Of course the complete command belongs on one line (signified by the backslashes: \).

A slightly more secure method is to write each password into a seperate file, and then use the --passfile{1|2} options intead of the --password{1|2} options:

   imapsync --nosyncacls --syncinternaldates \
   --host1 server.gtds.lan --user1 yourAccount --passfile1 yourPasswordFile \
   --host2 zimbra.gtds.lan --user2 yourZimbraAccount --passfile2 yourZimbraPasswordFile

You may interrupt imapsync at any time with CTRL-C. Simply restart the same command again to resume the migration.

I used imapsync to migrate from a Cyrus IMAPd to Zimbra. The ReadMe lists a number of other IMAP servers compatible with imapsync.

SSL

You can also do SSL version of imapsync, by calling the "imapsync-ssl" and providing "--ssl1" and/or "--ssl2" for each of the accounts you wish to migrate.


Migrating from POP3

pop2imap is a tool used to get a pop inbox and syncronise it to an IMAP folder. You can get it from [1]

It is very similar to imapsync above.

   pop2imap  \
   --host1 some.pop.com.au --user1 yourAccount --passfile1 yourPasswordFile \
   --host2 zimbra.imap.com.au --user2 yourZimbraAccount --passfile2 yourZimbraPasswordFile \
   --folder MyOldPOPMail

Will copy the INBOX on your pop account to MyOldPOPMail folder.

There are some problems with pop2imap though.

  • It will not create the folder, you must have that manually created
  • It does not support SLL, however this is easy to do with "stunnel" - providing the SSL tunnel to the server
  • It downloads all of the messages first to get headers, although some pop servers do this well, many do not and this is a very time consuming operation. Modifications to the script are simple to skip this step and force a copy of the mail (technically no longer a sync, but a straight copy).

Migrating from Exchange

Migrating from Lotus Domino/Notes

Jump to: navigation, search