Rescue your legacy VR app: ported to Unity 6 and OpenXR, then kept running
For VR training and brand apps built in 2019–2023 on the Oculus SDKs that broke, or can no longer be updated. A fixed-price audit, a port to a current stack, and managed operations so it keeps working.
Quick answer
If your VR app was built between 2019 and 2023 on Unity 2019–2022 with the Oculus Integration or the Oculus XR Plugin, it is running on tooling Meta has deprecated in favour of OpenXR. It may still start today, but you can't easily change it, rebuild it or fix it after the next Horizon OS update. VR Express ports it to Unity 6.3 LTS, OpenXR and XR Interaction Toolkit 3, keeping your scenes and content, and then runs it for you: headsets, OS-update testing, content refresh and a usage dashboard. We start with a fixed-price audit, credited to the port.
Who this is for
Between 2019 and 2023 many companies paid for a VR app: onboarding, safety, product training, HCP education, an event experience. Then the people moved on. Today the app is a build file on a shared drive and a box of headsets nobody wants to update.
- L&D and HR teams whose VR onboarding or training still has learners but no developer.
- Marketing and brand teams with an event or HCP experience they want to run again, with new content.
- Innovation teams that own a successful pilot that never became a maintained product.
- Agencies with client apps they built and can no longer support. We take over the port and the care, white-label if you prefer.
The usual triggers: the app crashes or misbehaves after a headset update, a new headset model won't run it, the content is out of date and nobody can open the project, or IT wants the devices under proper management.
How it works
- Audit (fixed price). We open your source, record the Unity and SDK versions, list every third-party package and whether its licence is still yours, take a snapshot of every scene and object, and test the current build on your headsets. You get a written report: what we keep, what we replace, the risks and a fixed price for the port.
- Port. We move the project to Unity 6.3 LTS with the Universal Render Pipeline, OpenXR with the Meta Quest feature, XR Interaction Toolkit 3 and XR Hands. We keep the original IDs of your assets and scripts, so scenes and prefabs carry over instead of being rebuilt by hand. Owned paid assets are restored from your licences, materials are upgraded to URP, and the Quest build pipeline is brought up to date.
- Device QA and handover. Every port compiles clean, and each one gets a device QA pass on your headset models before handover. You receive a private repository, a validation report and a build you can install.
- Run. We keep it working: device fleet management, regression testing when Meta ships a Horizon OS update, content refreshes, a usage dashboard and a care plan with agreed response times.
The full method, from discovery to optimisation, is described on our process page.
What you get: pilot, full port, run
- Pilot: the rescue audit. A fixed-price pilot of a few weeks that ends with the audit report, a port plan and a fixed quote. The pilot fee is credited to the full port.
- Full port. The app moved to Unity 6.3 LTS, OpenXR and XR Interaction Toolkit 3, with the device QA pass, a private repository in your name and a validation report. One codebase can produce more than one app: one of our client repositories already builds four apps, two for Quest and two for Windows.
- Run. A monthly or yearly plan: headsets enrolled and kept on the right app version, OS-update testing, content refreshes and a usage dashboard. Our full operations plan already runs for Postbank.
For package levels and care plans, see pricing.
Why we can do this at a fixed price
We did it to ourselves first. In October 2026 VR Express ported its own catalogue of 33 legacy VR projects, built on Unity versions from 2019 to 2022, to Unity 6.3 LTS with OpenXR and XR Interaction Toolkit. All of them compile with zero errors. That run turned into a repeatable toolchain: a snapshot of the original before anything changes, a porter that keeps asset IDs, a catalogue of the fixes that came up across dozens of projects, and a validation step that flags missing scripts, meshes and materials per scene.
That is why the audit can give you a fixed price: most of the problems your project will hit, we have already met. What we don't claim is that a compiled port is a finished product. Each port gets a device QA pass before handover, because a headset is the only honest test.
Legacy VR apps from our own catalogue
- Postbank VR Onboarding
Banking · 2021 · VR onboarding programme
Gamified VR modules that take new hires through the bank's history, culture and values, with virtual tours of key locations and simulated customer conversations. The onboarding project is part of the catalogue we moved to Unity 6.3.
- Postbank Onboarding Version 2
Banking · 2020 · VR + gamification
The second iteration of the onboarding programme: a standardised training module that brings new hires into the company culture.
- Janssen VR
Pharma · 2019 · HCP education in VR
An immersive simulation that visualises complex biological processes for healthcare professionals at medical conferences. Built in 2019, it is one of the projects we ported from its original Unity version to Unity 6.3.
- Meta Quizzes Prospan (Salveo)
Pharma · 2023 · Gamified VR quiz
HCPs answer questions by throwing a virtual ball at targets and learn the product benefits along the way, with an integrated product video. Also part of our Unity 6.3 port programme.
- Zentiva Sideral VR
Pharma · 2023 · Educational VR
An educational VR experience that visualises the molecular benefits of Sideral for healthcare professionals. Ported to Unity 6.3 with the rest of the catalogue.
More in our XR case studies and the full project portfolio.
Rescue vs rebuild vs leaving it in the drawer
Most teams in this position weigh three options. Here is how they compare.
- Leave it in the drawer. Costs nothing today. But the content you paid for stops reaching learners, the headsets age without management, and the next OS update may decide for you.
- Rebuild from scratch with a new agency. You get a modern app, but you pay again for scenes, models and logic you already own, and you wait months for something your people already know.
- Rescue and run. You keep what works, move it to a supported stack, and get a team accountable for keeping it working. The audit tells you up front whether a port makes sense; if a rebuild is the better call, the report says so.
A rescued training app can also grow with new modules. See our VR training solutions.
Full comparison: port vs rebuild a legacy VR app.
Why VR Express
VR Express is an independent XR studio in Sofia, Bulgaria, working since 2015, and we have run our own catalogue through the same port we offer you. One team covers the audit, the Unity work, device setup and long-term care: no hand-off between a build agency and a support desk.
Frequently asked questions about VR app rescue
Our VR app was built by another agency. Can you still rescue it?
Yes, as long as you can give us the Unity project source (or the agency's repository) and the licences for any paid assets it uses. The audit tells you exactly what is there, what is missing and what the port will take before you commit to anything. If only the installed app (APK) survives, we tell you that honestly in the audit: without source, the realistic option is a rebuild, not a port.
Why can't we just keep using the old build?
Sometimes you can, for a while. The problem is change: older builds made with the Oculus Integration SDK or the Oculus XR Plugin depend on tooling that Meta has deprecated in favour of OpenXR. The moment you need a content change, a new headset, a store or security update, or a fix after a Horizon OS update, the old project is hard or impossible to rebuild. Porting it to a current, supported stack makes it maintainable again.
What exactly do you port the app to?
Unity 6.3 LTS with the Universal Render Pipeline, the Unity OpenXR plugin with the Meta Quest feature, XR Interaction Toolkit 3 and XR Hands for hand tracking. We keep the original asset and script IDs so your scenes, prefabs and content carry over instead of being rebuilt, and we deliver the project as a repository your team, or any future vendor, can open.
Will the ported app work on our headsets on day one?
We don't hand over anything that only compiles. Every port compiles clean in Unity 6.3, and each port then gets a device QA pass on your headset models before handover, with a written list of what was checked. If something from the original cannot be carried over, such as a paid asset you no longer hold a licence for, it is listed in the audit, not discovered at the end.
What does the fixed-price audit include and what does it cost?
The audit covers the source, the SDK and Unity versions, third-party packages and their licences, the scenes and the devices you run. You get a written report with the port plan, risks and a fixed price for the port. It is a fixed-price pilot, and its fee is credited to the full port if you go ahead. We quote the exact amount once we know the size of the project.
What does the Run phase cover?
Device fleet management (enrolment, app versions, kiosk settings), regression testing when Meta ships a Horizon OS update, small content refreshes, a usage dashboard with sessions and completions, and a care plan with agreed response times, as a monthly or yearly plan.
Do you also take over apps for agencies, white-label?
Yes. Agencies that built VR apps for their clients in 2019 to 2023 and no longer have a Unity team can hand us the port and the ongoing care. We work under your name or ours, whichever your client relationship needs.
Which VR app should be working again?
Tell us what the app does, when it was built and which headsets you run. We will tell you in 30 minutes whether a port makes sense and what the audit covers.