Salesforce Docs Portal

Convert Lightning Out (Beta) Host Pages to Lightning Out 2.0 Using the MCP Migration Tool (Pilot)

Convert your Lightning Out (Beta) host pages to Lightning Out 2.0 with less manual rewriting. The Model Context Protocol (MCP) migration tool in the Salesforce DX MCP server encodes differences between loaders, $Lightning calls, and frontdoor-based authentication. AI-assisted clients connected to the Salesforce DX MCP server propose updated HTML and JavaScript. You still need administrator access for org configuration in Setup.

Where: This change applies to Salesforce developer tooling (Salesforce DX MCP) used with a connected org in Enterprise, Performance, Unlimited, and Developer editions.

Important
Important We provide this feature to selected customers through a pilot program that requires agreement to specific terms and conditions. To be nominated to participate in the program, contact your Salesforce account executive. Pilot programs are subject to change, and we can't guarantee acceptance. This feature isn't generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. We can't guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

When: Availability varies by channel. Confirm pilot or staged availability timeline with your Salesforce representative if the migration tool isn't enabled for all MCP users at general availability for Summer '26.

Who: Administrators need permissions to modify CORS, Session Settings, External Client Applications, and Lightning Out app registration in Setup. Developers configure the MCP client, install or update the Salesforce DX MCP distribution, and use org credentials following your org's security policies.

How: To migrate a Lightning Out (Beta) host page:

  • Back up your existing host HTML and JavaScript.
  • Enable the Salesforce DX MCP server with the Lightning Out migration tool.
  • Provide the External Client Application consumer key, org URL, and optional Lightning Out app ID.
  • Paste your legacy Lightning Out (Beta) host source into the MCP client and review the generated markup and scripts.
  • In the Lightning Out 2.0 app, recreate the components from your Lightning Out (Beta) Aura app.
  • Complete Setup tasks: add host domains under CORS and Trusted Sites for Inline Frames in Session Settings, set OAuth callback URLs that include frontdoor-url.html, and register the Lightning Out 2.0 app.
Note
Note The migration tool supports Lightning Out (Beta) host pages that embed custom Lightning web components only. Host pages that embed Aura components can't be converted with this tool.

For more information, see How Lightning Out 2.0 Compares to Lightning Out (Beta) and Set Up Authentication for Lightning Out 2.0.