Project 1 – Enterprise Cloud Migration Planning

1. System Architecture & Current Infrastructure

Before any cloud resource is provisioned, cloud engineers must understand exactly what a company already has. This section maps the current on-premises infrastructure of ABC Retail Pvt. Ltd. and compares it with the target cloud architecture. Every migration starts by answering the question: what are we moving, and why?

⚠ Remember: No Cloud Account Needed for Project 1 This project is entirely about planning and documentation. You will create Word documents, spreadsheets, and architecture diagrams using tools available on your computer. No cloud platform login is required.

2. Step-by-Step Action Items

Follow these tasks in order. Each task builds on the previous one. Take your time — this project is about understanding, not speed. Read each explanation carefully before moving forward.

TASK 1 Understand the Business – Read the Company Profile

Before making any technical decisions, you must understand the business. A cloud engineer who deploys servers without understanding business needs will make wrong decisions. This is the most important step.

Open a blank Word document or Google Doc. Title it: ABC Retail – Cloud Migration Strategy. This will be your main deliverable document throughout this project.

Create a section called "Executive Summary". In 2–3 sentences, write who ABC Retail is, what their main problem is, and what the goal of this migration plan is.

Create a section called "Business Analysis". List the company's current challenges using bullet points. Reference the Business Scenario at the top of this page.

ABC Retail Pvt. Ltd. – Business Challenges: • Hardware maintenance costs are increasing every year • Adding new servers takes 4–6 weeks (procurement + installation) • Disaster recovery is manual and unreliable (external HDDs) • Storage capacity is nearly full • IT team spends 80% of time maintaining hardware, not innovating • Company wants to expand to new cities but infrastructure won't scale • 200 employees across multiple branch offices need reliable access

You are listing the pain points so that every technical recommendation you make later can be directly tied back to solving a specific business problem. This demonstrates professional consulting thinking — each cloud service you recommend must solve a real problem, not just look impressive on paper.

Create a "Business Goals" section. Write what the company wants to achieve after the migration. Keep it in business language (not technical jargon).

Business Goals: • Reduce monthly IT infrastructure costs by 30-40% • Achieve 99.9% website availability (no more outages) • Enable the IT team to scale server capacity in minutes, not weeks • Support company expansion to 5 new cities in the next 2 years • Improve disaster recovery from days to hours • Allow employees to work from any branch office seamlessly

Writing goals in measurable terms ("30-40% cost reduction") makes your proposal credible and gives the company a way to measure success after migration. Vague goals like "improve performance" are unprofessional in real consulting proposals.

TASK 2 Assess the Existing Infrastructure – Build an Inventory

You cannot plan a migration without knowing what you are migrating. A proper infrastructure inventory is the foundation of every migration project. In real projects, this step involves running discovery tools on servers — but here we will build it from the business scenario.

Open a new spreadsheet (Microsoft Excel or Google Sheets). Name the file: ABC Retail – Infrastructure Inventory.xlsx

Fill in each row based on the company scenario. Use the table below as your starting template:

System	Type	Purpose	Priority	Cloud Service
Web Server	Physical Server	Hosts company website	HIGH	Virtual Machine (IaaS)
Database Server	Physical Server	Customer & order data	HIGH	Managed SQL Database (PaaS)
File Server	Physical Server	Employee documents	MEDIUM	Cloud File Storage / SharePoint
ERP System	Business Application	Enterprise resource planning	LOW	SaaS ERP or Replatform
Email System	Application	Internal communications	LOW	Microsoft 365 (SaaS)
Backup System	External HDDs	Data backup	HIGH	Cloud Backup Service

The inventory table is your single source of truth for the migration. The Priority column tells the team which systems to migrate first — high-priority systems are those that affect customers directly (website, database) or those that are most at risk of failure (aging hardware). Low-priority systems may be migrated later or replaced with SaaS products.

Save the spreadsheet and add a reference to it in your main strategy document: "See Appendix A: Infrastructure Inventory"

TASK 3 Cloud Readiness Assessment – Is the Company Ready?

Not all companies are equally ready for cloud migration. A readiness assessment identifies gaps that must be addressed before migration begins. Skipping this step leads to project failures.

