Genesys Cloud web messaging replaces legacy web chat and requires comprehensive migration of queues, flows, utilization settings, quality policies, analytics, and integrations to enable advanced capabilities such as multi-session conversations. The migration process involves specific procedural steps to update agent experience, enable authentication, convert web chat flows to message flows, update analytics configurations, and configure authentication settings for Genesys Cloud embedded clients. ACD Web Chat v2 and v1 are deprecated, with Genesys discontinuing support and encouraging all existing customers to migrate to Web Messaging and Messenger. Prerequisites for migration include Genesys Cloud CX 2, CX 3, CX 4, or Digital Add-on II licenses, along with all permissions under Web Deployments for Configurations and Deployments, and an inbound messaging flow. The structured migration path encompasses several key components: migrating queues from web chat to web messenger, converting web chat flows to message flows, updating agent utilization configurations, adjusting quality management policies, and enabling authenticated web messaging. Organizations must account for analytics impacts during the transition and migrate Predictive Engagement and Customer Journey configurations accordingly. The migration extends to Genesys Cloud embedded clients, with considerations for agent experience throughout the process. Some feature components require no migration action, while others necessitate specific configuration steps to ensure successful transition. This migration guide series provides detailed articles addressing feature impacts, migration procedures, and integration transitions for Predictive Engagement and Genesys Cloud embedded clients. Additional resources are available through the "About web messaging" documentation and community support channels for organizations requiring further guidance on implementation details.