License Portability

License portability describes whether and how an existing software license can be used when a workload moves between environments, such as from an on-premises data center to a cloud provider. It concerns contractual usage rights, not just the technical ability to copy an application or launch a virtual machine. The software vendor’s agreement determines eligible products, versions, infrastructure, locations, and reassignment conditions.

Two common cloud licensing strategies are bring your own license, or BYOL, and license included. With BYOL, the customer supplies eligible software licenses and pays separately for cloud infrastructure. Existing maintenance or subscription charges may still apply. With license-included offerings, the provider supplies the specified software usage rights as part of the service price. Those rights generally apply to that offering and do not become portable licenses that the customer can take elsewhere.

BYOL can preserve an investment in commercial database or operating-system licenses. For example, an organization moving an Oracle database might use eligible existing Oracle licenses with an Amazon RDS for Oracle BYOL deployment. It must still confirm its edition, options, license quantities, support requirements, and permitted deployment configuration. A license-included offering may instead simplify procurement when the organization has no suitable licenses or needs a short-lived environment.

Portability is not universal. Some agreements allow eligible software on shared cloud infrastructure, while others impose dedicated-hardware requirements or restrict particular providers. Benefits associated with active maintenance or subscription programs may affect eligibility. Microsoft License Mobility through Software Assurance, for example, applies to eligible server applications; it is not blanket permission to bring every Microsoft product to any cloud. Dedicated infrastructure can satisfy certain conditions, but it does not independently create licensing rights.

The licensing metric matters as much as the license count. Software may be licensed by physical core, virtual core, processor, user, or another measure. A cloud vCPU is not automatically equivalent to one licensed core under every agreement. Resizing instances, adding replicas, enabling disaster recovery, or scaling out can change the required entitlement. Migration overlap may also require additional rights if the old and new deployments run simultaneously.

Compare total cost rather than assuming BYOL is always cheaper. Include infrastructure, maintenance, support, dedicated capacity where required, administration, and unused license capacity. License-included pricing may suit variable demand, while BYOL may be economical for stable workloads with suitable existing entitlements. Reserved capacity discounts and other infrastructure purchasing commitments are separate from software license portability; buying a compute discount does not supply missing software rights.

In practice, inventory licenses before migration, validate terms with the vendor or authorized licensing specialists, map entitlements to the proposed architecture, and track consumption as the deployment changes. License-management tools can help record limits and detect usage, but they do not override contracts or guarantee compliance. For exam questions, remember the central distinction: BYOL reuses eligible customer-provided licenses, whereas license-included pricing bundles the specified software rights with the cloud offering.