How To Migrate Buddy List From ZeXtras Chat into Zimbra Chat

Posted by

Few days ago, i am perform upgrading Zimbra NE from 8.6 into 8.8.3 on my client. When upgrading into Zimbra 8.8, i am getting problem with proxy and has been solved with adding vhost. The solution has been wrote on previous post :

Another problem is my client use chat as another method to connect with another user besides email. They are used ZxChat. I am try to move/migrate buddy from old server into new server with this method : but did not work. I am also try to install ZeXtras latest version, but unsupported. You can find compatibility list from here :

When try to dig information about ZxChat and Zimbra Chat, they have different method to save and connect buddy on database. If using ZxChat, you can find database on /opt/zimbra/conf/zextras/zxchat. But, if using Zimbra chat, you can find database on MySQL/MariaDB. Table structure on Zimbra Chat especially RELATIONSHIP, Zimbra chat have 5 columns. But on ZxChat, it have 6 columns. I know it when open db2.script file from zxchat folder.

So, i am should be remove one column from db2.script that not used on Zimbra chat and convert it to sql. For easy my work, i am create simple script to remove column that unused. The following are how i am move buddy list from ZxChat into Zimbra Chat

– Copy db2.script from old server into Zimbra 8.8 (new server). You can find db2.script from /opt/zimbra/conf/zextras/zxchat folder on old server. I am assuming you save db2.script on /tmp folder

– Create a script to convert on the new server (Zimbra 8.8)

cd /tmp/

Fill with the following line

# script convert ZeXtras chat into Zimbra Chat
# By : and

# Convert User

grep -i "INSERT INTO USER" db2.script | cut -d "," -f3 --complement > user.sql
sed -i 's/$/);/' user.sql

# Convert Buddy/Relationship

grep -i "INSERT INTO RELATIONSHIP" db2.script | cut -d "(" -f2 | cut -d "," -f1 --complement > relationship.sql

# if getting problem when restore, please use below method and give comment grep -i "INSERT INTO RELATIONSHIP" above
# grep -i "INSERT INTO RELATIONSHIP" db2.script | cut -d "," -f1 --complement > relationship.sql
sed -i 's/^/INSERT INTO RELATIONSHIP VALUES(/' relationship.sql
sed -i 's/$/;/' relationship.sql

echo "User and relationship have been succeeded converted. Please see user.sql and relationship.sql in this folder"

save, give execute access and run script

chmod +x

When script has been done, the script will result 2 files. The file are user.sql and relationship.sql. Those file should be import into chat database on the new Zimbra (8.8)

– Backup chat database

su - zimbra
source ~/bin/zmshutil ; zmsetvars
/opt/zimbra/common/bin/mysqldump chat -S $mysql_socket -u root --password=$mysql_root_password > /srv/chat.sql

– Insert data into user and relationship tables

mysql chat < /tmp/user.sql
mysql chat < /tmp/relationship.sql

– Restart Mailbox

zmmailboxdctl restart

Please try to check from Zimbra webmail. The buddy list be supposed appear and available on user that have buddy from ZxChat formerly.

Finally, my client can be connect again with chat

Good luck and hopefully useful 🙂


  1. Hello,
    tried running script on 8.8.7 to migrate users to zimbra chat. Unfortunately doesn’t work for me..
    Getting errors:
    ERROR 1062 (23000) at line 1: Duplicate entry ‘1’ for key ‘PRIMARY’ERROR 1049 (42000) at line 2728: Unknown database ‘xxxx’,”);’

  2. Hi Iman

    How could i migrate contact and list of buddies from my old server to new server.

    Old server zimbra 8.7.11_GA_3800.NETWORK ( use zimbra chat) . .. Is there any methods i can migrate it?

    need your help on this

    thank you

    1. Hello,
      You can export chat database from old server and import into the new one
      – Export

      su - zimbra
      source ~/bin/zmshutil ; zmsetvars
      /opt/zimbra/common/bin/mysqldump chat -S $mysql_socket -u root --password=$mysql_root_password > /tmp/chat.sql

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.