> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolte.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Modernize a legacy codebase in reviewable checkpoints

> Break a large migration into small units you can review, verify and roll back one at a time.

A multi-week migration is not one task. Split it into reviewable units. Each unit produces a concrete result a person checks before the next one starts. This keeps plans reviewable, limits risk and gives the next task verified context.

**1. Inventory the current implementation**

Explore the codebase, trace behavior and list the modules a migration would touch. Start in Interactive Chat and narrow the scope with follow-up questions. See [Interactive Chat vs autonomous workflow vs CLI](https://docs.revolte.ai/get-started/when-to-use-revolte.md).

**2. Split the work into checkpoints**

Make each unit one outcome with a clear boundary, relevant context, acceptance criteria and a way to verify it. See [Interactive Chat vs autonomous workflow vs CLI](https://docs.revolte.ai/get-started/when-to-use-revolte.md).

**3. Migrate one bounded path**

Refactor or update one path while preserving existing behavior and your conventions. See [Work with existing code](https://docs.revolte.ai/workflows/work-with-existing-code.md).

**4. Add or update verification**

Generate tests for the path you changed and run them in your pipeline. See [Generate tests for existing code](https://docs.revolte.ai/use-cases/generate-tests.md) and [Test Suite pipeline stage](https://docs.revolte.ai/yaml/repo-preferences/pipelines/test-suite.md).

**5. Review before the next unit**

A person inspects the plan and the code changes before the next checkpoint begins. See [Review the execution plan](https://docs.revolte.ai/workflows/review-execution-plan.md) and [Review code changes](https://docs.revolte.ai/workflows/review-ai-changes.md).

**6. Repeat**

Each checkpoint can become its own Jira task and workflow run. See [Set up an autonomous workflow with Jira](https://docs.revolte.ai/workflows/autonomous-workflow-setup.md).

## Plan for recovery

Releases can be rolled back by restoring a known good deployment. See [Rollback strategy](https://docs.revolte.ai/deployments/rollbacks.md).

## Check the limits first

Before you plan monorepo or database migration work, read [Known limitations](https://docs.revolte.ai/reference/known-limitations.md).

## Next

> [card] [Add and maintain test coverage](https://docs.revolte.ai/use-cases/engineering/test-coverage.md)

> [card] [Keep production reliable](https://docs.revolte.ai/use-cases/devops/production-reliability.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.