We are super-excited to announce our new Zimbra to Zimbra Migration Software!
Sure, we have always done Zimbra to Zimbra migrations, but these to date have been using NG Backup, Rolling Upgrades and “the rsync method”. Well, NG Backup is no longer and Rolling Upgrades only work when both the source and the target systems are Network Edition. The rsync method is very labor-intensive when trying to upgrade operating systems, as well as the Zimbra version.
To date, there has been no tool to migrate from, say a FOSS Zimbra system to a Network Edition Zimbra system except to get only basic data like user accounts (with just a few attributes), distribution lists and domains. So… we spent months and created software (the “Software”) to amp up the fidelity and make Zimbra to Zimbra migrations as easy and as comprehensive as we could!
Our Software is intended to perform side-by-side migrations of Zimbra systems, single or multi-server on either the source and/or target systems; and if multi-server, with same or differing numbers of mailstore servers in the source and target environments.
Unlike Rolling Upgrades, our Software is operating system-, Zimbra version- and Zimbra type-independent. You can use it to migrate:
– From FOSS to NE
– From FOSS to FOSS
– From NE to NE (if for whatever reason the Rolling Upgrade process is inappropriate)
– From NE to FOSS
You could use our Software to migrate from a single-server FOSS Zimbra 8.8.15 system on Ubuntu 18.04 to a multi-server Zimbra 10.1 Network Edition system on Rocky Linux 9.
The Software does not migrate everything, for example the sharing that Zextras/NG Backup migrates, nor any LDAP or similar customizations that would be migrated in a Network Edition-to-Network Edition Rolling Upgrade. But, neither does the Software have the limitations/restrictions that Zextras/NG Backup and Rolling Upgrades have.
The Software DOES MIGRATE:
– Resource accounts (e.g. Conference Rooms)
– External accounts (off-Zimbra domain users to whom resources have been shared)
– Distribution Lists and their members
– Local domains and Domain Aliases
Of course, regular User accounts are also migrated, including their following attributes:
– Password
– Display Name
– Given Name (first name)
– Surname (last name)
– Email Aliases
– Work Title
– Company
– Complete Address (street, city, state zip)
– Telephone Number
– Spell Check Words to Ignore
– Personal Amavis Block List Senders
– Personal Amavis Allow List Senders
– Trusted Senders List
– Preferred “From” Email Address
– Preferred “From” Display Name
– All Zimbra Access Control Entries
– All Sieve Scripts (Filters)
– Contacts
–> Includes all contacts in non-empty subfolders of the “Contacts” address book
–> Note: Other address books are not exported/imported. We suggest moving all other address books as sub-address books under the “Contacts” address book prior to export.
– Calendar
– Briefcase
– Tasks
– Email Signatures
– zimbraId
In addition, the Software creates a list of Admin accounts (both Global and Delegated), available as a text file, but does not set either zimbraIsDelegatedAdminAccount nor zimbraIsAdminAccount attributes on any accounts on the target Zimbra system.
Note that the Software does migrate ACEs set on user accounts (but not on domains), to attempt to simplify the restoration of Delegated Admin accounts, and; to remove issues we have experienced with the Domain-level ACEs set by Zextras/NG Admin, which can differ from those used in FOSS-without-Zextras and Network Edition-without-NG systems.
The Software DOES NOT MIGRATE:
– Email Blobs (We use IMAPSYNC for this!)
– Shares (they are often broken, so best to create them fresh)
– Classes of Service (start fresh, with better password policies and other security settings)
– Galsync Accounts
– Localconfig attributes
– System-level LDAP and other attributes not included above, for example:
–> Branding and theming customizations
–> MTA settings
–> SSL certificates
–> Okta, Jumpcloud or Active Directory authentication integrations
Essentially, the Software expects us together to configure the new, bare destination system in accordance with current best practices — effectively leaving your regrets behind on the source system, but requiring more diligence versus a Rolling Upgrade.
How Does The Software Work?
After we execute a Zimbra to Zimbra Migration Services contract with you, we will:
- Analyze your existing Zimbra environment and recommend specifications (CPU, RAM, disk layout and number of servers) for your new Zimbra system.
- Advise on security hardening, performance and reliability best practices.
- Collaborate on kitting out your new Zimbra environment.
- Install the Software on a mailstore on both the current (source) and new (target) systems.
- Let the Software do a test export of your current system, and rsync that over to the new system.
- Run a test import on the new system.
- Collaborate on configuring IMAPSYNC to get the email blobs migrated (we have an up-to-date IMAPSYNC server on AWS you can use, or; we can help you deploy your own on-premises).
- Collaborate on evaluating the test migration, and make any adjustments or tweaks as needed.
- Collaborate on executing the actual cutover to the new Zimbra system.
How Much Does All This Cost?
We license the Software (with baked-in Support) for US$12.95 per mailbox for 30 days, subject to a 100-user account minimum. We offer discounts for Zimbra systems with more than 1,000 user accounts. What’s a “user account”? Go to your Admin Console, and on the home page look for “Accounts: <number>”. That’s the number of “user accounts” for pricing purposes; just like Zimbra’s own licensing.
The number of domains, distribution lists, aliases, servers, Classes of Service, etc. doesn’t impact the price.
Want to learn more? Fill out the contact form!