domains / families / software-engineering / experience-lwc-legacy-migrate

experience-lwc-legacy-migrate

authentic

Migrate legacy Salesforce UI stacks onto modern LWC — Aura → LWC conversion completeness verification and Lightning Out Beta → Lightning Out 2.0 host-page migration. TRIGGER on \"verify Aura to LWC migration completeness\", \"migrate Lightning Out Beta to LO 2.0\", \"upgrade $Lightning.use() to <lightning-out-application>\", \"replace hardcoded LO tokens with OAuth PKCE\", \"write an LO 2.0 host page\", or an external Lightning Out page that stopped rendering; also `.cmp`/`.js-meta.xml` files alongside LWC. DO NOT TRIGGER for the initial Aura-to-LWC conversion (use experience-aura-lwc-migrate), a React-to-LWC migration, or building a new LWC (use experience-lwc-design-generate).

When to use

• User has already converted an Aura component to LWC and wants a structured
• User has a non-Salesforce host page that embeds Salesforce LWC via
• User is upgrading `$Lightning.use()` / `$Lightning.createComponent()` calls
• User needs to replace a hardcoded LO auth token with OAuth PKCE + front-door

When not to use

• initial Aura-to-LWC conversion
• React-to-LWC migration
• building a new LWC

Skill page

Source