ACS 4.1.1.24 to 5.2.0.26.3 Network Device Migration issue

Question

Hello all.
I'm getting an error when I run the migration.bat script to migrate data from ACS 4.1 to 5.2 and analyse the Network Devices in the 4.1 database.
hqssec01
AnalyzeAndExport
Network Device
hqsvg22417k
error
invalid_sharedsecret
Cannot migrate Network Device that has Shared secret key with a name that contains any of the following characters: "'{}
hqssec01
AnalyzeAndExport
Network Device
hqsvg22418k
error
invalid_sharedsecret
Cannot migrate Network Device that has Shared secret key with a name that contains any of the following characters: "'{}
hqssec01
AnalyzeAndExport
Network Device
milswi1a1
error
invalid_sharedsecret
Cannot migrate Network Device that has Shared secret key with a name that contains any of the following characters: "'{}
hqssec01
AnalyzeAndExport
Network Device
DS2000_Storm_Standby
error
invalid_sharedsecret
Cannot migrate Network Device that has Shared secret key with a name that contains any of the following characters: "'{}
We use a common shared secret key for 253 devices to use for TACACS authentication.  Unfortunately ACS 4.1 allows you to use the " character in this key but 5.2 doesn't.  Is there a way of changing  the  key in the 4.1 database for all 253 devices without having to manually change all devices individually?
I can change the AAA client's key with various tools no problem, but the issue is the key stored on the ACS database.
Any help would be great!

Answer 1

Just to update.
RDBMS syncronization using csv files is only available on 4.2 so I updated from 4.1 to 4.2.
Using the accountActions.csv file, I made a copy accountActions2.csv and used the action id 225 to dump the NAS database to a file DumpNAS.txt.
I then imported the relevant fields from DumpNAS.txt into a new file accountActions3.csv and used action ID 224 to update the NAS database.
The issue I had was that the Value 3 field "Vendor ID" I could not locate the corrent string to use.
In the end I used the 'File Operations' function in ACS 5.2 and used the network device template to load the devices into ACS 5.2 with the new shared secret.  The only thing missing from was Network Device Groups, which had to be created manually and then manually move each device into the relevant NDG.
This may prove useful for anyone having a similar problem.