CMJ app is a tool that is used to migrate Jira configuration across different Jira instances. As such it will allow exporting the data to a snapshot file and then user can use the snapshot file to import the data in another Jira instance. This is done with an instance independent logic meaning that all objects will be matched between both instances and “equal“ objects from source and target will be treated as the same object. This is a procedure that CMJ can do only for the Jira configuration that is coming out of the box. For all configuration that is created by other apps (or acquired apps by Atlassian) it would be impossible to achieve because each app has its own mechanism to store data and CMJ can’t be aware of all apps internal working and handle this in a generic way.

For this reason CMJ app vendor created the Service Provider Interfaces mechanism to allow other apps to integrate with the export and import procedures in CMJ. This means that all app vendors that implement CMJ SPI will be automatically integrated with the CMJ routines and their app data will be included in the export and import by invoking the actual implementation that the vendor created.

There is SPI documentation - it has everything that is required for an implementation and detailed explanation of the whole process - Vendor Integration Corner.

CMJ SPI provides several types of integrations depending on the specifics on the app and the data it alters or uses. CMJ team analysis shows that the Assets app has only partial integration by implementing only some of the integration types. The clients need implementation of other types and that is what is missing here. More specifically, Assets implements the custom fields integration type (Custom fields SPI) and not the workflow type (Workflows SPI).