Datacat

Services / CRM & Ops Platforms

Vlocity to OmniStudio Migration

Custom build

Salesforce retires Vlocity Public Sector managed package access on 1 May 2028. We run a fixed-scope program to assess with the OmniStudio Migration Assistant (OMA), migrate in waves, and cut over to OmniStudio standard runtime before you lose access.

Early-access product:View product overview · Book a pilot

Who this is for

Program and platform leaders on Salesforce Public Sector Solutions with Vlocity OmniStudio in managed-package runtime — especially government and regulated enterprises with a hard deadline and a regression surface too large for ad hoc upgrades.

The risk if you wait

After 1 May 2028 you will no longer be able to access the Vlocity Public Sector managed package. Salesforce recommends upgrading the package, then migrating to standard runtime with the OmniStudio Migration Assistant. Other Vlocity managed packages must also move to standard runtime; Salesforce has not set dates for those segments, but the direction is clear.

  • OMA surfaces blockers that still need manual remediation and Angular rebuilds
  • Production cutover must move in controlled waves with credible regression evidence
  • Deploy pipelines still built for Vlocity Build Tool must shift toward metadata and SF CLI
  • Specialist capacity tightens as more estates compete for the same 2028 window

What we deliver

  • Assessment and migration roadmap

    OMA-led inventory, blocker triage, and a phased plan tied to dev, validation, and production — with fixed-price gates per phase.

  • Remediation and component rebuild

    Hands-on fixes for OMA-flagged issues, calculation logic moved to Business Rules Engine where required, and Angular components rebuilt where automation cannot.

  • Migration waves

    Repeatable waves through non-production and production with CAB-ready evidence, rollback thinking, and hypercare after each cutover.

  • Pipeline transition

    Move release trains from Vlocity Build Tool toward metadata deploys as components land in standard runtime — documented for your internal team.

  • Regression automation

    Test harnesses your QA team can extend — so each wave is evidence-backed, not hope-backed.

Outcomes you can expect

  • OMA assessment and blocker plan
  • Phased production cutover
  • Pipelines moved off Vlocity Build Tool
  • Regression evidence per wave

Phased fixed-price delivery

  • Discover & assess (4–6 weeks)

    OMA runs, blocker backlog, wave sizing, and a fixed-price proposal for migration waves and cutover.

  • Migration waves (6–12+ months)

    Parallel workstreams through dev and validation, then production cutover per wave — typical for large public-sector estates.

  • Cutover & hypercare

    Final production moves, pipeline handoff, and stabilisation until your operators own daily change.

Sized for programs in the mid six figures and above — fixed-price per phase after assessment, not day-rate staffing. We scope for 6–12 month delivery horizons on large estates.

Relevant delivery experience

DevOps support for about 500 engineers with daily Salesforce and Vlocity releases, on-demand sandboxes, and automation including AI-assisted steps.

Australian Government — Ministry of Health / NDIA →

Standard runtime is the destination

Managed-package OmniStudio was a stepping stone. Standard runtime brings OmniStudio components toward metadata deploys and packaging models Salesforce is investing in — but the journey is a program, not a weekend upgrade.

Fixed scope beats open-ended time and materials

We price assessment, each migration wave, and cutover separately so procurement can fund outcomes — regression evidence, production moves, and pipeline handoff — rather than an open calendar of consultants.

Related offers

Frequently asked questions

What is the official Public Sector retirement date?
Salesforce Help article 005384463 states that after 1 May 2028 customers will no longer be able to access the Vlocity Public Sector managed package, and recommends upgrading then migrating to OmniStudio standard runtime with OMA.
Do other Vlocity packages have the same date?
Salesforce’s August 2026 developer blog says other managed-package runtimes must also migrate to standard runtime, but no general retirement date is published yet. This program is built for Public Sector deadlines first and extends as your estate requires.
Does OMA remove all manual work?
No. OMA automates much of the component conversion, but Salesforce documents manual remediation, Angular rebuilds, and phased rollout. We plan for that reality in every wave.
Can you work with our incumbent integrator?
Yes. We can lead the migration workstream while your SI keeps the broader program — or embed with your internal platform team when they own the org.
Is there a product licence as well as services?
Yes. Early-access migration accelerators and SI toolkit licences complement the program; see the linked product overview and use the contact form to book a pilot.

Start with a fixed-price OmniStudio migration readiness assessment: OMA scope, blocker triage, and a phased fixed-price proposal before the 1 May 2028 Public Sector deadline.

Book a fixed-price assessment