User Migration: Difference between revisions

No edit summary
No edit summary
 
(300 intermediate revisions by 46 users not shown)
Line 1: Line 1:
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.
{{BC|Community Sandbox}}
__FORCETOC__
<div class="col-md-12 ibox-content">
=User Migration=
{{KB|{{Unsupported}}|{{ZCS 8.0}}|{{ZCS 7.0}}|}}
{{WIP}}


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.
{{Archive}}{{WIP}}


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.
First, note that you'll want to create accounts in Zimbra first before you do the migration. If you want to do it in one shot, read [[Bulk Provisioning]].


Migrating your users means you're going to have to deal with [[Mail Migration|mail]],  [[Calendar and Contacts Migration|calendar, contacts]]  and [[Password Migration|passwords]]. This page used to be one monolithic monstrosity -- but has now been broken down into separate pages:


== Bulk Creating the Accounts ==
* [[Mail Migration]]
* [[Outlook NK2 Cache Rebuild]]
* [[Calendar and Contacts Migration]]
* [[Password Migration]]
* [[Email Rules Migration]]
* [[Aliases file Migration]]
* [[Migrating_from_Postfix_and_MySQL_with_bash|Postfix+MySQL aliases and accounts migration]]
* [[Migrating_from_Dovecot_passwd_with_bash|Migrating from Dovecot passwd]]
* [[Zimbra to Zimbra Server Migration]]
* [[Prevent duplicates messages for POP3 users post migration]]


The first step in migrating users is to create the accounts, this is a topic of its own at [BulkCreate]
Please see [http://wiki.zimbra.com/index.php?title=User_Migration_Troubleshooting User Migration Troubleshooting] if you are having problems migrating data to your Zimbra installation.


== Migrating from an existing IMAP server ==
[[Category:Migration]]
 
{{Article_Footer|Zimbra Collaboration Suite 7.0|3/7/2006}}
Currently, the recommended method for migrating users to Zimbra from an existing IMAP server is with the [http://freshmeat.net/projects/imapsync/ 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 [http://www.linux-france.org/prj/imapsync/README ReadMe] lists a number of other IMAP servers compatible with imapsync.
 
 
== Migrating from POP3 ==
 
 
 
== Migrating from Exchange ==
 
 
 
== Migrating from Lotus Domino/Notes ==

Latest revision as of 03:11, 11 July 2015

User Migration

   KB 1340        Last updated on 2015-07-11  




0.00
(0 votes)



First, note that you'll want to create accounts in Zimbra first before you do the migration. If you want to do it in one shot, read Bulk Provisioning.

Migrating your users means you're going to have to deal with mail, calendar, contacts and passwords. This page used to be one monolithic monstrosity -- but has now been broken down into separate pages:

Please see User Migration Troubleshooting if you are having problems migrating data to your Zimbra installation.

Verified Against: Zimbra Collaboration Suite 7.0 Date Created: 3/7/2006
Article ID: https://wiki.zimbra.com/index.php?title=User_Migration Date Modified: 2015-07-11



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »


Jump to: navigation, search