Add a new section to your strategy document called "Cloud Readiness Assessment".

Create a readiness table evaluating the company across 6 key dimensions. Score each area as: ✅ Ready / ⚠ Partial / ❌ Not Ready.

Assessment Area	Status	Details	Action Required
Technical Infrastructure	⚠ Partial	Aging servers, no virtualization in place	Start with lift & shift for web servers
IT Staff Skills	❌ Not Ready	No cloud experience in current IT team	Cloud training for 3–5 key engineers
Application Compatibility	✅ Ready	Standard web apps, modern database schemas	Minor configuration changes needed
Budget	⚠ Partial	Migration budget approved, ongoing costs TBD	Complete cost-benefit analysis
Security & Compliance	⚠ Partial	Basic security policies exist	Update policies for cloud environment
Network Connectivity	✅ Ready	Existing internet connections adequate	Consider Direct Connect for production

The readiness assessment prevents the most common migration mistake: rushing into cloud deployment without the skills, budget, or technical foundation to succeed. By identifying "IT Staff Skills" as NOT READY, you are recommending that the company invest in training before migration begins — this is how professional consultants protect their clients from expensive failures.

Write a "Readiness Summary" paragraph underneath the table that summarizes the overall readiness level and lists the top 3 things the company must do before starting migration.

TASK 4 Recommend Cloud Models – Public, Private, or Hybrid?

Choosing the right cloud deployment model is one of the most important decisions in a migration project. The wrong choice costs money and creates security risks.

Add a section: "Cloud Deployment Model Recommendation" to your document.

Compare the three main models and explain why one fits ABC Retail better than the others:

Cloud Deployment Model Analysis for ABC Retail: PUBLIC CLOUD: ✓ Pay-as-you-go — reduces upfront hardware cost ✓ Global infrastructure — supports expansion to new cities ✓ Managed services — reduces IT maintenance burden ✗ Less control over physical hardware PRIVATE CLOUD: ✓ Maximum control and isolation ✗ Requires significant capital investment in hardware ✗ Does NOT solve the hardware maintenance problem ✗ Cannot easily scale globally HYBRID CLOUD (RECOMMENDATION): ✓ Migrate non-sensitive workloads to public cloud FIRST ✓ Keep sensitive financial data on-premises temporarily ✓ Gradually move everything to public cloud over 12-18 months ✓ Reduces risk by migrating in phases ✓ Meets security concerns during transition period

A Hybrid Cloud recommendation is most appropriate for ABC Retail because it allows the company to start benefiting from cloud immediately while maintaining control over sensitive data during the transition. This phased approach reduces business risk and allows the IT team to develop cloud skills gradually rather than requiring an overnight transformation.

Add a Service Model table mapping each workload to the most appropriate cloud service model (IaaS, PaaS, or SaaS):

Workload	Service Model	Example Service	Reason
Web Server (Website)	IaaS	AWS EC2 / Azure VM	Need OS control for custom config
Customer Database	PaaS	AWS RDS / Azure SQL	Managed backups, no DBA needed
File Storage	PaaS	AWS S3 / Azure Blob	Unlimited, cheap, geo-redundant
Email & Collaboration	SaaS	Microsoft 365	No infrastructure to manage
ERP System	SaaS / PaaS	Rehost then evaluate	Migrate first, modernize later

Mapping each workload to a service model is important because using the wrong model wastes money. Using IaaS (virtual machines) for email when a SaaS solution exists means paying for and maintaining servers unnecessarily. Each model recommendation must be justified with a business or technical reason.

TASK 5 Select Migration Strategies – The 6 Rs Framework

Not every application migrates the same way. Cloud professionals use the "6 Rs" framework to choose the right approach for each workload. Using the wrong strategy is one of the most common — and costly — migration mistakes.

Add a section: "Migration Strategy – The 6 Rs"

Define each of the 6 Rs in your document with a brief explanation:

