For the support for EAP 6+ as target technology, we need some Conditions and Operations, like sending a CLI command to a server.
Or - in the first place - producing these CLI commands. Which should not be done ad hoc, but rather use WildFly's client code.

The commands must be created at least at syntactical level to effectively produce them. That means the basic DMR API.

To support EAP 6+ as the input platform, these commands must be processed/undestood at semantical level - e.g. we should be able to create a model of a datasource from the commands.
This is more advanced and probably requires reusing WildFly's internals, because we don't know the defaults, which may create the full model; without knowing these defaults, which may change, we could create invalid or different configuration than the source platform had.

Ideas for how the conditions and operations could look like:

<transition>
     <from command="/subsystem=logging/logger=org.jboss.as:add">
            <param name="level" equals="EVERYTHING">
     </from>
     <to command="/subsystem=logging/logger=org.jboss.as:add">
            <param name="level" equals="ALL">
     </to>
     <from command="/subsystem=logging/logger=org.jboss.as:add">
            <param name="level" equals="NOTHING">
     </from>
     <to command="/subsystem=logging/logger=org.jboss.as:add">
            <param name="level" equals="NONE">
     </to>
     <hint>The add operation now doesn't support EVERYTHING and NOTHING, the value ${level} needs to be changed to either "ALL" or "NONE"</hint>
</transition>