I totally agree with marto and stevieb.

Also, you dumped XML into your post. You'll have to pull out the relevant VB script(s) that you would want converted to Perl. If you're not wanting to do that conversion yourself, you could purchase ActiveState's Perl Dev Kit (PDK) or their ActivePerl Pro Studio (which includes PDK). Their PDK includes a VBscript converter. It's been over 10 years since I had access to PDK, but from what I remember, I needed to tweak the Perl code that the VBscript converter created when I tried using it to convert Excel macros to Perl.

I'm not trying to sound mean here, but if you don't want to convert VB script to Perl yourself and are willing to throw money at the problem, you can always hire one or more developers to do the code conversion work for you. One possible place to look for Perl developers is at https://jobs.perl.org/.

Also, doing a super quick scan through your post, I saw references to Wscript, registry keys and MSSQL. That means that your XML data probably contains more than just VBscript. That could complicate your code conversion work if you're not careful.