How to Migrate Zimbra to New Server? Step-by-Step Guide
How to Migrate Zimbra to New Server?
If you are migrating your Zimbra mailbox to a new server, the procedure depends on whether your new server is similar to the previous server or if you are migrating from Zimbra server to another server. There are three methods to migrate Zimbra accounts to new server:
- Method 1 (Rsync): Use Rsync method when working with servers that are identical and have the same operating system and Zimbra version.
- Method 2 (CLI): Users can use CLI in situations where you are either upgrading Zimbra or changing OS.
- Method 3 (Dedicated Tool): Use the automated Zimbra to New Server Migration tool by RecoveryTools when you want a fast method that guarantees error-free Zimbra to New Server migration without downtime or complicated coding.
Method 1: Full Server Rsync Migration (Same OS & Version)
Use this approach only if the source and destination servers are running the exact same version of Zimbra and the same operating system. Follow the given steps to migrate Zimbra to new server:
- Stop services on the old server: Switch to the Zimbra user profile and safely stop all running services:
su - zimbra
zmcontrol stop - Verify processes have stopped: Ensure no Zimbra processes are running in the background:
ps -ef | grep zimbra - Sync the Zimbra directory: Use the rsync command as the root user to copy the data to your new server:
rsync -avH --progress /opt/zimbra/ root@new-server-ip:/opt/zimbra/ - Prepare the new server: Configure the new server with identical hostname, IP settings, and OS packages as your old server.
- Run the Zimbra installer (Software-Only): On the new server, install the identical Zimbra version using the software-only flag:
./install.sh -s - Fix permissions: Repair the file permissions on the newly synced directory as the root user:
/opt/zimbra/libexec/zmfixperms -e -v - Reconfigure and start services: Rerun the installer (
./install.sh) to configure the binaries, switch back to the Zimbra user (su - zimbra), and start the server (zmcontrol start).
Method 2: CLI Account & Mailbox Migration (Cross-Version)
Use this method if you are upgrading Zimbra versions, changing OS environments, or performing a selective account migration. Follow the step-by-step process to migrate Zimbra to another server
- Export Structural Data: On the old server, use the
zmprovcommand to backup all your domains, user accounts, passwords, and distribution lists into a safe backup directory. - Export Mailboxes: Save user emails into compressed
.tgzfiles using thezmmailboxcommand:
zmmailbox -z -m [email protected] getRestURL "//?fmt=tgz" > account.tgz - Provision the New Server: Install your target Zimbra version on the new server. Then, recreate the domains and accounts using the
zmprovdata you exported in step 1. - Import Mailboxes: Import the
.tgzarchives into the newly created accounts on the destination server using thezmmailboxpostRestURL command. - Update DNS: Once all data is successfully verified, point your MX records to the new server’s IP address to route new emails correctly.
Method 3: Dedicated Tool to Migrate Zimbra to New Server with Ease
Using manual command-line methods involves considerable downtime and strict adherence to the same operating systems. To migrate Zimbra to new server or another server without needing any CLI scripting, use a specialized tool like RecoveryTools Zimbra Migrator.
It supports migrating Zimbra including both on-premise or cloud-based Zimbra mailboxes (TGZ files) to another server easily with all emails, attachments, contacts, and calendars. You can select from 25+ destinations such as Office 365, Google Workspace, Exchange Server, IMAP, etc to migrate Zimbra mailbox to new server.
Trial Limitation: The free demo version gives you a chance to transfer 25 items from any folder. Purchase the full version to migrate Zimbra data to another server without limitations.
Steps to Move Zimbra Mailboxes to a New Server:
- Download and install RecoveryTools Zimbra to New Server Migration Tool on your Windows PC.
- Add the required Zimbra mailboxes or TGZ folders that you want to migrate to another server.
- Choose the required output file format (like IMAP, Office 365, PST) from the list to migrate Zimbra to new server.
- If required, set the advanced filters (Date Range, To, From, Subject) and click Next to begin Zimbra to new server migration.
Key Advantages of the Automated Tool
- Batch Migration: Migrate multiple Zimbra user mailboxes to another server easily at once.
- No OS Restrictions: Effectively migrate Zimbra to new servers without the need for matching operating systems or Zimbra editions.
- Data Integrity: Preserves original folder structure, attachments and metadata while migrating from Zimbra to another server.
- Scheduler Feature: Automate large-scale Zimbra data migrations to another server using the scheduler feature.
- Standalone Utility: A one-stop solution to migrate Zimbra to another server without Zimbra desktop installation.
Frequently Asked Questions
Q 1: I face a “Validating existing license is not expired… Unknown Error” when moving ZCS from Ubuntu 14 to 16. How do I fix this?
You can resolve this package dependency issue by running the following script on your server:
for pkg in $(dpkg -l | grep zimbra | grep perl | awk '{print $2}'); do sudo apt-get install --reinstall $pkg; doneQ 2: Do the source and destination Zimbra servers need to run on the same OS edition?
If you are using the manual Rsync method, yes. However, if you use the RecoveryTools software, there is no such prerequisite. It operates via IMAP sync, making it completely independent of the underlying server OS versions.
Q 3: Can I switch from CentOS to an updated Zimbra version (e.g., v8.6) without changing my domain name?
Yes. The automated tool allows you to map and move the accounts directly to the new server while keeping your domain name and email addresses intact.
Q 4: Does the migration include email attachments?
Yes, all mailbox items, including inline images and attachments, are fully supported and migrated to the new server environment.



