Skip to main content
After you approve your instructions, generates a Destination Architecture—the design document for what your migrated application will look like.

​
Why Destination Architecture Exists

You’ve defined where you’re coming from (Source Architecture) and what you want (Instructions). The Destination Architecture completes the picture by defining where you’re going. This document describes:
  • How the migrated application will be structured
  • What the new technology stack looks like
  • How components will be organized
  • Migration patterns for transforming source to destination

​
How It’s Generated

Destination Architecture is created by combining:
  1. Source Architecture — Understanding of your current codebase
  2. Approved Instructions — Your defined target and requirements
analyzes both and designs a destination that:
  • Achieves your modernization goals
  • Respects the structure of your source application
  • Follows best practices for the target stack

​
What It Contains

​
Target Technology Stack

  • Languages and versions
  • Frameworks and libraries
  • Build and tooling configuration

​
Application Structure

  • New module organization
  • Component hierarchy
  • Directory layout

​
Migration Mappings

  • How source patterns translate to destination patterns
  • Which source modules map to which destination modules
  • Transformation approaches for key components

​
Integration Points

  • How external dependencies are handled
  • API contract preservation (if required)
  • Configuration migration approach

​
Viewing Destination Architecture

After instructions are approved:
  1. Click Destination Architecture in the left sidebar
  2. Review the generated design
  3. Understand how your migrated application will be organized
Destination Architecture is read-only. It’s generated based on your approved instructions. If the design doesn’t match your expectations, consider whether your instructions fully captured your requirements.

​
From Architecture to Roadmap

Once Destination Architecture is complete, you’re ready to generate the Roadmap—the sequence of milestones that will execute your migration.
  1. Open Destination Architecture
  2. Click Generate Roadmap
  3. Wait for milestone planning to complete
The roadmap breaks your migration into logical chunks, ordered so each milestone builds on the previous one.

​
If Generation Fails

Destination Architecture generation can fail due to:
  • Complex or unusual source structures
  • Conflicting requirements in instructions
  • Technical limitations of the target stack
If generation fails:
  1. Review the error message
  2. Click Try Again
  3. If failures persist, contact support

​
Next Steps

With Destination Architecture ready, proceed to Working with Milestones to understand how the actual migration executes.