Merge pull request #304934 from Dhananjayanr98/patch-14

Update migration guidelines for Azure Migrate

Author: v-ccolin

articles/migrate/simplified-experience-for-azure-migrate.md

@@ -35,10 +35,26 @@ The key differences between the Classic and Simplified experience:
 - Classic experience is scheduled for deprecation on **30 March 2026**. We recommend using the **simplified experience** for initiating agent-based replication of any new VMware or physical servers.
   >[!NOTE]
   >Classic experience will not support starting replications on new servers after **October 30, 2025**.
-- Servers currently replicating using the classic experience will be supported until **March 30, 2026**. We recommend completing your migrations before this date.
 - If you have servers discovered through the replication appliance under the classic experience, ensure replication is initiated before **October 30, 2025**, and plan your subsequent migrations before the deprecation date **(March 30, 2026)**.
+- Existing VMware and physical machines can continue using the classic experience until **March 30, 2026**. After that date, any changes to replication configurations will require an upgrade to the new simplified experience.
+-  New features, enhancements, and mobility agent support for additional Linux distributions will only be made available in the simplified experience.
+-  If you don’t migrate your machines by **March 30, 2026**, replication health may be affected. You won’t be able to view, manage, or perform operations on these machines through the Azure portal after this date.
+  
+## Move your existing replications on classic experience to simplified experience
+>[!NOTE]
+  > When you migrate physical machines and VMware machines using agent based migration, the tool uses the same replication architecture as agent-based disaster recovery in Azure Site Recovery. Some components share the same code base and some content might link to Site Recovery documentation. **Simplified experience** is referred to as **Modernized experience** under Site recovery documentation.
+
+Follow these steps to move your existing replications to the simplified experience:
+
+1. [Check the required infrastructure for your setup](../site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md#how-to-define-required-infrastructure) and the [FAQs](../site-recovery/classic-to-modernized-common-questions.md) for all related information.
+2. [Check the architecture and minimum version of all components](../site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md#architecture) required for this migration.
+3. Check all the [resources required](../site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md#required-infrastructure) and deploy the [replication appliance](tutorial-migrate-physical-virtual-machines.md#simplified-experience-recommended).  
+4. [Prepare the classic Recovery Services vault](../site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md#prepare-classic-recovery-services-vault) used by your existing replications.
+5. [Prepare the simplified/modernized Recovery Services vault](../site-recovery/move-from-classic-to-modernized-vmware-disaster-recovery.md#prepare-modernized-recovery-services-vault) where your appliance has been registered.
+6. [Trigger migration for your existing replications](../site-recovery/how-to-move-from-classic-to-modernized-vmware-disaster-recovery.md).
+
 
 ## Next steps
 
 - Learn more about the [Simplified experience](tutorial-migrate-physical-virtual-machines.md#simplified-experience-recommended).
-- Learn more about the [deprecation of classic experience](../site-recovery/vmware-physical-azure-classic-deprecation.md).
+- Learn more about the [Deprecation of classic experience](../site-recovery/vmware-physical-azure-classic-deprecation.md).