Behaviour for versioned files on external storage

First of all: thank you for implementing such a much-needed tool!

I was thinking about using the tool migrating from a NC standalone docker to the AIO docker on an Unraid system. In the old docker, most of my actual user files are mounted as external storage (this is a common practice on Unraid for Nextcloud installations - e.g. look at https://www.youtube.com/watch?v=mOHOcgVMLGM).
Now I know that with v2.0.1 of this plugin, external storages are by default not part of the archive anymore (which I think is in line with the expected behavior). However, I'm unsure about the database for the versions of the files on that storage. Is this migrated? If so, how?

Related to that is the question for me: what is the correct migration procedure if one uses external storage and versioning?
Should I unmount the external (local) storage from the old container first? Should I remap them as external storage to the new container before importing the migration file (I assume)? What needs to be prepared to not completely mess up the database and files?

The point I'm making: is there already documentation available on the caveats etc. when using this plugin together with external storages?

Thank you!

The issue asks whether file-version databases on external storage are migrated and what migration sequence users should follow. Start by verifying the plugin's current behavior, then document the confirmed caveats and procedure; done means users can prepare, export/import, and remap external storage without ambiguity.