Automatically recreate Atlas Search indexes on a collection after the collection is dropped and recreated or overwritten
Currently, if you use the $out aggregation stage to modify a collection with an Atlas Search index, you must delete and re-create the search index. Also, if another collection is renamed with dropTarget:true to an existing collection that already has Atlas Search indexes on it, then it is necessary to recreate the Atlas Search indexes after the collection rename completes (which involves dropping the original collection).
This is a feature request to automatically recreate the pre-existing Atlas Search indexes on a collection after that collection is dropped and recreated (using either $out or renameCollection).
Jasho B commented
Well we want a button available on the Atlas portal to spooll out a search index script that we can then run after restore . Better would be the restorer process to handle this as it creates all the indexes .