Migration Campaigns are designed for enterprise engineering teams. To start a new migration campaign, simply contact us and we’ll add a demo of the requested migration to your dashboard. See i18n migrations for real-world examples of enterprise campaigns.
Before you start: plan with Insights
Use Codemod Insights dashboards to measure how widespread a pattern is, estimate effort, and decide which repositories to include in your campaign. Once priorities are clear, spin up a new Migration Campaign and execute with confidence.Not sure where to begin? We’ll help you surface high-impact, low-effort migrations you can tackle right away.
Running a Migration Campaign
- Visual parameter configuration - Edit workflow parameters through the UI instead of YAML
- Centralized state management - Coordinate migrations with persistent state across repos and teams
- Multi-repo orchestration - Run workflows across your entire codebase with progress tracking
- Business insights - Track migration progress with custom metrics and dashboards
Make sure the Codemod GitHub App is installed on repositories you plan to migrate.
1
Open Migration Campaigns
In the Codemod app, navigate to Campaigns -> Create Workflow.
The Campaigns section is visible only on pro tier or above or upon request.
2
Create campaign
Give your campaign a descriptive name and pick the repositories you wish to target.
3
Define workflow
Compose one or more steps—codemods, scripts, or manual approvals—into a repeatable workflow that Codemod will run for every affected repo.
4
Run & track
Start the campaign and watch progress roll in. Codemod opens pull-requests, tracks status, and surfaces metrics so you always know what’s left.