Migrate Lightning Components Between Orgs

1. Runs discovery on the source org. It finds dependencies such as an Apex class, a Visualforce page or a subflow, and checks the target org's prerequisites. For larger moves it inventories each org involved.
2. Retrieves the components and their dependencies from the source org.
3. For larger moves, writes a phased migration plan and waits for the user's approval before building.
4. Deploys to the target org. This can be a whole feature with its object, components, Apex, screen flow, prompt template, quick action and permission set. It can also be a large set of Apex controllers and component bundles, with credentials, a connected app and a scheduler.
5. Fixes problems as they come up, such as version-gated properties and dependency ordering or a @wire bug in one component.
6. Places the components where users see them. It added a tab to a record page, seeded demo data and checked the result in the browser. In another case it set a dashboard page as an app's home page.

Next step: Deploy Metadata Across Orgs.