1 ‐ OCI to Azure Migration Steps - SanjeevOCI/Azure GitHub Wiki

OCI to Azure Migration Steps:

1. Cost Estimation

Utilize the Azure Pricing Calculator to estimate migration costs from OCI to Azure. Adjust estimates based on your organization’s specific configurations and requirements.

2. Activities & Assignments

📌 Tasks and responsibilities assigned to respective teams.

Step Activity Responsible Team
1.1 Cost Estimation using Azure Pricing Calculator Architect
2.1 Document OCI Inventory Architect
2.2 Plan Network Architecture in Azure Architect
2.3 Obtain Sign-Off on Network Plan Architect, Stakeholders
2.4 Implement Landing Zone in Azure Architect
2.5 Provision App & Database Services Architect
2.6 Establish OCI-Azure Connectivity Architect
2.7 Request Data Sharing for Migration App/DB Admin
2.8 Execute Data Transfer from OCI to Azure Architect
2.9 Configure Application & Database in Azure App/DB Admin
2.10 Validate Subnet Interconnectivity Architect
2.11 Perform Application & Database Testing Testing Team
2.12 Set Up Development Environment Dev Team
2.13 Configure Test/UAT Environment Testing Team
2.14 Deploy Production Environment Prod/Testing Team
2.15 Execute Final Cutover to Azure All Teams
2.16 Conduct Go/No-Go Review All Teams, Client
2.17 Confirm Migration Completion & Post-Migration Review All Teams

3. Migration Process - Step by Step

3.1 Inventory Documentation (Architect)

  • List all resources in OCI, including compute, storage, databases, networking, and other services.
  • Identify dependencies and interconnections.
  • Prepare a detailed inventory document with configurations.

3.2 Network Architecture Design (Architect)

  • Design the network structure in Azure, defining VNets, subnets, NSGs, and other components.
  • Ensure high availability and disaster recovery needs are addressed.
  • Create a network diagram for approval.

3.3 Stakeholder Sign-Off (Architect)

  • Review the network and migration plan with stakeholders.
  • Implement feedback-based adjustments.
  • Obtain formal approval before proceeding.

3.4 Landing Zone Implementation (Architect)

  • Set up the initial Azure environment with resource groups, IAM roles, and policies.
  • Establish foundational components like VNets, subnets, and management groups.

3.5 Application & Database Services Setup (Architect)

  • Provision required compute resources (VMs, App Services, etc.) and databases (Azure SQL, Cosmos DB, etc.).
  • Configure services to ensure compatibility and performance.

3.6 Secure OCI-Azure Interconnection (Architect)

  • Establish secure connectivity between OCI and Azure using VPN, ExpressRoute, or other methods.
  • Verify network communication and configurations.

3.7 Data Sharing Request (App/DB Admin)

  • Coordinate with the application/database team to share necessary data for migration.
  • Ensure all required datasets are identified and ready for transfer.

3.8 Data Migration Execution (Architect)

  • Plan and execute data transfer from OCI to Azure using Azure Data Migration Service or other tools.
  • Validate data integrity post-transfer.

3.9 Application/Database Setup (App/DB Admin)

  • Set up applications and database servers in Azure.
  • Perform necessary configurations and adjustments.

3.10 Subnet Connectivity Verification (Architect)

  • Ensure proper interconnectivity between subnets within Azure.
  • Validate routing, security, and performance settings.

3.11 Application & Database Testing (Testing Team)

  • Conduct functional, performance, and security testing of migrated applications and databases.

3.12 Development Environment Setup (Dev Team)

  • Set up and validate the development environment in Azure.
  • Ensure all required tools and resources are available.

3.13 Test/UAT Environment Setup (Testing Team)

  • Configure and validate the test/UAT environment in Azure.
  • Conduct User Acceptance Testing (UAT) and resolve issues.

3.14 Production Environment Setup (Prod/Testing Team)

  • Deploy and validate the production environment in Azure.
  • Ensure operational readiness for final migration.

3.15 Final Cutover Execution (All Teams)

  • Perform the final migration cutover to Azure.
  • Monitor the process and address any issues promptly.

3.16 Go/No-Go Decision (All Teams & Client)

  • Assess migration status and make the Go/No-Go decision.
  • Ensure all critical concerns are resolved before going live.

3.17 Migration Completion & Post-Migration Review (All Teams)

  • Confirm successful transition to Azure.
  • Conduct a final review and provide post-migration support.

This version enhances clarity, structure, and readability while maintaining all key details. Let me know if you need further refinements! 🚀