Skip to main content
Morph structures the modernization process as a series of well-defined stages, guiding teams from initial project conception all the way to delivering production-ready pull requests. This page explains the key terms used throughout each phase of that journey.

​
Table of Contents

​
tl;dr

Morph turns your migration into a step-by-step pipeline:
  1. Create a Project (pick your repo(s))
  2. Define your Project Spec (what should change & how)
  3. Review before/after Architectures
  4. Break the project into Milestones
  5. Execute a full Milestone. During execution, Morph dynamically generates Tasks so progress is transparent and each deliverable is verifiable.
  6. Once milestone tasks are completed and verified, Morph produces a production-ready PR for that milestone.
  7. While Morph does the heavy lifting, grab a coffee (or touch grass) and come back for review.
Each concept builds on the previous one, so decisions stay traceable from high-level goals down to individual code changes.

​
Core Concepts

​
Project

A Project is the top-level container for a modernization effort. It defines:
  • What repository/repositories are in scope
  • Which branch strategy to use for generated code
  • The operational boundary for specs, architectures and milestones
In practice, a project is where Morph keeps the full migration context from initial setup to final PR delivery.
Create Project modal

Morph Project creation

Some common use cases:
  • Modernizing a legacy Flask-based application to FastAPI
  • Rewrite C++ CLI using Rust
  • Java application version upgrade

​
Project Specification

A Project Specification is the source-of-truth document for what “done” means. It captures migration requirements before major implementation begins. Typical contents include:
  • Target stack
  • High-level migration plan
  • Key design dcisions
  • Environment setup
  • Testing startegy
Project spec modal

Project specification creation

​
Architectures

Architectures describe system structure at two points in time:
  • Source Architecture: how the current system works today
  • Destination Architecture: how the migrated system should be organized
Architectures reduce ambiguity by making module boundaries, dependencies, and integration points explicit.

​
Milestone

A Milestone is a coherent, reviewable chunk of migration work. Milestones sequence the project into manageable steps with explicit scope, risks, and dependencies.
  • Functionally meaningful (not arbitrary file splits)
  • Small enough to review safely
  • Ordered so each one unlocks the next

​
Task

A Task is the smallest executable unit inside a milestone. Tasks translate milestone intent into specific implementation actions. Tasks usually map to one of:
  • File/module creation or migration
  • Endpoint or data-model implementation
  • Test implementation
  • Refactor/fix work

​
Visual Diagrams

​
Concept Relationship Diagram

​
Glossary

TermDefinition
ProjectTop-level modernization container for repos, branch strategy, and all migration artifacts.
Project SpecificationStructured requirements and design intent document defining what the migration must produce.
Source ArchitectureModel of the current system’s components, flows, and dependencies before migration.
Destination ArchitecturePlanned target structure after migration, including modules and integration boundaries.
MilestoneOrdered, reviewable chunk of migration work with explicit scope and dependencies.
TaskSmallest actionable implementation unit within a milestone.
RoadmapThe main screen in the Morph Platform listing the project’s milestones, with other project entities available via sidebar