FabricPool and hardware lifecycle management

Hello,
I have a question regarding using FabricPool aggregates and performing replacement for nodes in a cluster (for instance in case of a tech refresh). If I understand, starting from Ontap 9.6 we can benefit from optimized volume move, in case source and destination aggregates are using the same object store.

In that case, when performing the hardware refresh we will:
1) create a fabricpool on the new node(s) using the same object store of the ones to be decommissioned
2) perform vol move (with tiering policy "auto", only hot data will be moved)
3) destroying old aggregate(s) 
4) cluster unjoin of the old nodes

Do it will work this way? 😉

Thanks

Lorenzo