THE 6 Rs OF CLOUD MIGRATION: 1. REHOST (Lift & Shift) Move the application to a cloud VM without changes. Best for: Applications that work as-is, fastest migration. Example: Move the web server from physical to a cloud VM. 2. REPLATFORM (Lift, Tinker & Shift) Move with minor optimizations (e.g., switch to managed database). Best for: Apps where you want some cloud benefits without full rewrite. Example: Move database to managed AWS RDS instead of self-managed. 3. REFACTOR / RE-ARCHITECT Redesign the application to be cloud-native. Best for: Critical apps needing major improvement. Example: Break monolithic ERP into microservices. 4. REPURCHASE Replace with a commercial SaaS product. Best for: Commodity software with SaaS alternatives. Example: Replace internal email server with Microsoft 365. 5. RETIRE Decommission systems no longer needed. Best for: Duplicate or obsolete systems. Example: Retire old backup tape system. 6. RETAIN Keep on-premises (for now). Best for: Systems with regulatory requirements or high risk. Example: Keep financial records on-premises during Year 1.

The 6 Rs framework exists because organizations often make the mistake of thinking every application should be "lift and shifted" (simply moved as-is to the cloud). In reality, a database that is simply moved to a cloud VM misses the opportunity to use a managed database service that handles backups, patches, and scaling automatically — saving thousands of dollars in maintenance costs.

Create a Migration Strategy Matrix applying a specific "R" to each ABC Retail workload:

Workload	Migration Strategy	Timeline	Reason
Web Server	Rehost (Lift & Shift)	Month 1-2	Low risk, fast, highest priority
Database Server	Replatform → Managed DB	Month 2-3	Get managed backups & scaling
File Server	Replatform → Object Storage	Month 3	Unlimited storage, cheaper
Email System	Repurchase → Microsoft 365	Month 1	SaaS replaces maintenance burden
ERP System	Retain temporarily → Refactor later	Month 6+	High complexity, plan carefully
Backup System	Retire → Cloud Backup	Month 2	External HDDs are unreliable

Notice that the ERP system is marked as "Retain" initially. This is intentional — complex, business-critical applications should not be rushed into migration. Moving them last, after the team has gained cloud experience with simpler systems, dramatically reduces the risk of expensive failures.

TASK 6 Risk Assessment Matrix – Identify & Mitigate Risks

Every migration carries risks. A risk matrix identifies what could go wrong, how likely it is, how severe the impact would be, and what actions reduce that risk. Presenting a risk matrix to management demonstrates professional maturity.

Add a section: "Risk Assessment Matrix" to your document.

Create a risk matrix table with columns: Risk | Likelihood (Low/Med/High) | Impact (Low/Med/High) | Mitigation Strategy

Risk	Likelihood	Impact	Mitigation
Application downtime during migration	High	High	Migrate in off-peak hours; maintain parallel systems during cutover
Data loss during transfer	Low	Critical	Take full backups before migration; verify checksums; test restores
Staff cannot manage cloud resources	High	High	Begin cloud training 3 months before migration starts
Migration costs exceed budget	Medium	High	Phase the migration; validate costs after each phase before proceeding
Vendor lock-in	Medium	Medium	Use open standards; avoid proprietary services where possible
Security breach during transition	Low	Critical	Encrypt all data in transit; audit access; use MFA for all accounts

A risk matrix protects both the company and the consulting team. When you document risks upfront and propose mitigations, you are demonstrating that you have thought through the difficult scenarios. This also protects you professionally — if a risk occurs that you warned about, the company cannot blame you for failing to anticipate it.

TASK 7 Build the Migration Roadmap – Phased Timeline

A migration roadmap breaks the entire project into clear, manageable phases with timelines. It tells management what will happen, when it will happen, and what they should expect after each phase is complete.

Add a section: "Migration Roadmap" and create a phase-by-phase plan with an estimated timeline for ABC Retail.

