Oracle ULA Certification 90-Day Countdown Checklist
90 Days to ULA Certification: Your Week by Week Playbook

Why the 90-Day Window Matters: Oracle Pressure and What Is at Stake

When your Oracle ULA expires in 90 days, a timer starts that affects millions of dollars in licensing decisions. Oracle knows your ULA is ending. Their sales team has already begun outreach, offering renewal incentives, PULA alternatives, or cloud migration discounts. The pressure is intentional and relentless. Your procurement team is juggling executive priorities. Your technical teams may not understand why a forgotten test environment matters. IT operations may not even know the ULA is expiring.

Here is what is really happening in those 90 days: you must count every processor, every Named User Plus license, every virtualization configuration, and every cloud instance deployed within a 30-day snapshot window. Oracle's own License Management Services tools capture only 90-day snapshots; they do not retain long-term peak usage data. This means if you deployed 100 virtual machines for three months before your ULA expires and then shut them down, Oracle may claim you owe licenses for that temporary spike. Missing one forgotten test VM, one development instance, or one cloud database could leave you unlicensed after ULA exit, exposing you to audit penalties and renegotiation leverage.

The stakes are enormous. A Fortune 500 bank in the financial services sector avoided a $30M renewal by exiting strategically, and saved 40% over three years by diversifying to third-party support. A US manufacturer saved $4M per year after ULA exit by moving to open-source Java and third-party database support, totaling $12M over three years. A professional services firm saved $7M. A technology company saved $10M over three years. Typical savings for organizations that certify out instead of renewing range from 25 percent to 60 percent of proposed Oracle renewal costs.

The certification process is your moment to take control. You must complete a formal, legally defensible inventory in time to make a renewal decision, secure executive sign-off, and prepare for post-exit audit. Oracle has specific audit windows open 12 to 24 months after ULA exit. If your certification is incomplete or your internal documentation is weak, you are entering that audit period at a disadvantage.

Weeks 1 Through 4: Discovery and Inventory

The first four weeks are about seeing everything you have deployed. This is not optional and it is not easy. You will need to coordinate with infrastructure, database, development, and cloud teams.

In week one, initiate a formal software asset management assessment. Contact our ULA Certification Readiness Assessment to baseline your current deployment scope. Work with your infrastructure team to identify all servers running any Oracle product. Use Oracle's own LMS tools if available, but do not rely on them exclusively. They have blind spots. Specifically, request a historical deployment report showing all Oracle software installed or running in the preceding twelve months. This is critical because Oracle may claim you owed licenses for products you shut down but did not permanently remove.

In week two, expand the search to cloud. Work with your AWS, Azure, OCI, and any other cloud teams to list every instance running Oracle Database, Oracle Fusion, Oracle WebLogic, Oracle Java, or any other licensed product. Count the instance types, the core counts, and the regions. Cloud usage is counted as a 12-month average. If you ran 100 virtual machines in the cloud for three months before ULA expiration, Oracle credits you for approximately 25 instances on average. Do not assume cloud is outside scope. Most ULA agreements cover cloud deployment, but some older contracts contain ambiguous language. Review your specific ULA language with your procurement team.

In weeks three and four, commission a full discovery scan using tools like Flexera, Aspera, or your own IT audit systems. Identify every processor, every virtual CPU, every Named User Plus assigned to any Oracle product. Document operating system versions, database patch levels, and product edition. Many organizations discover orphaned instances they forgot about: development environments, testing sandboxes, disaster recovery standby systems, or legacy applications running Oracle Database in read-only mode. All of these count toward your certified footprint if they are active within your certification window.

Weeks 5 Through 8: Optimization and Strategic Deployment

With full visibility into your estate, you can now optimize before certification. This is where your exit strategy becomes concrete.

