Version Upgrade

• Upgrade is not an Update — An Update installs a new Release within the same Version; an Upgrade changes the entitled Version and may introduce new commercial, technical, or licensing conditions.
• A new Version is not automatically granted — Having a valid License, completed Activation, or receiving Updates does not automatically create rights to use a new Version.
• Upgrade conditions — The customer must have the applicable Product Entitlement, Platform Entitlement, Upgrade right or new Version Entitlement, valid License/Entitlement, and satisfy the applicable commercial conditions.
• Upgrade flow — Identify current Version → check Version Entitlement → identify new Version → verify Upgrade rights → complete applicable commercial conditions → grant new Version Entitlement → install a PUBLISHED Release of the new Version → verify and Activate under the new entitlement.
• Upgrade retains the Product where unchanged — If the new Version remains part of the Vietnam Office suite, Product Entitlement may continue to apply; the principal change is the Version Entitlement granted to the customer.
• Upgrade does not automatically change Platform — Upgrading from an older to a newer Version on Windows remains within the Windows Platform; on macOS it remains within macOS. An Upgrade does not convert Windows rights to macOS or Desktop rights to Mobile.
• Desktop Upgrade — After the new Version Entitlement is granted, the Desktop device may need to re-verify the License, Version, and Device Binding when installing and activating the new Version.
• Mobile Upgrade — New Versions/Releases on Android/iOS/iPadOS continue to be distributed through the applicable Store; usage rights must comply with Store Entitlement and the applicable Version Entitlement.
• Upgrade does not increase Quantity by default — Upgrading a Version does not automatically increase the number of Licenses or entitled devices. Quantity continues to follow the approved commercial entitlement.
• System Requirements for the new Version — Before upgrading, customers should verify that their device satisfies the System Requirements for the new Version. Having Upgrade rights does not guarantee that the current device is technically compatible.
• Compatibility of the new Version — A new Version may change or expand Compatibility. Customers should review Release Notes and Compatibility documentation before broad deployment.
• User data during Upgrade — Software Upgrade is not a document-backup mechanism. Customers should back up important data before major upgrades or system changes.
• Do not use a new Version before entitlement is granted — Possession of an Installer or Package for a new Version does not create Version Entitlement. Activation may be rejected if Upgrade rights have not been granted.
• Previous Version after Upgrade — Any continued right to use the previous Version is determined by the applicable Version Entitlement and Upgrade policy. It should not be assumed that every Upgrade permits simultaneous use of both old and new Versions.
• Enterprise and Project deployments — For Enterprise/Project deployments, Upgrade must comply with the applicable Product, Version, Platform, Quantity, Project, and Commercial Approval. Large-scale upgrades should proceed only after entitlement scope has been confirmed.
• Backend is the authoritative verification source — The Vietnam Office backend determines the current Version Entitlement, new Version Entitlement, Upgrade rights, Platform, Quantity, and License status before the new Version may be used.

Upgrade principle: new Version outside current entitlement → verify Upgrade Right → satisfy commercial conditions → grant new Version Entitlement → install the correct PUBLISHED Release for the Platform → verify License/Device/Store → use the new Version within the granted entitlement scope.