Salesforce details how to migrate Omnistudio components off the legacy managed package runtime (Vlocity Industries or Omnistudio Foundation packages) onto the Omnistudio standard runtime using the Omnistudio Migration Assistant (OMA) CLI tool. The standard runtime offers 2x-5x performance gains, full feature parity, simplified CLI-based deployments, and access to new features like Agentforce integration. The guide walks through a three-phase process (development, validation, production) with Assess and Migrate modes, plus scenario-specific variations depending on package type and data model. OMA reportedly cuts manual migration effort by 95%, though some manual work (like rebuilding Angular-based components) remains.
Table of contents
Omnistudio evolution: From managed packages to the standard runtimeBenefits of migrating to the standard runtimeFind your transition pathManaged package runtime versus standard runtimeWhat is the Omnistudio Migration Assistant (OMA)?How the migration process worksScenario-specific migration process variationsMigrate to all-new Omnistudio todayResourcesAbout the authorQuestions this post answers
How do I migrate Omnistudio components from the managed package runtime to the standard runtime?
Use the Omnistudio Migration Assistant (OMA), a Salesforce CLI plugin, installed via 'sf plugins install @salesforce/plugin-omnistudio-migration-tool@2.0.0-rc.57'. Run it in Assess mode to flag issues like namespace problems or Angular-based components, fix them manually, then run Migrate mode to move Flexcards, Omniscripts, Data Mappers, and Integration Procedures to the standard data model across development, validation, and production phases. daily.dev surfaces guides like this for teams planning platform migrations and runtime upgrades.
What performance improvement does the Omnistudio standard runtime offer over the managed package runtime?
The standard runtime delivers 2x to 5x faster execution depending on configuration, with Flexcards up to 5x faster, Integration Procedures up to 4x faster, Data Mappers up to 3x faster, and Omniscripts up to 2x faster. Internal testing showed average execution of 2112ms on the standard runtime versus 5061ms on a managed package runtime. Track platform performance benchmarks like these on daily.dev before committing to a runtime migration.
Do I need to upgrade my Vlocity Industries managed package before migrating to the Omnistudio standard runtime?
Yes, upgrade to the Vlocity Industries managed package version Winter '26 or later before starting the migration process, regardless of which transition path applies to your setup. This is required whether you're on Vlocity Industries managed packages or the Omnistudio Foundation package. Developers planning staged platform upgrades can follow prerequisite changes like this on daily.dev.