How to Migrate Cyrus to Dovecot Server Step by Step?

Organizations often look to change their existing email infrastructure when their needs are not being met. It could be frequent downtimes, slow response, or outdated UI. Your company might be in a similar position. That’s why you need clear guidance on how to migrate Cyrus to Dovecot.

The problem is not a lack of options, but the inverse; there are so many methods to choose from that it puts doubts in the mind of even veteran IT personnel.

So one could only imagine what would be going on in the minds of newly appointed Admins who have never managed a Cyrus IMAP to Dovecot transfer on their own.

Especially when they have to deal with the technical nuances of Berkeley DB. Shifting all of it is difficult because Dovecot does not read it natively.

No need to worry, I have helped countless organizations move their data across platforms. So if you just follow my instructions, you will be able to quit Cyrus and adopt Dovecot as your primary server. Let us first list out all the reasons that make people leave Cyrus in favor of Dovecot.

Why Admins Choose to Migrate Cyrus IMAP to Dovecot Email Server?

There is no better way to get a complete idea about the two providers than a full comparison chart highlighting the differences directly.

Feature	Cyrus (Old System)	Dovecot (New System)
Performance	Heavy and slow	Light and fast
Reliability	Indexing issues cause lag	Self-healing and stable
Backups	Complex and proprietary	Simple and standard
Maintenance	Requires high-level experts	Easy to manage
Compatibility	Struggles with modern tools	Built for the 2026 stack
Scalability	Gets slower as data grows	Designed to grow with data

Now you know for sure that staying on Cyrus is not beneficial, and Dovecot will be a better choice by a long shot. We still can’t go to the migration phase just yet. You need to make sure that both source and destination environments are ready for the task at hand.

What to Do Before Transferring Cyrus Email to Dovecot?

Start by fixing the database format issues. Do this even if you believe there is nothing wrong. It’s better to stay safe than sorry, especially when it comes to moving hundreds, if not thousands, of users’ data. Otherwise, you will face similar problems to those where iCloud emails are not coming through on your server.

Cyrus, as you might already be familiar with, uses .seen and .sub file formats. This has been the same ever since the first release of the legacy Berkeley DB.

As I have told you earlier, Dovecot faces issues while reading all this data. Even with all of its advances.

So that leaves you with the task of running cvt_cyrusdb on your source Cyrus server.

What this does is that it tells your Cyrus DB, “Look, I need to make these files readable by a foreign entity.” So Cyrus flips them to the skiplist or flat format, depending on your exact instruction set.

It’s not that you can’t move Cyrus to Dovecot with BDB; it’s that when you do, you ask your Dovecot server to do all the heavy lifting.

This prolongs the migration duration more than before because now the server makes a new empty index for every user. So all emails appear in the user’s inbox like they just arrived, causing a lot of confusion. It’s better to make all necessary changes in the background so the transition is as smooth as possible.

Take Cyrus Email to Dovecot Manually Via imapc Proxy

Here, we will be instructing the Dovecot server to pull messages from the Cyrus database:

Step 1. Configure the Migration Proxy

Go to your Dovecot server and build a migration config (e.g., /etc/dovecot/conf.d/90-migration.conf):

Then run the following script

# Define the Cyrus source as a remote IMAP client

imapc_host = 10.0.0.1 # Your Cyrus IP
imapc_port = 143
imapc_user = %u
imapc_password = master_password_here 
imapc_features = rfc822.size fetch-headers
imapc_list_full_rbac = yes

Step 2. Start the Manual Sync Execution

Install the doveadm utility if you haven’t already, then use it to pull the data.

# Execute the sync for a single user
# -R ensures the target mirrors the source (deleting items on target not on source)
doveadm -D backup -R -u [email protected] imapc:

Step 3. Fix the folder mappings:

Dovecot and Cyrus both use different folder mappings. So it is possible that folders don’t line up on the first try. You can manually map them with the help of the Dovecot 15-mailboxes.conf or use a mapping file with dsync.

Also Read: What to do if Dovecot is not receiving mail

Note: You may need to modify the scripts for your environment. Don’t copy and paste directly. This instruction is for all the scripts given by me. If scripts bother you, I have a less technical alternative.

Professional Way to Migrate Cyrus IMAP to Dovecot

There is no better choice than the SysTools IMAP migrator in this regard. It can fetch user data, pack it, and transfer it all in the background. It creates a direct server-to-server bridge between the two platforms that moves your user email messages with minimal downtime.

 

Using filters, you can decide what migrates and what stays with utmost precision. To top it all off, it is available for both Windows and Mac. The free demo lets you try all the features on the first 100 messages in the top 5 folders on any number of user accounts. So get your copy today. In five simple steps, you can transfer the data.

• Step 1. Install the software, check the IMAP endpoints, click on the email workload, and apply a date filter. Then press Next to proceed.
• Step 2. From the drop-down in the source screen, choose the Others option. Add the Cyrus IMAP server details. Validate and Press Next.
• Step 3. Choose the other option for the Destination as well, but this time add the Dovecot server details. Validate and Press Next.
• Step 4. Download the CSV template from the tool and fill it with the user list, then reupload it.
• Step 5. Select, Validate, and Migrate the data.

Conclusion

Earlier, organizations that were confused about how to migrate Cyrus to Dovecot now have the exact blueprint that professionals follow. Use the steps outlined here and take help of the automated utility to transfer the email data of your users. The scripts may confuse you, but the tool’s GUI won’t, so don’t do it manually; instead, do it the right way.

Frequently Asked Questions

Q: What are the chances that email data is lost while moving Cyrus to Dovecot?

I have tried my best to include clear-cut instructions aimed at mitigating data loss. The reality is that there a 100% guarantee of data safety is simply not possible. However, your best bet is to use the tool and ensure utmost safety for the user’s email data during the transfer. With the retry failed and the delta rerun option, the tool has plenty of safeguards to prevent data loss.

Q: How long does it take to move everything from Cyrus to Dovecot?

There is no universal timeframe. So comparing your situation with another’s is not that beneficial. There are a lot of variables that influence the duration. Your current setup, the number of users, and the methodology used all have a profound impact on how long it will take. One thing is for sure when it comes to Cyrus IMAP to Dovecot server migration, the fastest method is the tool.

Q: Which platform has a larger user base, Cyrus or Dovecot?

Dovecot has a significantly larger user base and market share. This translates to better support and a more active community.