VB Script in M-Files Cloud

If you are migrating vaults to shared cloud service, all custom scripts and vault applications have to be validated before they can be migrated. Code validation is not required if you have an isolated cloud service. So the recommended option is to get an isolated service which will make management of your vaults much easier also after you are on M-Files Cloud and need to make some changes to the scripts.

You can read more about code validation on the Developer Portal. I also recommend discussing your migration plans with your M-Files representative so that you can estimate the effort.

(Looking forward, and regardless if you migrate to cloud or not, it is a good idea to already start planning how to replace your scripts with vault applications as Microsoft is looking to deprecate VBScript support in Windows gradually over the coming years. This is not something that happens overnight but if you have a lot of scripts it's better to be proactive and start these discussions in your organization already. Naming conventions, for instance, can often be managed with Compliance Kit's Managed Properties module without custom coding.)

I would definitely agree that this could be an opportunity to look at those VBScripts and see whether some could be replaced with VAF applications, especially if it's possible to use off-the-shelf, pre-validated applications. 

I would definitely agree that this could be an opportunity to look at those VBScripts and see whether some could be replaced with VAF applications, especially if it's possible to use off-the-shelf, pre-validated applications.