Is this for you?
- Vue 2 is EOL and you've been putting off the migration.
- You're moving between React and Vue and want a clean plan.
- You have a JS codebase that keeps shipping bugs TypeScript would catch.
- Core Web Vitals are slipping and organic traffic is taking a hit.
- The team keeps starting a migration and abandoning it.
- You want measurable improvements, not vague performance advice.
Vue 2 → Vue 3 Migration Roadmap
A migration plan that tells you what to do first, what to do last, and what to throw away.
What you get
- Full codebase assessment with component inventory and complexity scoring.
- Incremental-vs-rewrite recommendation with reasoning.
- Phase-by-phase plan with effort estimates per phase.
- Options API → Composition API migration guidance.
- Third-party dependency review — what migrates, what needs replacing, what can stay.
- Prioritized remediation roadmap.
- 60-minute walkthrough.
Good fit: Vue 2 is EOL, the team keeps starting the migration and abandoning it, or third-party dependencies are mixed and compatibility is unclear. Includes Vuex → Pinia migration guidance. Nuxt migration is flagged but scoped separately.
React ↔ Vue Migration
Migration guidance for teams moving between React and Vue, in either direction.
What you get
- Pattern-by-pattern translation guide (hooks ↔ composables, context ↔ provide/inject).
- Component migration priority list.
- State management translation (Redux/Zustand ↔ Pinia/Vuex).
- Routing translation (React Router ↔ Vue Router).
- Phased rollout plan with effort estimates.
- 60-minute walkthrough.
Good fit: framework choice is made, you want a clean plan, state-management and routing mapping are concerns. The plan accounts for running both frameworks in parallel during the migration without being stuck there permanently.
TypeScript Adoption Plan
Incremental TypeScript migration that doesn't require pausing feature work.
What you get
- Codebase assessment with module complexity scoring.
- Phased migration plan (config → leaf modules → shared libraries → API layer).
- `tsconfig` recommendations with strictness ramp by phase.
- Tooling setup (build, lint, editor, CI).
- Effort estimates per phase.
Good fit: JS codebase shipping bugs TypeScript would catch, tooling choice paralysis (tsc/swc/esbuild/Vite-only), or a prior migration attempt that stalled. Vue-specific tooling (Volar, vue-tsc) is included when relevant; same for React + bundler specifics.
Frontend Performance Optimization
Make your frontend feel fast: load time, interaction speed, and Core Web Vitals.
What you get
- Core Web Vitals and lab test audit with baseline measurements.
- Bundle and dependency analysis with concrete reduction targets.
- Render and runtime profiling for the slowest user journeys.
- Image, font, and asset optimization recommendations.
- Caching and delivery strategy review (CDN, headers, critical assets).
- Prioritized optimization roadmap with impact estimates.
- 60-minute walkthrough.
Good fit: Core Web Vitals slipping, users complaining the app feels slow, bundles large and unclear what to cut. Covers mobile breakpoints and real-device behavior.
Scope
What's in
- Vue 2 → Vue 3 migration strategy (Composition API, Pinia/Vuex, dependency review)
- React ↔ Vue migration strategy (pattern translation, state, routing)
- Incremental TypeScript adoption plan (tsconfig ramp, tooling, CI)
- Frontend performance optimization (Core Web Vitals, bundles, runtime)
What's out
- Performing the migration or optimization (separate engagement)
- Full redesign or design-system overhauls
- Backend API changes and backend performance (see Laravel Modernization Audit)
- SSR framework choice beyond scoping (Nuxt, Next.js — flagged, not scoped)
Process
Intake
Day 1Kickoff, repo access, tooling inventory, intro to the team.
Discovery
Days 2–5Codebase read, component or module inventory, dependency graph, baseline measurements as applicable.
Analysis
Days 6–9Incremental-vs-rewrite modeling, phase design, effort estimation. For performance: optimization design with impact estimates.
Report
Days 10–12Draft, review, finalize.
Walkthrough
Day 1460-minute call with your team.
Pricing
50% to start, 50% on report delivery. Includes one 30-minute follow-up call within 30 days of delivery.
One fixed price. No surprises, no “starting at” language. If we agree on scope and you pay the deposit, the engagement is locked in.
Questions
Which scope should I pick?
Pick by the starting point: Vue 2 codebase targeting Vue 3, React codebase targeting Vue (or vice versa), JS codebase adopting TypeScript, or any codebase whose performance is slipping. The scope options below spell out the fit for each.
Can you do the migration for us?
Separately, yes. Every scope is the roadmap; implementation is a distinct scope.
Can I take more than one scope?
Yes — some teams pair TypeScript adoption with a Vue 2→3 migration, or frontend performance with a React↔Vue move. Priced individually; we'll scope sensibly on the intake call.
Do you cover Nuxt / Next.js specifically?
Nuxt and Next.js are flagged where they affect the migration or TS adoption (routing, SSR), but changing the SSR framework itself is a separate engagement.
Will you sign an NDA?
Yes.
About
I've shipped production applications in both React and Vue across 20+ years of frontend work. The translation guidance comes from actually having built the patterns on both sides, not from reading the docs.
More about Paper Scissors & GlueReady to start?
Book an intro call. If we're not a fit, I'll tell you on the call.