ABC Retail Cloud Migration Roadmap: PHASE 0 – PREPARATION (Months 1–2) • Cloud team training (AWS/Azure fundamentals) • Set up cloud accounts (dev/test/prod) • Establish naming conventions and tagging standards • Procure and configure cloud infrastructure Milestone: Cloud environment ready for migration PHASE 1 – QUICK WINS (Month 2–3) • Migrate email to Microsoft 365 (SaaS) • Set up cloud backup service (retire external HDDs) • Migrate file server to object storage Milestone: Immediate cost savings + reliability improvement PHASE 2 – CORE INFRASTRUCTURE (Months 3–4) • Rehost web server to cloud virtual machine • Set up load balancer and auto-scaling • Configure monitoring and alerts Milestone: Website running on cloud, zero downtime achieved PHASE 3 – DATABASE MIGRATION (Months 4–5) • Replatform database to managed SQL service • Validate data integrity post-migration • Configure automated backups Milestone: Database modernized with managed service PHASE 4 – VALIDATION & OPTIMIZATION (Month 6) • Complete functional testing of all migrated systems • Optimize resource sizing and costs • Document final cloud architecture • Decommission remaining on-premises hardware Milestone: Full migration complete, on-prem retired PHASE 5 – ERP EVALUATION (Months 7+) • Evaluate SaaS ERP alternatives • Plan refactoring roadmap if custom solution needed Milestone: ERP strategy decided

Notice that the roadmap starts with "quick wins" — easy migrations that provide immediate visible benefits (cost savings, reliability). This strategy is important because it builds confidence in the migration project among management and employees. Migrations that begin with difficult, high-risk systems often fail because team morale drops when early problems occur.

Create a simple Gantt-style table showing which phase happens in which month (you can draw this as a table in Word/Sheets with filled cells representing active periods).

TASK 8 Compile the Final Migration Strategy Document

Now bring everything together into a single professional document. This document is what a real consulting team would deliver to a client before any technical work begins.

Open your main document and ensure it has the following sections in this order:

