Migrating legacy components

This guide provides instructions for migrating Fuchsia components from Components v1 to Components v2.

For more details on the components migration effort, see State of the Components v2 Migration.

{% dynamic if user.is_googler %}

Note: For important additional considerations and resources you should review go/tq-cf-v2-migration-resources.

{% dynamic endif %}

Before you begin

Before you begin migrating, consider familiarizing yourself with the following topics:

• Introduction to the Fuchsia Component Framework: Components v2 comprises a set of concepts and APIs that are distinct from Components v1 or traditional OS program models.
• Introduction to the Test Runner Framework: Test Runner Framework is built on the Component Framework. You need to be familiar with these concepts before you migrate tests.

Get started

Begin your migration by following the guidance associated with your component's role:

• Migrate system components: Components that provide services to other components in the system. Typically, in Components v1 the mapping of service to component is registered in a sysmgr configuration file.
• Migrate test components: Components related to integration testing such as test components, mock components, and test harnesses.

Next, explore the following sections for additional migration guidance on specific features your components may support:

• Component sandbox features
• Diagnostics capabilities
• Other common situations