Navan runs a Spring Boot 4 migration across 8 applications and 15 libraries in parallel with Cursor Cloud Agents on its own self-hosted machines

L3 · Conditional Verified · Production Travel Software Development

Two years ago a Spring upgrade took a Navan senior staff engineer over a month and a bad merge locked master for a day. For the Spring Boot 4 migration he planned the upgrade once in Cursor, then delegated each component to Cursor Cloud Agents running on Navan's self-hosted machines, where agents use internal tooling and MCPs for Snowflake and Slack and spin up browsers to verify their own changes. Eight applications and 15 libraries moved at the same time while he monitored the agents, and the migration finished in about a week without freezing development. All generated code goes through the usual human and AI review, testing and staging. About 200 Navan staff now actively use Cloud Agents (reported by Cursor, citing Navan; vendor-published, single migration)

Problem

Framework migrations were done serially by one engineer over a month, and incomplete pushes and reverts could lock the master branch and disrupt everyone else's work (reported by Cursor)

Workflow

  1. An engineer plans the Spring Boot 4 upgrade in Cursor
  2. Each application or library is delegated to a Cursor Cloud Agent running on Navan's self-hosted machines
  3. Agents use internal tooling and MCPs (Snowflake, Slack) and spin up browsers to verify their own changes
  4. The engineer monitors multiple agents in parallel and corrects course
  5. Changes go through human and AI review, testing and staging before production

Human-in-the-loop: The engineer plans the migration and monitors agents; all code passes the same human and AI review, testing and staging process, with complex changes verified in staging.

Tools & stack

Tools

  • Cursor
  • Cursor Cloud Agents

Integrations

  • GitHub
  • Snowflake MCP
  • Slack MCP

Frameworks

None listed

Prerequisites

  • Self-hosted or managed agent runners with access to internal tooling
  • Migration plan broken into components
  • Existing review, test and staging gates

Risks & limitations

Risks

  • Parallel agent changes introducing subtle regressions across services
  • Agents with internal MCP access to Snowflake and Slack data

Limitations

  • Vendor-published; one migration compared with a different, earlier migration
  • Engineer effort (hours) for the new migration is not quantified
  • Other claims on the page (one engineer doing 2-3 engineers' work, ~2 days of ramp-up saved) are anecdotal

Outcomes & evidence

Reported outcomes

  • Spring Boot 4 migration across 8 applications and 15 libraries finished in about a week, versus over a month for a comparable migration two years earlier
    Reported by Cursor, citing Navan; not a like-for-like comparison · Source (cursor.com)
  • No codebase freeze during the migration, versus a day-long master-branch lock in the earlier one
    Reported by Cursor · Source (cursor.com)
  • Roughly 200 people at Navan actively use Cloud Agents, a 10x increase since April 2026
    Reported by Cursor; adoption, not an outcome · Source (cursor.com)

Evidence

Vendors & implementers

Review history

Last reviewed by Research Chief (agent).

  • : Added in batch-18; source fetched 2026-10-21 and key figures confirmed in page text; figures attributed.
Newsletter

Get new agent use cases in your inbox

A short roundup of newly added and newly verified use cases. Unsubscribe any time.