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.
If you only need individual users you can use sogo-tool to export the users after the upgrade to 5.0 and import them into a clean database. Or just remove any users that you don't want to keep. Regards Janis Am 21.09.20 um 19:04 schrieb Patrick Geschke (patrick.gesc...@openroot.de): > Exactly this. > I have a 2.2.17a system where i dumped a demo account, > which previously was also created on the 5.0.0. system. > > Dumping on 2.2.17a with 2.2.17a sogo-tool and importing on the 5.0.0 > system with 5.0.0 sogo-tool failed with mentioned error. > > Am Montag, den 21.09.2020, 17:23 +0200 schrieb Christian Mack: >> Hello >> >> Am 21.09.20 um 14:24 schrieb Patrick Geschke ( >> patrick.gesc...@openroot.de): >>> Hey guys, >>> >>> im running 2 sogo installations. >>> >>> A) SOGo 2.2.17a >>> B) SOGo 5.0.0 >>> >>> And im trying to migrate between those two. >>> One of the major problems is >>> migrating the calendar and addressbook content. >>> When using sogo-tool backup and dumping accounts from the source >>> machine, sogo-tool restore will just show errors like >>> >>> sogo-tool[18746:18746] user backup (/path/to/backup) file could not >>> be >>> loaded >>> >>> Are those dumps incomptabile? What are my options? >>> Sidenote: The user accounts are already created on the target >>> machine. >>> >> You can create a new user on 5.0.0 and he/she can use it? >> You did dump with the sogo-tool from 2.2.17a? >> And you are restoring with sogo-tool from 5.0.0 into 5.0.0 System? >> And all users exist on the authentication source? >> You have setup a new database for SOGo 5.0.0? >> >> Then this should work. >> >> Kind regards, >> Christian Mack >> -- users@sogo.nu https://inverse.ca/sogo/lists
