I’m guessing he’s talking about the Destination, probably switching from a Topic in the original published message to a Queue, since JMSToolbox is publishing (not moving ) a copy of the message to a specific queue. If published on a Topic again, it would goto all other queues that are subscribed to that.
Note that the broker has a copy message feature now that retains all original header/metadata values, so hopefully JMSToolbox isn’t needed for that use case.