Migrating Custom Country Setting

[Flies-Eyes]

Custom Country Settings for Specific Clients or Testing - Last year we went down the path of setting up specific folders in addition to the AdS standard AUS / United Kingdom / United States / International folders. This allowed us to do some testing without breaking things (which I still do anyhow) or create custom setups for different clients. Now we are at the point of doing our first time migration from 2020 to 2021. I was concerned about this from the very beginning. I am curious if others have gone down this avenue and had success with migrating non-standard country settings up to a new version. Our first attempt was a Fail.... As much as I like the theory if the annual migration for each client's settings is going to a slow time consuming expensive exercise it might be another function relegated to the wish list. To add some further complexity to the equation we are running a dedicated machine with an SQL Express Server that stores the *.mdf database that need to shared.

[Sebastian_Eiche]

the problem is, for having this options, you need to create registry entries and so on. this will not be registered by the migration dialog. 
I don't know how much do you have but what should work:

• create a backup of the folder AS2021
• Profile "a": use original folder in 2021 --> copy all files from profile "b" in the original folder of 2020  (maybe "AUS") --> AS migrate command --> after success: rename the folder in AS2021 to profile "a"
• next Profile "b": restore original folder in AS2021--> copy all files from profile "b" in the original folder of 2020 --> AS migrate command--> after succes rename the folder to AS2021 to profile "b"
• next profile
• in the end, recreate the settings in the registry

a lot of work, maybe this could be a a feature request

[Flies-Eyes]

Thanks for that update. Much appreciated.  The big question will be if we should presist with this management solution. I suspect not.  

[kent.w]

I've been helping Murray with this.  I tried the above mentioned solution and ended up with the same problem however the migration report showed much fewer errors.

At the completion of the migration I use Management tools to check the AstorBase.mdf > ModelRole table, 2021 does not match 2020.  I also check AstorCurrentAddIn.mdf > ModelRole table, in 2020 there are plenty of entries, in 2021 it is empty.

I believe if it can't manage these two tables than it is not working.

Can anyone advise if I can just copy the databases from 2020 to 2021?  Will AS 2021 work if I do that?

[Sebastian_Eiche]

this should work without problems. There was an issue by migrating the AstorAddin, but it could be solved to do the migration step twice. 
So please try to migrate the same databases two times