In week five, classify all instances into three buckets: keep, migrate, and retire. Instances you will keep on-premises or in cloud should remain within your deployment footprint. Instances you will migrate to open-source alternatives like PostgreSQL, MySQL, or MariaDB should be retired before your certification date. Instances running legacy Oracle products with no business value should be shut down and decommissioned now, not after your ULA ends. Removing a test environment before your certification snapshot date means Oracle has no claim to licenses for that instance. This is legal optimization and it is essential.

In weeks six and seven, execute your retirement plan. Shut down development instances you do not need. Migrate non-critical workloads away from Oracle. This is your window to reduce your certified footprint without penalty. Talk to your technical teams about consolidation. Can you retire redundant database instances? Can you move Java workloads to open-source frameworks? Can you freeze feature development on legacy Oracle applications until after your ULA expires? The goal is to certify the smallest defensible estate you can support, allowing you to exit at a lower annual baseline.

In week eight, document all changes you have made. Create a detailed spreadsheet showing which instances were active, when they were decommissioned, and why. Include signed approvals from your application owners and infrastructure lead. This documentation becomes part of your certification evidence. If Oracle questions your certified count later, your contemporaneous records of deployment decisions protect you.

Weeks 9 Through 12: Certification Execution and Post-Exit Defense

The final sprint is about formalization, sign-off, and audit preparation.

In week nine, run your final discovery snapshot. This is your official certification window. Count every active instance as of this date. Reconcile against your internal inventory tracking. Resolve discrepancies. Your infrastructure and database teams must confirm counts with sign-off. This snapshot becomes your binding certification to Oracle.

In week ten, prepare your certification submission package. Oracle requires a signed executive statement certifying worldwide deployments and usage. Your Chief Information Officer or Chief Financial Officer typically signs this statement, declaring under penalty of perjury that your organization has disclosed all active Oracle products. Prepare this document with your legal team. Include supporting evidence: asset management reports, infrastructure diagrams, database server lists, and cloud deployment manifests. Organize this material so it is retrievable and defensible during future audit.

In weeks eleven and twelve, submit your certification to Oracle and secure internal approval for your post-ULA strategy. Whether you are renewing, exiting to open-source, or transitioning to third-party support, your board and CFO need to understand the financial impact. Document your decision with supporting analysis. Did you model the cost of renewal versus exit? Did you evaluate Vendor Shield audit defense services? Did you price third-party database support, Java support, or middleware licensing alternatives? For complex organizations, this analysis can mean the difference between a renewal lock-in and a successful transition.

Many organizations leverage professional guidance at this stage. Our ULA Negotiation Services specialize in structuring exit strategies and managing the formal certification submission. We have completed certifications for 500+ organizations and routinely identify cost optimization opportunities in the final weeks that save 15 to 25 percent on post-exit licensing.

What Happens After Certification: Post-Exit Audit Readiness

Your certification is submitted, but your exposure is not finished. Oracle maintains audit rights for 12 to 24 months after ULA exit. During this window, Oracle can request detailed deployment records, library files, configuration files, and historical system logs. They are looking for evidence of unlicensed usage, products you certified as not deployed but actually used, or deployment models you did not fully disclose.

Prepare your audit defense file now while your infrastructure is fresh in memory. Gather your discovery reports, your snapshot counts, your decommissioning records, and your executive certification statements. Store these securely and make them readily retrievable. Work with your LMS audit response team to understand Oracle's likely audit questions. Have your procurement team maintain a log of all oracle communications during the certification period. If Oracle sends you audit notices post-exit, you want immediate, comprehensive, professional response.

Consider proactive audit support. If your organization deployed Oracle products in complex cloud architectures or if you have any uncertainty about your certification accuracy, engage audit advisors before Oracle initiates formal audit. A pre-emptive conversation with Oracle is often less disruptive than a surprise audit letter. Our advisory services specialize in post-exit audit defense and help organizations resolve Oracle questions with confidence.

Your post-ULA strategy should also address java support, database support alternatives, and middleware licensing options. If you are exiting Oracle entirely, review our Java Renewal Strategy and our white paper collection for migration guidance. If you are adopting a cloud-first architecture, consult our ULA Landing Page for post-certification deployment optimization.