...
Make sure CMJ will be able to create a non-default scheme with the name of the current default scheme.
- Use the selective merge to match the scheme to an existing scheme on the current Jira instance.
- Rename the default scheme on the target Jira instance and retry the deployment with the same snapshot
- Change the name of the conflicting scheme on the source Jira instance, create a new snapshot and retry the deployment
- Associate the project(s) with the default scheme on the source Jira instance, create a new snapshot and retry the deployment
...
There is a change in the default scheme that attempts to rename it to a name that is already in use by a non-default scheme. You can find the conflicting scheme by the 
icon in both the tab and the change with similar error in a tooltip:
Resolution
- Use the selective merge to make the scheme non-default and select a different name. By using this you will be able to deploy without leaving the wizard. A new non-default scheme will be created.
- Use the selective merge to match the scheme to another existing scheme on the current Jira instance.
- Rename the default scheme on the source Jira instance to the same (or any non-occupied) name as target's, create a new snapshot and retry the deployment.
- Associate the project(s) with a different scheme, create a new snapshot and retry the deployment, create a new snapshot and retry the deployment.
...