Skip to main content
Before migrating your code, generates a Source Architecture document—a comprehensive wiki describing your current codebase.

​
Why Source Architecture Matters

You’re migrating from a source repository to a destination repository. To do this correctly, needs to understand what the source actually is:
  • What technologies and frameworks are in use?
  • How is the application structured?
  • What are the core components and how do they connect?
  • What patterns and conventions does the code follow?
Without this understanding, migration would be guesswork. With it, can make intelligent decisions about how to transform your code.

​
What Gets Documented

The Source Architecture captures:

​
Technology Stack

  • Programming languages and their versions
  • Frameworks and libraries in use
  • Build tools and configuration

​
Application Structure

  • Module and package organization
  • Entry points and main flows
  • Key directories and their purposes

​
Architectural Patterns

  • Design patterns in use (MVC, repository, etc.)
  • Data flow and state management
  • API structure and endpoints

​
Dependencies

  • External service integrations
  • Database connections
  • Third-party API usage

​
How It’s Used

The Source Architecture serves multiple purposes throughout your migration:

​
Informing Instructions

When generates your migration instructions, it uses the Source Architecture to understand what needs to change. This ensures the instructions are grounded in reality, not assumptions.

​
Designing Destination Architecture

The destination design is based on the source. You can’t plan where you’re going if you don’t know where you are.

​
Guiding Milestone Creation

Milestones are planned with knowledge of your codebase structure. Related files are grouped together, dependencies are respected, and the migration order makes sense.

​
Providing Context to AI

Every code generation task has access to the Source Architecture. This context helps produce code that respects your application’s patterns and conventions.

​
Viewing Source Architecture

  1. In your project, click Source Architecture in the left sidebar
  2. The document opens showing the analysis of your codebase
  3. Review to confirm it accurately describes your repository
The Source Architecture is read-only. It’s generated based on your actual code, so if something looks wrong, it may indicate an issue with the source repository structure.

​
When Source Architecture Generates

Source Architecture generation begins automatically when you:
  1. Create a new project, or
  2. Submit your modernization goals
The process typically takes a few minutes, depending on repository size. You can navigate away—generation continues in the background.

​
If Generation Fails

If Source Architecture generation fails:
  1. Click Source Architecture to see the error
  2. Click Try Again to retry
  3. If failures persist, contact support with your project details
Common causes:
  • Repository access issues
  • Unusual project structures
  • Very large repositories (may need more time)

​
Next Steps

Once Source Architecture is complete, generates your migration Instructions. See Modernization Instructions to learn about reviewing and approving them.