Legacy Code Modernization Tracking

😰

The Modernization Question

Leadership asks: "How much of the legacy code is migrated?"

You say: "We think... maybe 60%?"

Migration Phases with Buoy

📊

Baseline

Scan your legacy codebase to understand the current state. How many hardcoded values? How many duplicate components?

📈

Track

As you migrate, track progress with real metrics. See adoption grow week over week, sprint over sprint.

🛡️

Enforce

Once migrated, enforce the new patterns. Block PRs that introduce new legacy patterns.

📋

Report

Show leadership exactly how much is done, what's left, and the trend. No more "we think 60%".

Track Progress with Real Data

buoy-cli

Migration Progress

═══════════════════════════════════════

Legacy Code: 38% ███████░░░░░░░░░░░

In Progress: 15% ███░░░░░░░░░░░░░░░

Migrated: 47% █████████░░░░░░░░░

This sprint: +8% migrated

Velocity: ~12% per sprint

ETA: 3 more sprints to 100%

Configuration for Migrations

buoy.config.mjs

export default {
  // Define what "legacy" means
  legacy: {
    // Legacy directories to track
    directories: ['src/legacy/', 'src/old-components/'],

    // Legacy patterns to detect
    patterns: [
      'className="legacy-*"',
      'import.*from.*@old-design-system',
    ],

    // Mark files with this comment as legacy
    markers: ['@legacy', '@deprecated'],
  },

  // Modern design system reference
  tokens: './src/tokens',

  // Track migration progress
  migration: {
    enabled: true,
    trackBy: 'directory', // or 'file' or 'component'
  },
}

What You Get

📊

Exact Numbers

Not "we think 60%" but "47.3% migrated, up 8% from last sprint"

📈

Velocity Tracking

Know your migration velocity and estimate completion dates

🛡️

Prevent Regression

Block PRs that add new legacy code to migrated areas

Modernization Tracking