From Chrome 150 you can seamlessly transition a PWA to a new same-site origin.

Chrome's platform is a leading web browser developed by Google, offering insights into web standards, browser features, and web development tools. Through documentation, developer tools, and webinars, Chrome provides insights into building modern web applications and optimizing performance. Developers can learn about web APIs, progressive web apps (PWAs), and Chrome DevTools to create fast, secure, and user-friendly web experiences.

Chrome Developers

Chrome 150 introduces PWA Origin Migration, a new platform feature that lets developers seamlessly move installed PWAs to a new same-site origin without forcing users to manually reinstall. The migration uses a two-way handshake: the new app's manifest declares a `migrate_from` field pointing to the old origin, and the old origin confirms via a `.well-known/web-app-origin-association` file. Optionally, the old manifest can proactively signal the migration with a `migrate_to` field. Developers can control user experience with a `behavior` flag set to either `suggest` (passive notification) or `force` (blocking dialog on next launch). The destination manifest must include an `id` field to prevent duplicate app installations.

Seamless PWA origin migration: Change domains without losing users

Really glad to see this. Domain changes used to be painful for installed PWAs, and a lot of users never made the move. This should make migrations much smoother and reduce drop-offs.

Is the offline data also being migrated to the new domain?

Nice feature. That’s helpful. Though I wouldn’t call it “losing users”. If a user doesn’t want to install the new PWA after a domain change, then the user was already lost. No biggy there.
Though this makes it pretty easy now for me to switch our own “users” (our on-site POS devices) without having so go through the de- and re-installation every 9 months :D (the usual time we switch domains for our POS/Gamifications)