Forwarded to devs Migrator does not sync address book contacts from Roundcube webmail

[Hangover2]

Username: Hangover2

TITLE

Migrator does not sync address book contacts from Roundcube webmail

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.38 Update #2 (source and target server), Debian 9.13 x86-64 (source server), Debian 10.10 x86-64 (target server)

PROBLEM DESCRIPTION

Address book contacts from Roundcube webmail are not synced to a new Plesk server with the Plesk "Migration & Transfer Manager" tool.

STEPS TO REPRODUCE

- add a contact via Roundcube webmail to your address book
- migrate the subscription to a new Plesk server with the Plesk "Migration & Transfer Manager" tool

ACTUAL RESULT

- the address book of the Roundcube webmail email user is not migrated and so missing on the new Plesk server

EXPECTED RESULT

- the Roundcube address books of all email users of the migrated subscription should be transferred to the new Plesk server

ANY ADDITIONAL INFORMATION

- asking the clients to get the passwords for their mailboxes and doing it manually on our side or let them do it with an tutorial is not user friendly for big installations / migrations
- to copy the whole Roundcube database is also not possible if only some subscriptions are migrated
- so the solution will need a kind of extra script to query the roundcubemail database based on the username + handling the three tables: contacts + contactgroups + contactgroupmembers
- as their structure is quite simple it should not be that hard to implement and it would make migrations more stress-free

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[IgorG]

This is known Plesk Migrator limitation (Point 22): What are the known limitations of Plesk Migrator Extension?

The feature of transferring RoundCube address book is not planned to be implemented in Plesk due to some technical reasons: Allow migrating Address Books from the supported webmail clients using Plesk Migrator

1. Roundcube itself does not provide any tools for the database transfer;
2. The version of RoundCube/Horde databases differs from one version to another, which creates a serious issue for the process automation and the restoration of the database from the old version to the new.

You can use some 3rd party scripts to automate this process, for example: GitHub - JaimeObregon/export-roundcube-sql: Exports Roundcube webmail configuration (users, identities, contacts, groups...) for a given domain, so it can be easily migrated to a target Roundcube host.

You should apply it at your own risk and perform a full server backup before using it.