Released under GNU General Public License v3 (GPL-3)

This script is free for anyone to use and can be distributed freely

You are solely responsible for adequate protection and backup of the data and equipment used in connection with any of this script, and we will not be liable for any damages that you may suffer connection with downloading, installing, using, modifying or distributing such script.

The script allows you to migrate emails, account passwords, domains, contacts, calendars, briefcases, auto-responders, filters, forwarders, aliases, distribution lists, legal intercepts, preferences, share settings of folders and signatures between Zimbra installations. This script has been tested on 8.8.15 and allows you to transfer between Zimbra instances on different operating systems and different Zimbra versions. So in theory you can migrate from Zimbra 8 to 9 using this script.

We just added the export and import of shared settings; so that shared calendars, briefcases, contact groups can now be migrated.

So this script allows you to migrate from Centos 6 to Centos 7 or Centos 8; or from Centos to Ubuntu and between different versions of Zimbra.

There is an export script for exporting all of the data (export_zimbra.sh) which needs to be run on the server that you are migrating from and one for importing the data into the server that you are migrating to. The script is written in bash.

There is an import script for importing into another Zimbra instance (import_zimbra.sh) which should be run on the new Zimbra server that you will be migrating to.

There is an import script for importing into a Carbonio server (import_carbonio.sh) which should be run on the new Carbonio server that you will be migrating to.

We recommend that the 2 scripts be put in /opt/scripts/. Before they can be run they need to be executable. export_zimbra.sh should be run on the server you are migrating from and will output all of the data to /opt/zmbackup/. Important to note that emails will not be exported as it would occupy too much storage. Instead emails are migrated using imapsync.

When running export_zimbra.sh and import_zimbra.sh make sure that Zimbra is running.

To use:-

To export Zimbra (To be run on the server that you are migrating from) - run as root

cd /opt/
mkdir scripts
cd scripts
wget https://raw.githubusercontent.com/hodfords/zimbra-migration/main/src/export_zimbra.sh
chmod 755 export_zimbra.sh
./export_zimbra.sh

Once all the data has finished exporting - you can import on the new Zimbra server - run as root

cd /opt/
mkdir scripts
cd scripts
wget https://raw.githubusercontent.com/hodfords/zimbra-migration/main/src/import_zimbra.sh
chmod 755 import_zimbra.sh
./import_zimbra.sh 111.222.333.444

Once all the data has finished exporting - you can import on the new Carbonio server - run as roo=t

cd /opt/
mkdir scripts
cd scripts
wget https://raw.githubusercontent.com/hodfords/zimbra-migration/main/src/import_carbonio.sh
chmod 755 import_carbonio.sh
./import_zimbra.sh 111.222.333.444

111.222.333.444 is the server address containing the export data and the server you are trying to migrate from.

• imapsync
• ability to run bash scripts
• cut
• rsync
• Zimbra should be running when you run the scripts
• sed
• cat
• stat

• During the export and potentially the import process - if your calendar has a lot of entries then Zimbra times out and the export process does not output the calendar at all. This blog has a lot of really useful information:- https://www.anahuac.eu/zimbra-to-carbonio-z2c/

And this might resolve the export and import issues.

su zimbra
zmlocalconfig -e socket_so_timeout=99999999
zmlocalconfig --reload

• For very large mailboxes (in terms of the number of messages) if you encounter imapsync returning the "Killed" response and other error messages like "uninitiliazed value $h1_msgs[0] in hash slice at /usr/bin/imapsync lin 2558" or something like that then it means your server has run out of RAM during the migration process; this usually happens during the "Parse Header" stage which takes a long time. I tried many different settings on imapsync and found the only way to get around this issue is to increase th RAM on the server. For reference, I had 16Gb of RAM and ran into this problem; after increasing to 32Gb the migration of imapsync went through successfully. I had one mailbox with about 1 million messages; not big messsages just notifications where each email is around 1Kb.

• If you have "Out of Office" Replies and Signatures in duo-byte characters like Chinese, Japanese, etc. then you need to run the following commands otherwise the export will not work properly.

• The HTML signature import part does not work; when exporting using zmprov -   is not exported and a lot of the other HTML code will become " for instance and re-importing the   is problematic.... We've tried using the program "recode" to get around it but still there are problems.

su zimbra
export LC_ALL="en_US.UTF-8"

• Need to add the ability to export and import catchall email addresses for domains (e.g. zmprov ma catchall@newdomain.com zimbraMailCatchAllAddress @sourcingagent.com.vn)

• if there are errors such as Can't locate File/Tail.pm in @INC when running imapsync then you need to install perl-File-Tail (in CentOS : yum install perl-File-Tail)

#Keywords

• Cross platform migration
• Centos 6 to Centos 7
• Centos 6 to Centos 8
• Centos 7 to Centos 8
• Centos to Rocky Linux
• Centos to Ubuntu
• Ubuntu to Centos
• Red Hat linux to Ubuntu
• Red Hat Linux to Centos

#Legacy Email Clients For some email clients with legacy email clients such as Outlook 2007, Outlook 2016 that still support clear email password authentication you need to run these commands. This legacy support operation is not recommended as it poses security issues to the system but there are users running really old email clients then these will help.

su zimbra
zmprov mcf zimbraImapCleartextLoginEnabled TRUE
zmprov mcf zimbraPop3CleartextLoginEnabled TRUE

• Added the ability to update the status of each account
• Added the ability import legal intercept settings
• Added the ability to import preferences for each user
• Added the export and re-import of different calendars, briefcases and contacts
• Added the import of shared calendars, briefcases