Hi Sab and Jonathan,
Really nice to see you help out so quick!
We have one IS in the setup. The IS is connected to both broker and UM.
Yes, I am using the service pub.utils.messaging:migrateDocTypesTriggersToUM as indicated in the migration guide.
thanks for the inputs,
Loïc
Loic,
your earlier post said you had a JMS Alias pointing to Broker. This is not what you need for this utility. You must have a wM Messaging connection (not JMS) connected to Broker. It doesn’t need to be the default connection, but must be present.
Do you have that?
Hi Jonathan,
Yes this is the correct setup. However, I think that is where there was a problem: I disabled the Broker connection alias, but I couldn’t get it to enable again - IllegalStateException.
I had to reconfigure the connection.
I now test ran the migration service again and it now executes fine. 
Thanks for the help!
Loïc
Loic,
good to hear!
One little gotcha: by default the service runs as reportOnly, which only reports what changes it would make, but doesn’t update any assets. You need to set reportOnly to false to get it to actually update doc types and triggers.
(If you read the doc, it should be clear, but a lot of people miss that!)
Cool, thanks for the tip, indeed I hadn’t picked that up yet.
Cheers,
Loic