I would recommend a more structured approach:
1) Move complete search apps to your SHC
2) Disable the scheduled searches on the standalone search hed.
Details: Instead of trying to move individual searches moving by app is easier to control.
- The splunk cmd btool (from dwaddle) gives you a nice list of all apps that have scheduled searches.
- Go through each one and if you want that app's searches running on the SHC copy it to shcluster/apps on the SHC deployer.
- Once all apps have been copied do a cluster deploy
- Then go back to your standalone search head (or appropriate deployment server) and disable those searches so that they are no longer scheduled on the standalone server.
This will be easier to maintain and control.
If you continue to create apps on your standalone search head or you already have those same apps on the SHC you will need to merge the app files. I recommend winmerge for this 🙂
The first half to this is not so horrible:
| rest /servicesNS/-/-/saved/searches | search is_scheduled=1 | fields + title, eai:acl.app, eai:acl.owner
There, "identified" 🙂 The harder part is the "move". I would suggest a liberal application of things like:
splunk cmd btool --debug savedsearches list <searchname> | egrep -v "/etc/system/local/
To see where all the various pieces of your saved search is defined, and then grab the pieces from the .conf files directly and reassemble them on the other side.