Migrating HS 2016.2.3 to new Data Center, tips/guide/etc?

Hi,

I was wondering if there were any guides, similar to the ones for an upgrade, that walkthrough at a high/medium level the process for migrating an Ensemble Instance.

I am presuming that the general flow would be to install a fresh instance in the target environment, and migrate items over.. but any specific order? gotchas? things to avoid? Some things that should/shouldn't be im/exported (ie, must be manually migrated) ?

Doing some googling I found this page, and i have confirmed I don't need Endian xlation or DB Extent conversion.

We're going from Windows -> Windows , physical to VM (considerations or gotchas on this?)

I have only inherited support of this environment for the past ~year or so, but i know there's a hefty dose of customizations in the environment.

I am also considering doing an upgrade at this time (to at least 2017.2), but I presume the decision as to whether to do so at this time  is more a function of site-specific needs and timeline than any "Best Practice" or ISC recommendation ?

I apologize if this question(s) is a bit n00bish - I have a little bit of experience upgrading instances in-place, but none doing a proper migration :)

Other notes: I plan to involve our Account reps but I wanted to do some pre-research / investigation first.
The client is technically on Healthshare but is really only using Ensemble functionality - possibly no HS functionality at all, AFAIK.

Thanks!