Migration plan - create new tokens at new catch event?

[B.d_d.d]

v2 process definition added a new message intermediate catch event that doesn’t exist in v1.
When migrating v1->v2 plan, is it possible to add an instruction to create a token there, and how?

I tried
{
“sourceActivityIds”: [
“existingcatchevent”
],
“targetActivityIds”: [
“existingcatchevent”,
“newcatchevent”
],
“updateEventTrigger”: true
},

But that didn’t create the tokens in that event after migration…