Is this for you?
- Vue 2 is EOL and you've been putting it off.
- The team keeps starting the migration and abandoning it.
- You're not sure whether to migrate incrementally or rewrite.
- Third-party dependencies are mixed — some migrated to Vue 3, some dead, some unknown.
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.
Scope
What's in
- Vue 2 → Vue 3 migration strategy
- Composition API adoption plan
- Dependency compatibility review
- Component inventory and prioritization
What's out
- Performing the migration
- Design system overhauls
- Backend API changes
- Routing framework swaps (Nuxt, etc.) — available as a separate engagement
Process
Intake
Day 1Kickoff, repo access, intro to the team.
Discovery
Days 2–5Component inventory, dependency graph, pattern identification.
Analysis
Days 6–9Incremental-vs-rewrite modeling, phase planning, effort estimation.
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
We're also considering Nuxt. Is that in scope?
Adding Nuxt mid-migration is a separate decision with its own scope — we'll discuss on the intake call.
Do you support Vuex → Pinia migration guidance?
Yes, included.
Can you do the migration for us?
Separately, yes. This engagement is the roadmap.
Will you sign an NDA?
Yes.
About
26+ years of full-stack experience across PHP, JavaScript, and Python. I ship production systems for teams that need senior technical work they can trust, from the founding engineer's perspective.
More about the studioReady to start?
Book an intro call. If we're not a fit, I'll tell you on the call.