Many customers will ask how to move workloads that are currently part of a sidecar mesh to an an ambient mode mesh. We should provide an official answer and guidance on this, based on what is current possible with OSSM 3.2 / Istio 1.27. 

How this documentation is structured will depend on the content. If there is no migration possible, this may be a very short sentence to explain that workloads need to be re-deployed in an ambient mode mesh. If there is a procedure that would allow a workload (or a namespace) to be transitioned to ambient mode, then we would document that procedure in an ambient "migration" section. If there are limitations to the migration that should also be noted.