# Use the Migration Verification Tools (Beta)

The migration verification tools facilitate and verify the completeness of your Aura-to-LWC and Lightning Out migrations.

:::note
MCP Tools for LWC is a pilot or beta service that is subject to the Beta Services Terms at [Agreements - Salesforce.com](https://www.salesforce.com/company/legal/agreements/) or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.
:::

To use this tool, pass the `--toolsets` flag as part of the `args` property of your MCP configuration file and specify `lwc-experts`. See [Use DX MCP Tools for LWC](/docs/platform/lwc/guide/mcp-intro.md) for configuration details.

Here are some possible prompts that invoke the migration tool.

## Verify Aura-to-LWC Migration Completeness (`verify_aura_migration_completeness`)

The `verify_aura_migration_completeness` tool provides a completeness checklist to facilitate an Aura-to-LWC conversion.

To use this tool, ask about the LWC conversion result of an Aura component. Example prompts include:

- Audit these Aura components and produce an LWC migration completeness checklist with gaps and blockers.
- Validate parity between Aura and LWC versions; list missing features, events, and styling differences.
- Recommend replacements for Aura-only features (navigation, events, eval) using LWC-safe patterns.

The tool evaluates your LWC conversion and provides an assessment of your code, providing a checklist with recommendations. You also get a completeness metrics based on functional and UI parity, event handling, data binding, modularity, error handling, localization, security, performance, and other best practices. This tool can also be invoked from the [`orchestrate_lwc_component_creation` tool](/docs/platform/lwc/guide/mcp-lwc.md) when running an Aura-to-LWC migration.

:::important
When working with these tools using Agentforce Vibes Extension, you must enable the `a4d-general-rules-no-edit.md` and `a4d-lwc-rules-no-edit.md` global rules. The `a4d-general-rules-no-edit.md` rule is enabled by default. For more information on configuring rules in Agentforce Vibes, see [Agentforce Rules](https://developer.salesforce.com/docs/platform/einstein-for-devs/guide/devagent-rules.md) in the *Agentforce Vibes Extension Developer Guide*.
:::

## Verify Lightning Out Migration (`guide_lo_migration`)

The `guide_lo_migration` tool provides guidance for Lightning Out (beta) to [Lightning Out 2.0](/docs/platform/lwc/guide/lightning-out-intro.md) migration, following a comprehensive workflow that covers architecture, lifecycle, and other patterns for the correct integration.

To use this tool, ask about migrating your Lightning Out code. Example prompts include:

- Evaluate this component for a Lightning Out 2.0 migration and identify any issues.
- Share instructions for Lightning Out 2.0 migration with event and styling recommendations
- Show me how to migrate this component to use Lightning Out 2.0 and explain the steps.

**See Also**

- [Salesforce DX MCP Server](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_mcp.htm)
- [LWC MCP Tools Reference](/docs/platform/lwc/guide/mcp-reference.md)
- [Use the Aura-to-LWC Migration Tools (Beta)](/docs/platform/lwc/guide/mcp-aura.md)
- [Migrate Aura Components](/docs/platform/lwc/guide/migrate-introduction.md)