Hi Lorenzo,

why do you want to export all of those items? In my opinion a full database backup should be sufficient. In addition, you might want to take a snapshot of the App Server or take a backup of the wwwroot-folder. Of course, run the Update first in a lower environment and perform testing afterwards before moving to Prod.

Going from 6.16 to 6.22/6.23 isn’t considered as a migration - it’s just a Update installation.

Best regards
Roman

Good day, thx 4 your reply.

It’s correct that we’ve to upgrade to new version, but what we’re asking is:

• if there’s a procedure / methodology to test all the features that were working in prev. version in the new one.

Also we’re asking

• if  we’ve to execute some re-configuration activity or if we can expect that what was configured in 6.16 will be automatically reconfigured with 6.22/23

In general, upgrading FSM 6 from Update 16 to Update 23 should require zero to minimal reconfiguration.  However, you may need some configuration to take advantage of new features.  Besides following the Upgrade guide, you should also review the Enhancements, Notices, and Corrections sections of the Release Notes for all updates after Update 16.  Besides testing all business critical functions, test other features that are mentioned in the release notes. As mentioned in the Upgrade Guide, pay particular attention to the Run Log for the Mobile Upgrade.  That will list mobile design/metadata changes that may require some configuration.