One approach to this issue is not to 'migrate' the exiting vaults.
In your new environment, your existing vault, would link to the vault path in 'production server'.
You would put this vault as read-only.
You would create a new vault mounted in the new environment to be able to create new data.
If this new environment has only READ access (windows/OS permission) to path of 'production' folders, it is impossible to delete or broke anything.
That is interesting. What are some of the key steps that you take to execute that scenario? I understand at the high level, but are there some key settings or steps you need to take?
Upcoming October 2019 Regional User Groups