Salesforce
OmniStudio Migration Testing: Standard Runtime Guide

Rishabh Kumar
Published On

Table of contents
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
How Do You Test an OmniStudio Standard Runtime Migration?
Test it as a before-and-after comparison. Record how each critical journey behaves on the managed package runtime, migrate in a sandbox, then run the same journeys on the standard runtime and compare outcomes, not page structure. Expect automated UI tests written against the old runtime to break, because Salesforce itself notes that the HTML element tags differ between the two.
Organisations using Salesforce Industries are moving their OmniStudio components, including OmniScripts, FlexCards, Integration Procedures and Data Mappers, off the managed package runtime that came from Vlocity and onto the standard runtime built into the Salesforce platform.
Salesforce’s Omnistudio Migration Assistant automates much of the conversion. What it can’t do is prove that every guided process still behaves the same for the people who use it.
What the Migration Changes
OmniStudio came to Salesforce with the Vlocity acquisition. Many Industries customers, in insurance, communications, energy, the public sector and beyond, still run it on a managed package runtime.
That's either a Vlocity Industries package with its own custom data model, or an Omnistudio Foundation package on the standard data model. Since Summer '25, OmniStudio has been package-free for new customers, and Salesforce is steering existing customers onto the standard runtime.
Area | Managed package runtime | Standard runtime |
|---|---|---|
Where it runs | Inside an industry managed package | Built into the Salesforce platform |
Data model | Custom objects for Vlocity packages, standard objects for Foundation packages | Standard data model |
Designers | Managed package designers | Standard designers |
How components render | Package wrappers and markup | Standard runtime wrappers and markup |
The Omnistudio Migration Assistant, a Salesforce CLI plugin, converts components, replaces legacy wrappers and produces an assessment report before anything moves. Salesforce also supports a hybrid approach, with old and new components running side by side during a phased migration. Once the managed package runtime setting is switched off, the org locks into standard runtime mode.
That last point shapes the whole test plan. The switch is effectively one way, so the proof that journeys still work has to exist before it’s flipped in production.
Use the Assessment Report to Plan the Testing
Run the Migration Assistant in assess mode before planning a single test. Its report shows the readiness of every component, and the components it flags as needing manual work are where behaviour is most likely to change.
Put the journeys that use those components at the top of the test list, alongside the journeys with the highest business risk.
Why Test Automation Breaks, and What to Test Instead
Salesforce’s guidance on the Migration Assistant flags the testing impact directly, because the HTML element tags differ between the two runtimes. Any UI test that finds OmniScript steps, FlexCard actions or form fields through the old markup will fail after migration, even when the journey works perfectly. That’s the obvious problem. The less obvious one is that some journeys will genuinely behave differently, and a wall of broken tests makes those real differences harder to spot.
Tests tied to page markup break easily. Learn which locator strategies survive structural change with our guide on test automation locator strategy.
Area | What can change | What to assert |
|---|---|---|
OmniScripts | Step navigation, conditional steps, validation, save and resume | The user can complete each path and ends in the same state |
FlexCards | Actions, data shown, conditional visibility | The right data and actions appear for each persona |
Integration Procedures | Calls to other systems, error handling, response mapping | Downstream systems receive and return the same data |
Data Mappers | Field mappings, especially where custom objects become standard ones | Records hold the same values as before migration |
Embedded components | Custom LWCs inside OmniScripts and FlexCards | Behaviour and data exchange unchanged |
Portals | OmniScripts on Experience Cloud sites | Customers and brokers can complete them as before |
Removed or changed features | Capabilities the standard runtime handles differently, such as OmniOut, and older AngularJS-based OmniScripts, which are no longer supported | Journeys that relied on them have a working replacement |
For insurers, the riskiest journeys are usually quote and bind, first notice of loss and mid-term changes. For communications and energy, it’s order capture and service changes. Start there.
Check Performance Too
Salesforce reports that, in its internal testing, components ran markedly faster on the standard runtime. That’s a reason to migrate, and also something to verify for your own components.
Record how long your critical journeys take on the old runtime as part of the baseline, then compare after migration. A journey that’s slower, not faster, is worth investigating before the switch.
A Testing Plan for the Migration
Inventory and Prioritise
List every OmniScript, FlexCard, Integration Procedure and Data Mapper, the journeys each supports and who uses them, then rank journeys by risk and by the assessment report.
Capture the Baseline
Before migrating anything, run the critical journeys end to end on the managed package runtime, as each persona, and record the outcomes, including records created, values set, documents generated, data sent to other systems and timings.
Migrate in a Sandbox, in Dependency Order
Migrate bottom-up, so Data Mappers and Integration Procedures are in place before the OmniScripts and FlexCards that use them.
Compare Outcomes, Not Screens
Run the same journeys on the standard runtime, and classify every difference as a migration defect, an intended change approved by the business, or a test needing repair because markup changed.
Use the Hybrid Period Deliberately
If you migrate in phases, test journeys that cross old and new components, such as a legacy OmniScript calling a migrated Integration Procedure.
Rehearse the Switch
Turn off the managed package runtime in a full-copy sandbox and run the full suite, because the switch locks the org.
Keep the Evidence
The baseline, comparisons, every difference and its resolution, and who approved the production switch.
Keep the Suite Afterwards
The standard runtime receives platform changes in every Salesforce release, like the rest of the org.
If the migration also moves data from custom to standard objects, run the four layers from Salesforce data migration testing too.
Coded Tests or Intent-based Tests?
Salesforce recommends UTAM, its UI Test Automation Model, for automating OmniScript and FlexCard tests, with page objects maintained alongside components so tests survive structural changes. That suits teams with developers to own the page objects. Intent-based tests, written as what the user does rather than which element they touch, take a different route to the same goal. Either way, the lesson from this migration is the same. Tests tied to the old markup are a cost you’ll pay again at the next structural change.
UTAM grew out of Salesforce's wider approach to testing Lightning components, and Salesforce LWC testing shows where it fits.
Testing the Migration with Virtuoso QA
Virtuoso QA fits a before-and-after migration because its steps describe what the user does, not the markup underneath.
A step like “enter the vehicle details and continue” is written in plain English, so the same journey can run on both runtimes. Where changed markup means a step must be re-targeted, self-healing repairs it only when it’s confident. Below that threshold, the test fails rather than guessing, and Touchstone classifies the failure, so a genuine behaviour change surfaces instead of being repaired into a pass.
Journeys check outcomes inside Salesforce and, through API steps, in the systems your Integration Procedures call. Touchstone’s proposals and approvals are versioned and recorded alongside the run results, ready for the person who signs off the switch.
Virtuoso QA's Salesforce test automation runs your OmniScript and FlexCard journeys on both runtimes and compares the outcomes, so every difference is found and decided before the one-way switch.
Related Reads
Frequently Asked Questions
What is the OmniStudio Standard Runtime?
Will My Automated Tests Break When I Migrate?
What is the Omnistudio Migration Assistant?
Can I Migrate in Phases?
Who Should Sign Off the Migration?
Written by

Rishabh Kumar
AI Testing & Quality Engineering Contributor
Rishabh leads business development and marketing at Virtuoso QA. He writes about AI-powered test automation, end-to-end testing, self-healing tests, and quality engineering, exploring how these capabilities can improve test coverage, reduce test maintenance, and support reliable software releases.










