Vue 2 is end of life.
Move without a rewrite.
Vue 2 stopped receiving fixes at the end of 2023, and the ecosystem moved on without it. We migrate Vue 2 applications to Vue 3 incrementally, using the compat build so the app keeps running and shipping while it happens. Prepaid in Hour Blocks of 6, 12 or 24 hours.
Within two business days
Your message goes straight to the studio. No sales queue, no account manager in between.
Prepaid Hour Blocks
Buy 6, 12, or 24 hours up front at $30/hr. Unused hours never expire.
10 live products
Vue 3 and TypeScript front ends running in production across our products, not a framework we read about.
You own the code
Full source, in your repository, with the reasoning written down. No lock-in to us or anyone else.
Six distinct pieces
hiding inside one ticket.
Teams under-estimate this migration because they cost the Vue version bump and forget the other five. Here is the whole shape of it.
Getting it booting on day one
The migration build runs Vue 3 while emulating Vue 2 behaviour feature by feature, with a warning for every place the old behaviour is being used. That turns an unknowable rewrite into a finite list you can burn down, and it means the application boots in the first days rather than at the end. Feature flags come off in batches, each batch its own commit.
- Compat build configured and booting
- Warning inventory turned into a task list
- Compatibility flags removed in batches
- The app stays runnable throughout
- Short-lived branches, not a six-month fork
- Clean exit from compat mode at the end
The breaking changes, one by one
The specific removals that bite. Template filters are gone and become methods or computed properties. The global event bus built on the instance event methods no longer exists and needs a real pattern behind it. The .sync modifier is replaced by the new v-model argument form, and the v-model contract on custom components changed prop and event names. Anything hung on the Vue prototype moves to the application config. Multi-root components change attribute fall-through, which usually shows up as styling that silently stops applying.
- Filters replaced with methods or computeds
- Event bus replaced with a real pattern
- v-model and .sync contracts updated
- Prototype extensions moved to app config
- Functional and render-function components
- Attribute fall-through issues found early
Vuex to Pinia, and the router
Vuex 4 exists as a stepping stone, but Pinia is the maintained path and removes most of the ceremony: no mutations, proper TypeScript inference, and stores that are just composables. We migrate module by module so the two can coexist during the transition rather than requiring one giant commit. Vue Router moves to version 4, which changes how the router is created, how the catch-all route is written, and how navigation guards resolve.
- Vuex modules migrated to Pinia stores
- Both stores coexisting during transition
- Vue Router 4 creation API
- Catch-all and dynamic route syntax
- Navigation guard behaviour verified
- Persisted state and hydration checked
The UI library swap
Usually the largest single piece of work, and the one that gets forgotten in estimates. Vuetify 2 to 3 renames components and props and changes the grid and theming system. Element UI becomes Element Plus. BootstrapVue has a separate Vue 3 successor. Each one means real template edits across every screen, not a dependency bump. We do it screen by screen with visual comparison, and we tell you up front which library is going to hurt.
- Vuetify 2 to 3 component and prop renames
- Element UI to Element Plus
- BootstrapVue to its Vue 3 successor
- Theme and grid system differences
- Screen-by-screen visual comparison
- Honest effort estimate per library
Build tooling and tests
Vue CLI is in maintenance and the ecosystem energy is in Vite. Moving the build usually takes development server start and hot reload from tens of seconds to near-instant, which pays for itself in developer time within weeks. Tests move to Vue Test Utils 2, which changes mounting and wrapper APIs enough that a mechanical pass over the suite is part of the job rather than an afterthought.
- webpack or Vue CLI to Vite
- Environment variable and alias handling
- Vue Test Utils 1 to 2 across the suite
- TypeScript configuration if you use it
- Lint and format rules updated for Vue 3
- CI pipeline green before merge
When Vue lives inside a backend app
Plenty of Vue 2 apps are not standalone: they are bundled inside a Laravel, Django or WordPress build, sometimes several small Vue instances mounted on different server-rendered pages. That changes the migration shape, because the asset pipeline and the mounting code belong to the backend. We work on both sides, which is the point - there is no handoff between a front-end team and a backend team, because the same studio does both.
- Vue bundled inside Laravel or Django
- Multiple mount points per page
- Asset pipeline and versioning updates
- Server-rendered data handoff patterns
- Inertia or plain API seam reviewed
- Deployment updated to match the new build
What the migration leaves behind.
A migration that ends with one enormous merge and no notes is a liability. This is the standing deliverable list.
A migration inventory
Before any code changes: every compat warning, every affected component, every dependency with no Vue 3 version, with an effort estimate per group. Yours whether or not you continue.
Batched, reviewable commits
One batch per category of change, each merged on its own. If something regresses in week three, the cause is one commit rather than one enormous merge.
An app that never stops running
The compat build keeps the application bootable from the first day, so your team can keep shipping features on the same branch line.
A green test suite
Whatever suite you had, migrated to Vue Test Utils 2 and passing in CI. If you had none, we add smoke tests for the routes that matter most.
A modern build
Vite configured for development and production, with environment handling documented and the CI pipeline updated to match.
Written handover
What changed, what patterns replaced the Vue 2 ones, and the short list of things we deliberately left for later with reasons.
Vue 3 running in production.
Client work stays under NDA, so what we show is what we run ourselves: our products, live, with Vue 3 front ends against real backends rather than a tutorial to-do list.
CijeneHR
A Vue 3 and TypeScript front end over a Laravel 12 API, handling search and comparison across thousands of products with price history. Exactly the bundled-into-a-backend shape most migrations have.
Read the case studyNajNajNovije
A news aggregator with a Vue 3 front end tuned for speed, pulling from multiple sources. Built to stay fast on mobile, which is where front-end weight is felt first.
Read the case studyStockLrn
A data-heavy Laravel and Vue application with interactive financial charts. Chart and widget components are usually the fiddliest part of any Vue migration, so this is the relevant kind of complexity.
Read the case studyThere is also a broader Vue developer page for component work, new builds and front-end features that are not migrations.
Four steps, no discovery call
you have to sit through.
Tell us the size and shape of the app. The first Hour Block is usually the inventory, so the estimate is based on your code rather than a guess.
Tell us the problem
A few sentences on what you have and what you need. Rough is fine - we ask the questions that matter and tell you honestly if it is not a fit.
Pick an Hour Block
Prepay a block of hours - 6, 12, or 24. The block is the budget: we work until it is used, or you top up.
Work in the open
Compat build first so the app keeps booting, then one merged batch per category of change, with the screens compared visually before and after.
Handover and support
You get the source, the runbook, and a short support window for anything that surfaces after launch.
Bought in
prepaid Hour Blocks.
No volume games and no agency margin on top. You buy the block of hours that fits the size of the job, so you know the number before we start rather than after.
Typically enough for a focused fix, a small feature, or an integration you are stuck on.
Start with StarterTypically enough for a working prototype, or one well-scoped feature built and shipped.
Start with StandardTypically enough for a larger build with integrations, auth, or billing wired in.
Start with ProEvery Hour Block is hours at $30/hr with no discount. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire - roll them into the same project or a later top-up. If the work runs long, you buy another block; nothing is billed without you agreeing to it first.
Frequently asked.
Vue 2 still works. Why migrate at all?
Vue 2 reached end of life on the last day of 2023, so it receives no security or bug fixes. The practical pain arrives through the ecosystem rather than Vue itself: the UI library you use has stopped releasing for Vue 2, new hires have never written it, and every npm audit produces findings you cannot resolve without moving. It works until the day it blocks something, and that day is not scheduled.
What is an Hour Block, and what if the job takes more or fewer hours?
An Hour Block is a prepaid block of hours: Starter is 6 hours for $180, Standard is 12 hours for $360, Pro is 24 hours for $720. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire and roll into the same project or a top-up. If the work runs over, you buy another block, and nothing gets billed without you agreeing to it first.
Do we have to rewrite every component in the Composition API?
No, and you should not. The Options API is fully supported in Vue 3 and is not deprecated. Rewriting three hundred working components into a different style is risk with no user-visible payoff. We migrate them as they are, and use the Composition API only for new code or where a component genuinely needs shared reactive logic.
Can the app keep shipping features while the migration happens?
Yes, and that is why the compat build exists. The migration build runs Vue 3 with Vue 2 behaviour enabled per feature, so the application boots on day one and you turn the compatibility flags off in batches. That keeps the branch short-lived rather than a six-month fork nobody dares merge.
What usually breaks?
The reliable offenders are template filters, which were removed outright, the global event bus built on the instance event methods, the sync modifier, the changed v-model contract on custom components, functional components, and anything attached to the Vue prototype. Multi-root components also change how attributes fall through, which shows up as styling that quietly stops applying.
What about Vuex, Vue Router and our UI library?
Vuex 3 goes either to Vuex 4 as a holding step or straight to Pinia, which we would normally recommend since it is the maintained path and needs less boilerplate. Vue Router moves to version 4 with a new creation API and a different catch-all route syntax. The UI library is usually the biggest single piece: Vuetify 2 to 3, Element UI to Element Plus, BootstrapVue to its Vue 3 successor, each with real template changes.
Should we move off webpack at the same time?
Usually yes, because Vue CLI is in maintenance mode and Vite is where the tooling effort goes now. Development server start and hot reload typically go from tens of seconds to near-instant, which pays for the migration in developer time alone. If your build has heavy custom webpack configuration we will say so and price it separately rather than pretending it is free.
How do we start?
Send a few sentences through the form on this page: roughly how many components, which UI library, and whether it is a standalone app or bundled into a backend framework. You get a reply from us directly, usually within two business days, with a realistic read on effort.
Tell us about your Vue 2 app.
Roughly how many components, which UI library, and whether it is a standalone SPA or bundled inside a backend framework. A few sentences is plenty - we read every message and reply within two business days with an honest read and the Hour Block that fits.
Prefer email?
[email protected]