DOCUMENT STRUCTURE: 1. Cover Page - Project Title: "Cloud Migration Strategy – ABC Retail Pvt. Ltd." - Prepared by: [Your Name] - Date: [Today's Date] - Version: 1.0 2. Executive Summary (1 page) - Who is ABC Retail? - Why are they migrating? - What will the migration achieve? 3. Business Analysis - Current challenges - Business goals 4. Current Infrastructure Assessment - Infrastructure inventory table 5. Cloud Readiness Assessment - Readiness matrix with scores 6. Cloud Deployment & Service Model Recommendations - Why Hybrid Cloud - IaaS/PaaS/SaaS mapping 7. Migration Strategy Matrix (6 Rs) - Per-workload strategy 8. Risk Assessment Matrix - Risks, likelihood, impact, mitigation 9. Migration Roadmap - Phased timeline 10. Expected Benefits - Cost reduction estimates - Availability improvements - Operational improvements 11. Conclusion 12. Appendices (Infrastructure Inventory, etc.)

A professional document structure is essential because senior management rarely reads entire technical reports. The Executive Summary must contain the most important information so that a CEO can read only that section and understand the entire project. The detailed sections exist for the IT team and technical reviewers who need specifics.

Apply consistent formatting throughout the document: use Heading 1 for major sections, Heading 2 for sub-sections, and body text (11pt or 12pt) for all other content.

Add page numbers and a table of contents at the beginning of the document.

Save the document as both .docx and .pdf format. Professional documents are always delivered in PDF to prevent formatting changes.

✅ Professional Tip Use a consistent color theme throughout your document. Pick one accent color (like blue or teal) and use it for all headings, table headers, and callouts. This makes the document look designed rather than just typed.

3. Migration Planning Pipeline

Cloud migration follows a predictable lifecycle. Understanding this pipeline helps you plan each phase and know what outputs each phase should produce.

4. Complete Deliverable Assets & Templates

Use these templates as starting points for your project deliverables. Copy them into your documents and fill in the details specific to ABC Retail.

executive_summary_template.md — Project 1 Document Template

# CLOUD MIGRATION STRATEGY DOCUMENT # ABC Retail Pvt. Ltd. # Prepared by: [Your Name] | Version 1.0 | [Date] --- ## EXECUTIVE SUMMARY ABC Retail Pvt. Ltd. is a medium-sized retail company operating for over 10 years with a traditional on-premises IT infrastructure. As the company grows, maintaining physical servers has become increasingly expensive, unreliable, and difficult to scale. **Problem Statement:** The company's on-premises infrastructure cannot support its growth targets. Hardware failures cause downtime, procurement delays prevent rapid scaling, and the IT team spends most of its time on maintenance rather than business innovation. **Recommended Solution:** Migrate to a Hybrid Cloud architecture over 6 months using a phased approach. Begin with quick wins (email, backups, file storage) before tackling core systems. **Expected Outcomes:** - 30-40% reduction in monthly infrastructure costs - 99.9% uptime SLA for all production systems - Server provisioning time reduced from weeks to minutes - Disaster recovery time reduced from days to 4 hours --- ## INFRASTRUCTURE INVENTORY SUMMARY | System | Type | Strategy | Priority | Timeline | |-----------------|----------|-------------|----------|-----------| | Web Server | IaaS VM | Rehost | HIGH | Month 2 | | Database | PaaS DB | Replatform | HIGH | Month 3 | | File Server | PaaS | Replatform | MEDIUM | Month 3 | | Email | SaaS | Repurchase | LOW | Month 1 | | ERP | TBD | Retain→ | LOW | Month 7+ | | Backup | PaaS | Retire+New | HIGH | Month 2 | --- ## DEPLOYMENT MODEL Recommended: Hybrid Cloud Rationale: Migrate low-risk workloads first while retaining sensitive data on-premises during initial transition period. Target Providers: AWS (primary) or Azure — to be finalized in Phase 0 --- ## KEY RISKS 1. Downtime during cutover — MITIGATION: Off-peak migration windows 2. Staff skills gap — MITIGATION: Cloud training before migration 3. Budget overrun — MITIGATION: Phase-gated approvals 4. Data loss — MITIGATION: Full backups + integrity checks --- ## MIGRATION PHASES Phase 0: Preparation (Month 1-2) → Training, accounts, governance Phase 1: Quick Wins (Month 2-3) → Email, Backup, File Storage Phase 2: Core Infra (Month 3-4) → Web Server + Load Balancer Phase 3: Database (Month 4-5) → Managed SQL + Data Validation Phase 4: Validation (Month 6) → Testing + Optimize + Retire On-Prem Phase 5: ERP (Month 7+) → Evaluate + Plan

5. Deliverables Summary

📄 Documents to Create

Cloud Migration Strategy Document (PDF + DOCX)
Infrastructure Inventory Spreadsheet
Cloud Readiness Assessment Report
Migration Strategy Matrix (6 Rs)
Risk Assessment Matrix
Migration Roadmap (Phased Timeline)
Executive Presentation (10–15 slides in PowerPoint/Google Slides)
Project README file

✅ Verification Checklist

Business requirements clearly documented
All existing infrastructure assessed and inventoried
Cloud readiness scored across all 6 dimensions
Deployment model justified with reasoning
Each workload mapped to a 6R strategy
Risk matrix includes mitigation for each risk
Migration roadmap has specific timelines
Executive presentation uses business language (not jargon)
Document has table of contents and page numbers

6. Why We Did This & What It Accomplishes

Strategic Intent & Professional Impact

Why We Did This

Real cloud projects begin with business analysis, not server provisioning. Jumping straight to creating VMs without a plan leads to cost overruns and failed migrations.
The 6 Rs framework forces you to think critically about each workload rather than treating migration as a "copy-paste" exercise from on-premises to cloud.
A readiness assessment prevents companies from investing hundreds of thousands of dollars into migration only to discover their team lacks the skills to manage the new environment.
Risk matrices are legally and professionally important — they document that you identified potential problems and proposed solutions, protecting both the company and the consulting team.
Phased migration roadmaps reduce business risk by providing checkpoints where management can review progress and pause if problems arise.

What This Accomplishes

You now have a professional migration strategy document that demonstrates cloud consulting skills — the kind of document real cloud architects produce for enterprise clients.
The infrastructure inventory becomes the blueprint for all technical work in Projects 2–10. Every resource you deploy later should map back to something in this document.
The phased roadmap ensures that no future project decision is made in isolation — every step connects to the business objectives established here in Project 1.
Management (or your instructor) can review this document and understand exactly what will be built, why, at what cost, and with what risk mitigation — before a single dollar of cloud spending occurs.
This document becomes your portfolio piece demonstrating that you understand cloud not just as a technical discipline but as a business transformation tool.