# Omnistudio Lwc Omniscript Migration

> Migrate classic Visualforce-based OmniScripts to LWC-based runtime with feature parity and regression testing. NOT for new OmniScript design — use omnistudio/omnistudio-lwc-integration.

- Skill: `pranavnagrecha/omnistudio-lwc-omniscript-migration` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds add pranavnagrecha/omnistudio-lwc-omniscript-migration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pranavnagrecha/omnistudio-lwc-omniscript-migration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: PranavNagrecha (https://skillmd.com/u/pranavnagrecha)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/pranavnagrecha/omnistudio-lwc-omniscript-migration

---


# OmniStudio LWC OmniScript Migration

Salesforce is deprecating the Visualforce OmniScript runtime. Orgs must switch each OmniScript to the LWC runtime via the 'Run OmniScripts in LWC' setting and retest. Third-party templates and embedded custom VFs need replacement LWCs. This skill covers inventory, parity testing, and the rollout sequence.

## Adoption Signals

Any org still using VF-mode OmniScripts; required by the deprecation timeline.

- Pre-migration audit when an OmniScript embeds custom Visualforce in a step or footer template.
- Required when LWC OmniScript runtime parity gaps (e.g., specific Action types) must be evaluated before the cutover.

## Recommended Workflow

1. Inventory OmniScripts via OmniScript object query; note Type, Sub-Type, Active version.
2. Enable 'Run OmniScripts in LWC' at org level; each OmniScript can still opt out temporarily.
3. For each script: activate LWC mode; run QA scenarios; fix any parity gaps (custom VF → LWC rewrite).
4. Update embedded scripts: pages that host OmniScripts via `<c-omniscript>` LWC instead of VF include.
5. Deprecation cutover: disable VF mode globally; remove unused assets.

## Key Considerations

- Some template types (signature pad, legacy chart) need custom LWC rewrite.
- Styles differ subtly in LWC mode; QA designers carefully.
- LWC runtime is faster but strict about async patterns — some VF-only tricks won't port.
- Don't justify the migration with a borrowed percentage — the widely-quoted "30–60% faster" is attributable to nobody. Justify it on supportability (the AngularJS runtime is no longer supported) and measure your own scripts before and after if a number is wanted.

## Worked Examples (see `references/examples.md`)

- *Phased LWC cutover* — 80 OmniScripts
- *Custom VF replacement* — Signature capture inside script

## Common Gotchas (see `references/gotchas.md`)

- **Style drift** — Colors off after migration.
- **Async timing** — Remote action timing different in LWC.
- **No opt-out left** — Business outage when last VF-only script flips.

## Top LLM Anti-Patterns (full list in `references/llm-anti-patterns.md`)

- Big-bang cutover without QA
- Ignoring deprecation timeline
- Custom VF assets left after migration

## Official Sources Used

- OmniStudio Developer Guide — https://developer.salesforce.com/docs/atlas.en-us.omnistudio_developer.meta/omnistudio_developer/
- OmniStudio for Salesforce — https://help.salesforce.com/s/articleView?id=sf.os_omnistudio_for_salesforce_overview.htm
- OmniScript to LWC OSS — https://developer.salesforce.com/docs/atlas.en-us.omnistudio_developer.meta/omnistudio_developer/os_migrate_from_vf_to_lwc.htm