Migrations to Azure¶

Field-tested migration playbooks from common on-prem and other-cloud platforms onto the CSA-in-a-Box Azure stack. Each playbook covers assessment → design → migration → cutover → decommission with realistic timelines and pitfalls.

Data, AI & Analytics migrations¶

Core CSA-aligned playbooks for cloud-scale analytics, data platforms, AI/ML, and the operational data stores that feed them.

Hyperscaler & cloud platforms (analytics workloads)¶

Data warehouses & lakehouses¶

Big data ecosystems¶

ETL & data integration¶

Business intelligence¶

Analytics & statistical computing¶

Operational databases (analytics sources)¶

Streaming & IoT¶

Enterprise modernization (beyond analytics)¶

These migrations are not part of the core analytics platform but often accompany cloud / data migrations at the enterprise level. Included so architects and customers can see the bigger picture when planning multi-year cloud transformations.

Compute & infrastructure¶

End-user computing¶

Enterprise applications¶

Identity & access¶

Productivity & collaboration¶

DevOps tooling¶

Security operations & observability¶

What every migration has in common¶

Regardless of source, every migration follows the same 5 phases:

flowchart LR
    A[1. Assessment<br/>2-4 weeks] --> B[2. Design<br/>2-3 weeks]
    B --> C[3. Migration<br/>4-16 weeks]
    C --> D[4. Cutover<br/>1-2 weeks]
    D --> E[5. Decommission<br/>4-8 weeks]

Sequencing rule¶

We always migrate consumers before producers, going upstream:

1. First: read-only consumers (BI dashboards, downstream APIs) — point them at a shadow Azure copy
2. Then: transformations (dbt / SQL / Spark)
3. Then: ingestion (the actual writes from source systems)
4. Finally: freeze the source and decommission

This minimizes the window where any single workload depends on both clouds simultaneously.

Cost during migration¶

Plan for ~140% of your steady-state Azure cost during the migration window because both source and target run in parallel. Tag every resource created during migration with purpose=migration-from-<source> so you can report on it separately.

See also Best Practices — Cost Optimization for tagging and reserved-capacity strategy.

Compliance during migration¶

Migration is the highest-risk window for data exposure. Read these before starting:

• Best Practices — Security & Compliance
• Compliance — your relevant framework
• Runbook — Security Incident

Specifically: never open a public IP on the source side to "make it easier to copy data over." Use ExpressRoute / VPN / Private Link.

Need a playbook for something not listed?¶

Open an issue at https://github.com/fgarofalo56/csa-inabox/issues with the source platform, approximate data volume, and target Azure services. We add playbooks based on demand.