Migrating Exchange 2013 iApp to Exchange 2016 iApp

I haven't tested, but I almost sure that 2016 iApp would not work well with 2013, this is why there are 2 different iApps.

Think about how you would do the migration without F5. Just add F5 after to the logic.

You could for example, deploy a new application with 2016 iApp. As the servers get upgraded, add them to the pool of the new iApp. You need a new temporary FQDN (or more, if you use one per service), and point migrated users to that FQDN. Later when migration is completed, change temporary FQDN to the old one.

As you can see, most of the logic is about your network and not F5 itself.

In case you don't know, this is the solution and deployment guide for Exchange 2016:

https://support.f5.com/csp/article/K11100442

https://www.f5.com/pdf/deployment-guides/microsoft-exchange-2016-dg.pdf