I was under the impression that IDM did not only drop unnecessary renames but also moves liek the following:

<move class-name="User" dest-dn="\MUMMERT-META\MUMMERT\at\users\Someone" dest-entry-id="48450" event-id="migrate-app-sync-1">
<association>232998F269A64A2BC12573530081C5D0</association>
<parent dest-dn="MUMMERT\at\users"/>
</move>
</input>
</nds>
16:21:57 862CCBB0 Drvrs: DRV_MPMA_ALL ST:Pumping XDS to eDirectory.
16:21:57 862CCBB0 Drvrs: DRV_MPMA_ALL ST:Performing operation move for \MUMMERT-META\MUMMERT\at\users\Someone.
16:21:57 862CCBB0 Drvrs: DRV_MPMA_ALL ST:Moving entry \MUMMERT-META\MUMMERT\at\users\Someone to \MUMMERT-META\MUMMERT\at\users.
16:21:57 862CCBB0 Drvrs: DRV_MPMA_ALL ST:
DirXML Log Event -------------------
Driver: \MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_MPMA_A LL
Channel: Subscriber
Object: (\MUMMERT-META\MUMMERT\at\users\Georg von Pfoestl)
Status: Error
Message: Code(-9010) An exception occurred: novell.jclient.JCException: moveEntry -606 ERR_ENTRY_ALREADY_EXISTS

could it be that idm 3.0 would've ignored this move event and idm 3.5 introduced this error condition?

Cheers, Lothar