Savings depends on the configuration of the AFF, specifically what features you are using: Aggregate deduplication, Compression, Compaction, etc.. and if those same features are supported on the FAS. Typically all of these can be supported with newer ONTAP versions, licensing, and hardware model support, even though they are FAS. If they are supported, then data comes over deduplicated/compacted/compressed without having to be hydrated and dehydrate as part of the transfer, so your savings calculation would be equivalent. If you can't support some of these features, or you don't configure them, you will need to compute how much savings they are providing and use this for your calculations. You can also use network compression to compress the transfer between systems, although it is just network compression and doesn't have anything to do with the saving of the data to disk. Make sure your mirror relationships are XDP so that you could run independent versions of ONTAP between the AFF and the FAS to support newer versions on the FAS to support your goal. 9.8 is a little dated.