When we started implementing Splunk, we created most of the artifacts(KOs, reports, dashboards, etc.) in the default 'Search and reporting" App. When the number of artifacts increased over time, it became difficult to manage. So, all the artifacts created earlier in Search and Reporting app need to be moved into a separate app(s).
Creating all the artifacts again manually, in the new App is tedious and error prone. I figured out hack to manage this situation by using the existing "Search and Reporting" App as a template. I created a template from the existing search app by simply copying the search folder in "$SPLUNKHOME\etc\apps" to "$SPLUNKHOME\share\splunk\app_templates".
Now, in the browser, when new App is created the usual way from Apps menu, a new entry named "search" appears in template dropdown. Using this as a template for the new App will bring in all the existing artifacts along.
I would appreciate, if someone in the community can verify this approach.
After testing the practice above , i can conclude that your approach work very well .Except that we have to delete certains views in the new app that has been creating with search and reporting app . This will avoid te duplication.