Skip to content
CodeMorph

Teams

Migrate a shared codebase together.

Big migrations stall when they belong to nobody. CodeMorph gives the whole team one plan built from the real dependency graph, so batches can be split up, reviewed in your normal flow and verified before they merge.

Contact salesSee pricing
Leaf-first migration orderTwelve files in four batches. Batch 1 holds leaf modules in lib and utils, batch 2 the models that import them, batch 3 the API routes and middleware, and batch 4 the entry point. Each batch turns orange while it converts and green once verified.Batch 1 · leavesBatch 2Batch 3Batch 4 · entrylib/db.jslib/db.tslib/logger.jslib/logger.tslib/mailer.jslib/mailer.tsutils/money.jsutils/money.tsmodels/user.jsmodels/user.tsmodels/product.jsmodels/product.tsmodels/order.jsmodels/order.tsmiddleware/auth.jsmiddleware/auth.tsapi/users.jsapi/users.tsapi/cart.jsapi/cart.tsapi/orders.jsapi/orders.tsindex.jsindex.ts
JavaScript, not yet migrated Converting TypeScript, verifiedIllustrative project. Scan & Plan computes this order for your code today.

How teams migrate

One plan, many hands

Leaf-first order tells you exactly which work can happen in parallel and which has to wait.

  1. 01

    Scan once

    Build the dependency graph and the batch plan for the repository. Everyone works from the same order.
  2. 02

    Split the batches

    Files within a batch don't depend on each other, so a batch can be shared across developers without stepping on toes.
  3. 03

    Review in your flow

    Each developer accepts their diffs and verifies, then opens a pull request for the batch like any other change.
  4. 04

    Move up the graph

    When a batch merges, the next one is typed against it. The migration progresses without a freeze or a long-lived branch.

Roles

Who does what

A migration goes faster when everyone knows their part. A typical split:

RoleResponsibilities
Migration leadRuns Scan & Plan, sets the target strictness in tsconfig.json, decides the batch order and owns the definition of done.
DevelopersTake batches, give Morph instructions, accept or reject each diff, and run Verify before opening a pull request.
ReviewersReview each batch's pull request like any other change, with a focus on exported types that other modules depend on.
Platform or CI ownerAdds tsc --noEmit to CI so the project can never slip back, and tightens the check as strictness increases.

Playbook

A rollout that keeps shipping

Migrations fail when they freeze feature work. This sequence avoids that. Adapt the pace to your codebase.

  1. 01

    Prepare

    day one
    Add typescript and a permissive tsconfig.json with allowJs. Make sure tests and build pass on main. Record the baseline error count.
  2. 02

    Plan together

    Run Scan & Plan and walk through it as a team. Large cycles or huge first batches are worth discussing before anyone converts a file.
  3. 03

    Foundations first

    Migrate the leaf batches (utilities, helpers, data access) and merge them quickly. Everything after this gets better types for free.
  4. 04

    Fan out

    Split the middle batches across developers. Files within a batch don't import each other, so parallel work rarely conflicts.
  5. 05

    Guard the progress

    Add tsc --noEmit to CI as soon as the first batches merge, so new JavaScript or type errors can't creep back in.
  6. 06

    Finish and tighten

    Migrate entry points and config last, set allowJs to false, then raise strictness one flag at a time.

Working with CI

Keep the migration honest

Run & Verify proves each batch on a developer's machine. Your CI should prove it again on every pull request. Add the same three checks CodeMorph runs:

CI checks
# in your CI workflow
npm ci
npx tsc --noEmit
npm test
npm run build

Because CodeMorph verifies with your own scripts, a batch that passes locally passes in CI too.

The Teams plan

What's included

$40 per seat per month at launch. Free while CodeMorph is in beta.

Planned

Shared migration plans

One plan per repository, with batch ownership and progress everyone can see.

PR-ready batches

Verified batches land as branches ready for your normal review process.

Org model policy

Choose the allowed providers and models for everyone, including your own Anthropic account.

Everything in Pro

Batch migration, review, Run & Verify and the Morph agent for every seat.

Centralized billing

One invoice for the team, with seats you can add or remove.

Onboarding call

We'll walk through your first plan with you and help split the work.

Today every developer can use the full workflow for free in the beta; the team features above are in progress.

FAQ

Questions from team leads

Can we start before the Teams plan launches?
Yes. Everyone on the team can download the beta and migrate today, each working from the same plan order. Get in touch and we'll help you set it up.
Does our code leave our machines?
No. Scanning, review and verification run locally. Conversion and Ask call the model provider you configure, under your own account.
How do we avoid merge conflicts?
Files in the same batch don't import each other, so parallel work within a batch rarely collides. Merging batch by batch keeps branches short-lived.
Do you offer volume pricing?
Yes, for larger teams. See Enterprise or contact sales.
Can different developers use different models?
Today each developer chooses their own model and key. With the Teams plan, an admin will be able to set the allowed providers and models for everyone.
What if two developers need the same file?
Files in the same batch don't depend on each other, so assign each file to one person. If someone is editing a file for feature work, migrate it in a later pass.
How do we track progress?
The status bar shows typed files out of total, and each batch shows its progress. Merged batch pull requests are a simple team-wide measure.
Can we migrate while still shipping features?
Yes, and you should. Merge batch by batch, keep branches short-lived, and let CI's typecheck protect what's been migrated.

Get started with CodeMorph for Teams.

Download the beta, open a project and see your migration plan in under a minute.

Contact salesRead the docs