Oracle Product Migration
By Aziz Islam.
Migrations involve many different older licensing and pricing metrics and methodologies and are affected by the rights granted under the original licenses.
Why migration?
There could be many reasons that necessitate an Oracle software license migration. I.e.
- To ensure that licenses remain useful and valuable over time,
- Changes in technologies and businesses need to evolve.
- To facilitate effective license management.
Types of Migrations.
- Supported Product Migration: allows those with supported licenses to receive an update for an older product as described in Oracle’s Technical Support Policies
2. License Migration: is a means of contractually modifying an end user’s Oracle licenses purchased under older license metrics (e.g. Concurrent Device) to take advantage of current license metrics (e.g. Processor).
3. License upgrade: is a means of contractually changing an existing license from –
- a more restrictive to a less restrictive level (e.g., Application Specific Full Use to Full Use, or Named User Plus to Processor);
- more limited functionality to more expansive functionality (e.g., Database-Standard Edition to Database-Enterprise Edition); and/or
- a shorter term to a longer term (e.g., 2-year term to perpetual).
As a general rule, license downgrades (e.g., Database-Enterprise Edition to Database-Standard Edition) are not permitted.
Please keep in mind that your license migration is dependent on an existing license configuration and grant, and therefore may not be identical to the another end-user. Accordingly, you’ll want to review the specifics of migrating Oracle licenses with your SAM vendor. Akoft can assist you to understand the types of migrations that are available and the key calculations used in those migrations.
For more information please send an email to – info@akoft.com.
