Skip to main content
Learn how ArcKit accelerates cloud migration planning by generating comprehensive architecture documentation, risk assessments, and transition roadmaps.

​
When to Use This Approach

Use ArcKit for cloud migration projects when you need to:
  • Document existing on-premises architecture before migration
  • Design target cloud architecture with compliance controls
  • Create transition plans with minimal disruption
  • Assess risks and dependencies across workloads
  • Generate stakeholder-ready migration documentation

​
Relevant Commands

# Initialise migration project
arckit init --type migration

# Document current state architecture
arckit.design --mode as-is

# Design target cloud architecture
arckit.design --mode to-be

# Generate migration risk assessment
arckit.risks --focus migration

# Create transition roadmap
arckit.roadmap

# Compliance mapping for cloud
arckit.compliance --cloud azure-gov

​
Example Walkthrough: M365 GCC-H Migration

Reference project: arckit-test-project-v1-m365 This example demonstrates migrating UK government users from on-premises Exchange and SharePoint to Microsoft 365 GCC-High cloud environment.

​
Step 1: Document Current State

ArcKit captured the existing email and collaboration infrastructure, including Active Directory integration, file shares, and compliance controls.

​
Step 2: Design Target Architecture

Generated comprehensive documentation for M365 GCC-H including:
  • Identity federation (Azure AD Connect)
  • Compliance boundary configurations
  • Data residency controls (UK region)
  • Security baselines and conditional access

​
Step 3: Risk and Dependency Analysis

ArcKit identified critical risks:
  • User authentication disruption during cutover
  • Data loss during mailbox migration
  • Third-party integrations requiring reconfiguration
  • Compliance gaps during transition period

​
Step 4: Transition Planning

Produced phased migration roadmap with:
  • Pilot group selection criteria
  • Migration wave scheduling
  • Rollback procedures
  • Communication and training plans

​
Key Artifacts Generated

Architecture Views

Current state, target state, and transition architecture diagrams

Risk Register

Migration-specific risks with mitigation strategies

Compliance Mapping

Controls maintained throughout migration

Transition Roadmap

Phased approach with milestones and dependencies

​
Best Practices

Use arckit.design --mode as-is to capture existing architecture first. This baseline ensures nothing is lost during migration and helps identify technical debt.
Run arckit.compliance for both current and target states. Migration must maintain regulatory controls continuously - gaps are unacceptable.
Let arckit.risks inform your migration waves. High-risk workloads may need pilot testing; low-risk systems can move faster.
ArcKit’s generated diagrams and roadmaps are stakeholder-ready. Use them in governance boards, steering committees, and user communications.

M365 GCC-H Migration

Government cloud migration example

National Highways Data

Data platform modernisation

Security & Compliance

Maintaining compliance during transitions

Build docs developers (and LLMs) love

Get started for freeTalk to us