Track Your Code Migration Progress

Migrating from JavaScript to TypeScript? Java to Kotlin? See exactly how far you've come and how fast you're moving.

The Problem

Your team is migrating a codebase to a new language or framework. Stakeholders want to know: How much is done? How much is left? Are we on track? Without tooling, you're left counting files manually or making rough estimates.

The Workflow

First: Prepare Your Repository

Before setting up migration categories, we recommend completing the initial repository preparation — exclude irrelevant files, handle suspicious commits, and merge developer identities.

Follow the Getting Started guide →

1 Create Code Categories

Open the Settings tab in Git Insight. Create two categories for the old and new stacks. For a JavaScript to TypeScript migration:

  • TypeScript: patterns *.ts, *.tsx
  • JavaScript: patterns *.js, *.jsx

For Java to Kotlin:

  • Kotlin: patterns *.kt, *.kts
  • Java: patterns *.java

Categories use glob pattern syntax (same as .gitignore). You can add as many patterns per category as needed.

2 See Current State

Open the Project Statistics tab. You'll see a breakdown of every file extension in the project — total files, lines, and tokens per extension. The pie chart gives you an instant visual of the current ratio between old and new stacks.

Example: if you see 45,000 lines of TypeScript and 15,000 lines of JavaScript, you're 75% through the migration (by line count).

3 Track Migration Velocity

Switch to the Developer Statistics tab. Use the category filter checkboxes to view only your migration categories. The contribution chart shows how many lines of each category are being added or removed over time.

Set the date range to the last 3-6 months and group by month. You should see:

  • New stack lines increasing (TypeScript/Kotlin being added)
  • Old stack lines decreasing (JavaScript/Java being removed)

If both are increasing, developers might be writing new code in the old language — time to revisit migration guidelines.

4 See Who's Contributing

The Developer Statistics table shows each developer's added and deleted lines — filtered by your category. This helps you understand who's actively working on migration tasks and who might need support or motivation.

5 Drill Into Details

Double-click any developer to see their commits. Switch to the Changes tab to see which directories still have old-stack files. This helps prioritize: "We still have 50 JavaScript files in src/components/legacy — let's focus there next sprint."

Migration Types This Works For

  • JavaScript → TypeScript (*.js, *.jsx → *.ts, *.tsx)
  • Java → Kotlin (*.java → *.kt, *.kts)
  • CSS → SCSS/SASS (*.css → *.scss, *.sass)
  • CommonJS → ESM (track by file extension or directory patterns)
  • Any extension-based migration — the category system is flexible enough for any pattern

Start Tracking Your Migration

Install the free trial, create your categories, and see your migration progress in minutes.

Install Free Trial