In case anyone is wanting to do the same here's how I reallocated tickets in bulk. Note : I tested this on my update test bed using 1.10 and it seems ok. I tried applying the same to my v1.9 database and there are enough differences that this does not work on 1.9. As always:Make a backup, your mileage may vary, do this at your own risk, don't try this at home, all stunts are performed by professionals in controlled circumstances etc and all the other usual disclaimers. Only do this is you are confident you can fix it again by yourself afterwards. 1) Reallocating tickets to another user where that users name is in the thread body :set @[deleted] = 27;set @[deleted] = 29;set @[deleted] = "%Forest%";update ost_ticket otset ot.user_id = @[deleted]where ot.user_id = @[deleted] and ot.ticket_id in ( select thread_id from ost_thread_entry ote where ote.body like @[deleted] and ote.user_id = @[deleted]);I've just used an example here. In my actual query I used the HTML of their email footer that appears in the body of the thread. You need to work out what is unique in your situation.The old user may also be a collaborator in some tickets so use this to remove them from that tooset @[deleted] = 27;set @[deleted] = 29;update `ost_thread_collaborator` otcset user_id = @[deleted] WHERE `user_id` = @[deleted];At this point you should be able to go into your user directory in the Agent interface and there should be no tickets against your old user so you should be able to delete their entry.You may also have some other threads allocated to the old user id that you want to tidy up.set @[deleted] = 27;set @[deleted] = 29;set @[deleted] = 'Forest';update `ost_thread_entry` oteset user_id = @[deleted] , poster = @[deleted]WHERE `user_id` = @[deleted] ;