Upgrade to 9x preparation: migrate watches

Hello

I am going through the upgrade assistant on my QA cluster in preparation for the upgrade from 8.19.4 to 9.2.x
The assistant marks the following index as critical block for the upgrade:

.reindexed-v7-watches-6

The index effectively contains all my watches config. There is an alias ".watches" that is linked to this index.
The assistant does not provide an option to reindex this index. I tried to manually reindex it to ".watches" but this does not work (system managed index issue).
Then I tried to reindex the index to a "normal" new index. Redirecting the .watches alias does not work either (.watches is a reserved system name).
I eventually backupped the json content and deleted the .reindexed-v7-watches-6 and recreated all my watches based on the backupped json content.
This is ok for a few watches. My production environment contains 97 watches, also in the .reindexed-v7-watches-6 index. Is there a way to migrate the watches in bulk to a correct .watches index? Manually recreating 97 watches is a bit much.

Best regards
Christophe

We’re not sure how this situation happens yet, but we’ve seen this at least once before. That customer manually reindexed .reindexed-v7-watches-6 into a new index index named .watches-reindexed-for-9 and set the .watches alias to the new index. Then they deleted the .reindexed-v7-watches-6 index.