This would have been the ideal approach, but there are some problems: The old system is legacy and currently still in use, which means an in- place upgrade is out of the question.
The migration of the old user database is also not an option, since the new side uses a Plesk + SOGo integration which creates the SOGo users via a hook that runs post-plesk user creation. Am Montag, den 21.09.2020, 14:43 -0400 schrieb Ludovic Marcotte: > On 2020-09-21 2:07 p.m., Janis Hamme ([email protected]) wrote: > > > Don't know if what you try is supposed to work, but it might be > > easier > > to migrate the entire database to your new system and then upgrade > > the > > database schema as described in the user manual for upgrading SOGo > > versions. > This is definitively the best approach. > > -- > Ludovic Marcotte > [email protected] :: +1.514.755.3630 :: https://inverse.ca > Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence ( > https://packetfence.org) and Fingerbank (https://fingerbank.org) > -- Patrick Geschke IT-Systems Engineer openroot GmbH // Ibbenbüren Gildestraße 2 49477 Ibbenbüren Fon: +49 (0) 5451 560 915 - 0 Fax: +49 (0) 5451 560 915 - 99 M: [email protected] W: www.openroot.de Geschäftsführer: Patrick Geschke Amtsgericht Hamburg, HRB 142365 Ust-ID: DE 308025519 -- [email protected] https://inverse.ca/sogo/lists
