✓ ShippedByAgents
Practitioner (own blog/paper) Migration

Forter migrates about 90% of 500 repos from Jenkins to GitHub Actions in under three months with a local Claude Code migration agent

Forter needed to move 500 repositories from a custom Jenkins setup to GitHub Actions reusable workflows, which it estimated at 3.4 engineering years. A first attempt that handed GitHub Issues to Copilot's cloud agent fell short because the agent lacked cross-repo context. The team moved to a local Claude Code skill that analyses each repo in four phases, proposes changes for review, then makes a shallow clone, applies the changes and pushes a PR once a developer approves. Complex, sensitive repos were migrated by hand alongside it.

The numbers (as reported)

Repos migratedAbout 91% of 500, including 100% of non-custom repos
Calendar timeJust under three months, against an estimate of about a year
EffortAbout 10 weeks, never more than 3 engineers at a time
Original estimate3.4 engineering years
Claimed speed-up13x

Facts

Company / subject
Forter
Tools
Claude Code, GitHub Copilot
Codebase
brownfield
Work type
Migration
Stack
Jenkins, GitHub Actions
Published
2026-06-16
Last checked
2026-11-02

What the source claims Practitioner (own blog/paper)

Claimed by the builder, writing about their own work. Not checked independently.

  • About 91% of 500 repos moved to GitHub Actions in just under three months, against an estimate of roughly a year ~3 months vs ~1 year
    “we managed to fully migrate ~91% of all repositories, including 100% of our goal repos, in just under three months”
  • Forter says its framework sped up the migration 13 times over the 3.4 engineering-year estimate 13x
    “sped up a full-scale CI migration 13 times over”

Caveats

Company writing about its own work. Part 1 of a 3-part series; the three-month clock starts once the workflow was stable, not from the first attempt.

More stories by tool: Claude CodeGitHub Copilot

Related topics: MigrationsBrownfield codebases

Source

Forter Tech Blog (Dor Almog)

One email a week: what actually shipped

New sourced stories, the numbers behind them, and what didn't work. No hype.

We'll only use this to send the newsletter. See the privacy page.