Live
Corporate platform on Next.js · Engineering and infrastructure
- Next.js
- Corporate platform
- Engineering
Any industry · Software delivery
Legacy modernisation and code migration
Migrate old PHP, Java or .NET applications service by service with Claude Code: characterisation tests first, then codemods and a pull request per service behind CI gates.
- ClaudeAnthropic
- Typical timeline: Pilot in 2–4 weeks
The problem
Old PHP, Java or .NET applications and unmaintained frameworks block new features, and a full rewrite is risky and slow.
- Every new feature fights the old codebase.
- Nobody wants to own the big rewrite.
- Big-bang migrations stall halfway.
How we solve it
Claude Code maps the system, writes characterisation tests and codemods, and opens a pull request per service, with parallel sub-agents, CI gates and staged rollout, so the system moves forward one safe step at a time.
It plugs into GitHub or GitLab, Your CI, Jira or Linear and AWS, Google Cloud or Azure, so nothing you rely on today is replaced. The architecture below shows each step and which model does the work.
Architecture
From your stack, through the AI layer, to numbers you can track
Each step names the model or system doing the work. Writes to your systems wait for a person to approve them.
Your stack
- GitHub or GitLab
- Your CI
- Jira or Linear
- AWS, Google Cloud or Azure
AI layer
Softpiper AI layer
- Claude
- Map the system, using Claude Code
Modules, dependencies, risky areas and test gaps are mapped.
- Characterisation tests, using Claude Code
Current behaviour is captured in tests before anything changes.
- Plan per service, using Claude Opus
A migration plan sequences services by risk and value.
- Migrate, using Sub-agents · Routines
Codemods and a pull request per service, with sub-agents working in parallel.
- Gate, using Your CI
CI runs the full suite on every pull request; engineers review before merge.
- Roll out, using AWS · Google Cloud · Azure
Feature flags and a staged rollout to your target cloud.
Outcomes you measure
- Services migrated per sprint
- Test coverage
- Regression incidents
- Build and deploy times
Why this model
Why Claude
We choose per task on capability, cost and where your data must stay. Final versions are picked at kickoff.
ClaudeAnthropic
Anthropic positions Claude Opus for long-running agentic coding: it plans migrations, writes codemods and works through parallel sub-agents, while Routines or Managed Agents run overnight batches.
Standardised on Google? For Google Cloud targets, Google's application-modernisation tooling can complement the migration.
Delivery
What you get, how long it takes, and how we keep it safe
Guardrails
- Characterisation tests before any change.
- Feature flags and staged rollout.
- Engineers review and approve every merge.
- A rollback plan for every service.
Plus the guardrails on every build: facts from your systems, approvals for writes and money, a human one step away, audit logs and evals. See all
Deliverables
- Codebase map and migration plan
- Characterisation test suite
- Migrated pilot service
- Migration playbook for the remaining services
- CI and rollout configuration
Typical timeline
- Discovery and pilot service2–4 weeks
- Phased rolloutPlanned per service
A planning range for a first production release. We confirm scope, price and dates in a tailored proposal.
KPIs to track
- Services migrated per sprint
- Test coverage
- Regression incidents
- Build and deploy times
- Engineering hours per migrated service
Goals we agree with you and measure from a baseline. They are what we track, not results we promise.
Related services
The services behind this playbook
Management and support
We run what we launch: keep it working, keep improving it, and modernise it without a risky big-bang rewrite.
View serviceCloud and DevOps
Secure, observable infrastructure on Google Cloud and Vercel, with deployments that are boring in the best way.
View serviceWeb apps
Fast, accessible web products, from MVP to platform, engineered to last.
View service
Our work in this space
What we've built for growing businesses
Sites and products we've shipped for businesses in this sector. They show how we work; they are not deployments of this playbook.
More playbooks
Related playbooks
Any industry
“Talk to your data” analyst
Business users wait days for an analyst to pull simple numbers, and dashboards can't answer the follow-up question.
- Claude
- Gemini
- Typical timeline
- 3–6 weeks
- Plugs into
- Postgres / Supabase · BigQuery · Snowflake +1 more
Startups
MVP acceleration and AI-native dev workflow
Founders need to ship a credible product fast with a tiny team, then keep shipping without building a large engineering department.
- Claude
- Gemini
- Typical timeline
- 4–10 weeks
- Plugs into
- GitHub or GitLab · Supabase / Postgres · Vercel or Cloudflare +2 more
Retail and e-commerce
AI shopping concierge for web and WhatsApp
Shoppers leave when they can't get a fast answer on sizing, stock, delivery or returns, and your team answers the same questions across chat, email and WhatsApp.
- Claude
- Gemini
- Typical timeline
- 3–10 weeks
- Plugs into
- Shopify · WhatsApp Business · HubSpot or Zoho CRM +1 more
Pip · Softpiper's AI
Ask Pip about this playbook
Ask Pip how this would work for you
Pip is Softpiper's AI. Tell it what you run today and it will walk through how this playbook fits, what we would build first and a tailored price range. Or book a call with the team.