...
Follow the below approaches to migrate and overcome the issue:
Approach 1
CMJ's Power Admin can be used to inspect configuration objects contributed by JSM and how they are referenced by the projects that need to be moved, then, the configuration can be changed to remove these references based on the documentation here.
Currently, Power Admin does not support JSM-specific configuration, i.e. configuration that is part of a service desk project, but it will show all items like schemes, screens, workflows, etc. that refer to the problematic objects.
Info We recommend this be tested on a staging instance if the changes are not desired on the source instance.
...
- Alternatively, JSM can be installed on the target Jira instance before performing the deployment and can be removed after that.
- Some unnecessary configuration items may be left after the removal of JSM, but they should be easy to find with Power admin and then removed necessarily.
- A trial license should suffice for the temporary installation of JSM, and the deployment should work even if JSM isn't licensed.
...