This is a step-by-step migration guide within the Oracle Knowledge Hub. For a full architectural overview, see our Oracle Cloud at Customer: The Complete Guide. For contract negotiation specifics, see How to Negotiate Oracle Cloud at Customer Contracts.
📋 Table of Contents
- Assess Your Current Oracle Environment
- Perform Detailed Workload Analysis
- Engage Independent Expertise
- Plan Capacity, Licensing & Cloud Commitments
- Prepare Your Data Centre and Network
- Deploy and Migrate in Phases
- Post-Migration Optimisation
- 9 Key Recommendations
- Migration Action Checklist
- Frequently Asked Questions
1. Assess Your Current Oracle Environment
Begin by evaluating your existing Oracle landscape. Inventory all Oracle software and infrastructure to understand what you have and how it is used. Check versions of databases and applications. Legacy versions (e.g., older Oracle Database releases) may require upgrades to be compatible with Oracle Cloud at Customer. Document current CPU, memory, and storage utilisation levels. This baseline assessment reveals your true resource needs and any gaps.
Develop a comprehensive picture of your Oracle estate's workload patterns. For example, identify peak CPU usage periods and memory hogs. If you find an Oracle Database running on an outdated version (say 11g or 12c), plan to upgrade to a supported version before migration to avoid compatibility issues. A thorough assessment ensures you only move what is needed and can right-size the Cloud at Customer environment. Use Oracle licence compliance scripts and internal discovery tools to build an accurate picture.
For guidance on running a structured assessment, see our Oracle Cloud Migration Readiness Assessment and how to conduct an internal Oracle licence audit.
2. Perform Detailed Workload Analysis
With an inventory in hand, dive deeper into technical workload analysis. Utilise tools such as Oracle's Automatic Workload Repository (AWR) reports or monitoring data to profile performance. Look at peak vs. average utilisation, storage growth trends, and I/O throughput requirements. This analysis might take a few weeks, but it is critical to accurately size the Cloud at Customer solution.
It helps you determine how many OCPUs (Oracle CPU cores), how much storage, and what network capacity you will require. Understanding Oracle's licence minimums and counting rules is essential here, as they directly affect your sizing calculations.
Oracle Cloud at Customer offerings come in different flavours. For example, Exadata Cloud@Customer for databases, or Dedicated Region for a full on-prem cloud. Your analysis will indicate which option is the best fit. For a detailed comparison, see Cloud at Customer vs. Dedicated Region.
One global retailer discovered through AWR analysis that its average database CPU usage was 30% of on-premises capacity, enabling them to consolidate and select a smaller Exadata configuration than Oracle's initial recommendation. Data-driven analysis prevents oversizing the hardware and cloud services.
3. Engage Independent Expertise and Plan Strategy
Do not plan in a vacuum. Seek independent advice to validate your findings and strategy. Involve a third-party Oracle licensing or cloud expert (or an internal architecture review board) to get an unbiased second opinion. These experts can highlight if Oracle's sales proposals are inflated and suggest cost-saving configurations.
Use their input to refine your target architecture and migration roadmap. Additionally, build a strong business case for the migration. Align the Cloud at Customer move with business objectives, such as improving performance, ensuring data sovereignty, or reducing data centre costs.
Leverage external advisors to challenge vendor assumptions. This helps dictate migration terms on your own needs, not Oracle's selling agenda. For example, an unbiased review might reveal you only need 50 OCPUs of database capacity, not the 100 OCPUs Oracle pitched. Use that to adjust the plan and avoid overspending. Read about 20 key considerations for managing Oracle contracts.
Need Independent Oracle Cloud@Customer Advisory?
Redress Compliance provides completely vendor-independent Oracle advisory services. We help enterprises right-size deployments, negotiate favourable contracts, and avoid common licensing pitfalls.
4. Plan Capacity, Licensing, and Cloud Commitments
Plan the commercial and capacity aspects of your Oracle Cloud at Customer deployment. Oracle will offer a subscription that includes on-prem hardware plus cloud services via Oracle Universal Cloud Credits (UCC). Break down the cost components: typically, the hardware appliance (Exadata rack or OCI rack) is a fixed subscription portion (often around 25–30% of total cost), and the cloud service usage (OCPUs, storage, etc. via UCC) will be the majority of the spend.
Licensing Model Options
Cost Saver
✅ Bring Your Own License (BYOL)
- Use existing Oracle software licences on Cloud at Customer
- Lowers cloud usage fees significantly
- Must keep licences under active support
- Cost-effective if you have already invested in licences
- Requires careful compliance tracking
Simpler
📦 License-Included
- Oracle provides software licences as part of the subscription
- Simplifies compliance: Oracle manages the licences
- Typically costs more per unit
- Useful if you lack certain licences
- No need to track BYOL rules
Negotiation Tips for Cloud Commitments
Negotiation is key in this phase. Oracle often requires a multi-year commitment (commonly 4 years) with a minimum annual UCC purchase. Negotiate the UCC commitment based on realistic usage. For detailed negotiation strategies, see our Oracle Cloud Negotiations guide and Oracle Cloud Contracts and Credits for CIOs.
If your migration will ramp up over 12 months, do not commit as if you will use full capacity from day one. Consider committing to a lower UCC spend in Year 1 and increase commitments in later years as usage grows. Push for volume discounts on UCC. Oracle offers tiered discounts (e.g., 10% off at a certain spend level, higher for bigger commitments). Negotiate flexibility where possible, such as the ability to adjust your cloud credit commitment annually, or protections against price hikes in renewals. See Oracle Renewal Negotiation Checklist for key clauses.
Common Contract Pitfalls
| Contract Pitfall | Consequence | How to Avoid |
|---|---|---|
| Overcommitting to cloud credits | Paying for unused cloud services if actual consumption falls short | Start with conservative commitments; scale up as needed. Ensure contract allows unused credits carryover or adjustment. See UCC guide. |
| Oversized hardware configuration | Excess capacity increases costs with no performance benefit | Right-size based on your analysis. Include scalability options to add capacity later rather than overbuying now. |
| Ignoring BYOL vs. included licence options | Unnecessary spend or compliance issues if chosen incorrectly | Evaluate current licences. Use BYOL to save costs if you have licences and support. Choose licence-included only where needed. |
| Long-term lock-in without exit plan | Limited flexibility if business needs change | Negotiate termination rights or the ability to reduce scope in later years. Read Oracle Contract Terms Glossary. |
Read: How to Negotiate Oracle Cloud at Customer Contracts | Oracle Contract Negotiation Service | Oracle License Conversion Programs for Cloud
5. Prepare Your Data Centre and Network
Oracle Cloud at Customer involves Oracle shipping and installing hardware in your data centre. Ensure your facilities are ready well in advance.
🏢 Space, Power, and Cooling
Verify that you have sufficient rack space, a suitable power supply, and adequate cooling for Oracle's equipment. Oracle typically provides specifications (e.g., a full rack Exadata with specific power draw requirements). The data centre must meet Oracle's standards for security and environment since the hardware remains Oracle-owned.
🔗 Network Connectivity
Set up a robust network connection between the Cloud at Customer hardware and Oracle's cloud network. Most deployments require a connection to Oracle's public cloud for management and updates, via secure VPN or a dedicated Oracle FastConnect circuit. Plan for redundant links if high availability is needed. See Oracle licensing for disaster recovery for HA/DR considerations.
🔒 Security and Access
Collaborate with Oracle to fulfil security requirements. This may include providing controlled physical access for Oracle engineers, meeting encryption or firewall requirements, and integrating the appliance into your identity management for user access.
👥 Team Readiness
Prepare your IT staff to manage a hybrid cloud environment. Oracle will handle hardware maintenance and cloud infrastructure management tasks (like patching the control plane). However, your team will still manage your applications and databases on the Cloud at Customer stack. Plan training sessions so administrators understand the new tooling, including managing licences in OCI environments.
Verifying network settings and running a connectivity test with Oracle before the hardware arrives can save days of troubleshooting. A well-prepared environment means that when Oracle delivers the system, it can be installed and configured without delay, keeping your timeline on track.
6. Deploy and Migrate in Phases
With the contract signed and preparations done, Oracle will deliver and install the Cloud at Customer hardware. Deployment typically takes 4–8 weeks from order to having the system on-site and operational. Coordinate closely with Oracle's team for a smooth installation.
Once live, approach migration of workloads in planned phases. Start with lower-risk or non-production systems as a pilot. This phased migration allows your team to gain experience on the new platform and resolve any issues on a smaller scale. Next, migrate your critical production workloads, scheduling cutovers during approved maintenance windows.
Data Transfer and Testing
Before switching over, ensure all data is transferred and applications are thoroughly tested on the Cloud at Customer environment. Running in parallel or doing trial runs can validate performance. Use proven migration tools and methods. Oracle provides utilities like Data Pump or Zero Downtime Migration for databases.
Minimise Downtime
Plan for the actual go-live of each system carefully. If near-zero downtime is required for a database, you might employ Oracle GoldenGate replication or other strategies. If some downtime is acceptable, schedule it during off-hours and communicate the schedule to stakeholders. Have a rollback plan in case of unexpected issues.
Migrations can range from 6 to 18 months in duration. A simple Oracle environment might be fully migrated in half a year, while a large enterprise with many interdependent systems could take over a year. Avoid rushing to consume all cloud services immediately. Use your phased approach to ensure stability.
7. Post-Migration Optimisation and Management
After migrating, the journey is not over. Now it is about operational excellence on Oracle Cloud at Customer. Ensure you have proper monitoring in place. Leverage Oracle's cloud management tools to watch resource utilisation (CPU, memory, storage), performance metrics, and up/down status of services. See our 32 OCI cost optimisation strategies for practical tips.
Cost Governance
Cost governance is a key post-migration task. Regularly review your cloud credit consumption against your committed amount. If you consistently use less than what you are committed to, consider scaling down or using more of the services you are paying for. Conversely, if usage is trending above expectations, plan for capacity increases or contract adjustments. Our Oracle Cost Optimisation Playbook covers this in depth.
Performance Tuning
Fine-tune databases and applications running on Cloud at Customer. The underlying hardware (such as Exadata) may offer performance features you can exploit, including smart indexing and caching, to gain even more value. See our Oracle Database Licensing & Options Playbook for insights on features that require additional licensing vs. those included.
Scalability Planning
Regularly revisit scalability plans. Oracle Cloud at Customer can often scale by adding more hardware racks or enabling more OCPUs. Work with Oracle proactively if you foresee needing expansion, as adding hardware might have lead times.
Stay Compliant
Since this is your on-premises environment, you are responsible for compliance with any applicable data regulations. Verify that all security controls are effective, including encryption, access controls, and audit logs, especially in regulated industries such as finance or healthcare. For licensing compliance, regularly run Oracle compliance scripts and review on-prem to cloud portfolio management.
Manage the relationship with Oracle carefully. Hold regular service reviews to discuss performance, support issues, and optimisation opportunities. Keep an eye on the end of your subscription term well in advance: decide whether you will renew, expand, or terminate the Cloud at Customer service. See our Oracle support renewal contract checklist for key clauses to review before renewal.
✅ 9 Key Recommendations
Conduct Thorough Analysis First
Do not rely solely on Oracle's sizing. Use your own metrics and tools to determine exactly what capacity and services you need. See Oracle Licensing Calculator.
Leverage Existing Licences
Utilise BYOL pricing if you have underutilised Oracle licences. It can significantly reduce your cloud costs. Track compliance with OCI BYOL strategy.
Negotiate in Detail
Treat the Cloud@Customer contract as you would any major enterprise agreement. Negotiate discounts on cloud credits, seek flexible terms, and clarify responsibilities in writing.
Plan for the Long Term
Design your environment with future growth in mind. Start at a size that meets current needs but can scale. Read CIO Playbook: Cloud@Customer Deployment Strategy.
Invest in Network and Security Upfront
Ensure your network connectivity is robust and secure. Use dedicated connections and implement all necessary security controls from day one.
Train and Empower Your Team
Bridge skills gaps by training IT staff on managing Oracle Cloud at Customer tooling, consoles, and APIs. See managing licences in OCI environments.
Migrate Gradually and Test Thoroughly
Avoid big-bang migrations. Move in phases and conduct thorough testing after each phase. Plan DR strategies for each cutover.
Monitor Usage and Optimise Costs
Schedule regular reviews of cloud credit usage. Shut down non-prod environments when not needed. See OCI Cost Optimisation.
Maintain Vendor Independence
Continue to keep an eye on the broader cloud market. Avoid customisations that lock you in too tightly. Keep Oracle accountable to SLAs. Compare with OCI vs. AWS for Oracle workloads.
📋 Migration Action Checklist
Inventory and Assess
Gather data on all Oracle systems (versions, usage stats, dependencies). Identify any upgrades or changes needed to run on Oracle Cloud at Customer. Use licence information tools and audit risk assessments.
Define Requirements and Strategy
Determine the right Cloud at Customer offering and sizing for your needs, using independent expert input. Build a business case and migration plan. See Cloud@Customer vs. Dedicated Region.
Negotiate the Deal
Right-size the hardware and cloud credit commitments, choose a licensing model (BYOL vs included), and secure discounts and favourable terms. See negotiation guide.
Prepare Infrastructure
Ready your data centre for the incoming Oracle hardware (space, power, cooling). Set up network connections and ensure security policies are in place.
Execute Migration in Phases
Start with a pilot, thoroughly test, then move critical applications. Monitor outcomes of each phase before proceeding. See which Oracle software runs on Cloud@Customer.
Frequently Asked Questions
The first step is to analyse your current Oracle environment. Identify what software and workloads you have, check their versions, and gather performance data. This assessment determines readiness and sizing for the Oracle Cloud at Customer migration. Use Oracle compliance scripts and internal audit processes to build an accurate baseline.
Yes. Oracle Cloud at Customer supports a Bring Your Own License (BYOL) model. You can apply your current Oracle licences (with active support contracts) to the Cloud at Customer environment, which lowers the service fees. If you prefer not to use BYOL or lack certain licences, you can opt for a licence-included subscription where the licence cost is built into the hourly rates, though this is generally more expensive. See our BYOL comprehensive guide and BYOL vs. License-Included cost comparison.
Deployment and migration happen in stages. The Oracle-supplied hardware typically arrives and is set up within approximately 4 to 8 weeks after the contract is signed. The subsequent migration of workloads can take anywhere from 6 to 18 months, depending on complexity. Simple environments may complete in half a year, while large enterprises with many interdependent systems could take over a year.
You will need to ensure your data centre can accommodate the Oracle Cloud at Customer equipment. This means having sufficient rack space, power, cooling, and physical security. Additionally, set up a reliable network connection to Oracle's cloud (for management and updates). Oracle usually provides guidance and can run workshops to help with network and security preparedness.
Cost control starts with accurate planning. Commit to cloud usage based on realistic needs (do not overcommit). During migration, use a phased approach so you are not paying for full capacity before you use it. After migration, closely monitor your consumption of Oracle cloud credits. If you notice underutilisation, consider adjusting usage or negotiating lower commitments. Also shut down idle resources (non-production environments when not in use) to minimise waste. See our Oracle Cost Optimisation Playbook.
🚀 Ready to Migrate to Oracle Cloud at Customer?
Our independent Oracle licensing experts help enterprises plan, negotiate, and execute Cloud at Customer migrations, ensuring you get the right sizing, favourable contract terms, and a smooth transition.
Oracle Advisory Services | Contract Negotiation | Book a Meeting
📚 Related Reading
Oracle Cloud at Customer: The Complete Guide → Oracle Exadata Cloud at Customer → How to Negotiate Cloud at Customer Contracts → Cloud at Customer vs. Dedicated Region → Which Oracle Software Runs on Cloud@Customer → Cloud at Customer vs. Oracle OCI → CIO Playbook: Cloud@Customer Deployment Strategy → Oracle BYOL: Comprehensive Guide → BYOL vs. License-Included Cost Comparison → Oracle Universal Cloud Credits Guide → Oracle Cloud Negotiations → Oracle Cloud Contracts for CIOs → OCI Cost Optimisation → 32 OCI Cost Optimisation Strategies → Oracle Cost Optimisation Playbook → Oracle License Conversion Programs → OCI vs. AWS for Oracle Workloads → Oracle Support Renewal Checklist → Oracle Exadata Licensing Strategy → OCI BYOL Licensing Strategy →Explore Oracle Advisory Services
Vendor-independent. Fixed-fee. Proven results across hundreds of enterprise engagements.