This page describes the insights that Migration Center generates
about your infrastructure.

Migration Center collects information from your assets with the
discovery client, or from the data that you collect and upload using the
database scripts. Then, it analyzes the information collected
using predefined rules and automatically generates various insights based on the
preferences that you define.

## View insights for server and database assets

To view insights about a specific server or database, follow these steps:

1. Go to the **Assets** page.

   [Go to Assets](https://console.cloud.google.com/migration/discovery/assets)
2. On the assets details page, click the **Servers** or **Database deployments** tab.

3. From the list of assets, click the asset for which you want to view
   insights.

4. On the asset details page, in the **Insights** tab, review the available
   insights for the asset.

### Understand server migration insights

Server migration insights provide you with a technical assessment of
your server workloads fit for specific transformation objectives. These insights
help you determine the potential fit with a feasible Google Cloud product.
These insights also inform you if there are any technical blockers that prevent
you from modernizing your server assets such as virtual machine (VM) instances
to a feasible Google Cloud product such as Compute Engine or
Google Kubernetes Engine.

The assessment uses technical fit conditions that are evaluated against the
data collected from the source workloads. The fit conditions catalog is a
knowledge repository based on Google Cloud technical specifications and known
technical limitations of the transformation tools to be used for performing the
migration.

The **fit type** column shows you how well an asset matches a Google Cloud
product for migration using the following fit scores:

- **Fit unspecified:** there is not enough information to perform an assessment.
- **Good fit:** no issues found, your workload is fit for transformation to the suggested Google Cloud product.
- **No fit:** technical blockers found that prevent the migration to a Google Cloud product.
- **Fit with effort:** some technical issues found which can be resolved with some effort to enable the migration to a Google Cloud product.

The fit level per server is performed by reviewing several fit conditions, called
*fit rules*, and their aggregated result is presented as the server level technical
fit score.

Along with the feasible Google Cloud product and fit type, the insights also provide
you with information such as suggested Compute Engine machine type, cores, memory,
and recommendation for simultaneous multithreading (SMT).

#### Detected software

Migration Center collects information about software products installed
on a specific server asset. This information helps you define the scope of your
migration assessment and determine which server asset can be migrated to a
product such as Compute Engine, or transformed to be deployed on a
fully-managed service such as GKE.

> [!IMPORTANT]
> **Important:** The detected software list might include AI-powered suggestions. Rate the suggestions with the **thumbs up** or **thumbs down** buttons. Migration Center uses your feedback to improve the accuracy of the suggestions.

### Understand database migration insights

Database migration insights provide you with a detailed technical assessment with
the potential fit with a feasible Google Cloud database product. The
**fit type** column shows you how well an asset matches a Google Cloud
database product for migration using the following fit scores:

- **Fit unspecified:** there is not enough information to perform an assessment.
- **Good fit:** no issues found, your database is fit for migration to the suggested Google Cloud database product.
- **No fit:** technical blockers found that prevent the migration to a Google Cloud database product.
- **Fit with effort:** some technical issues found which can be resolved with some effort to enable the migration to a Google Cloud database product.

You can also see a list of compatibility issues between the source and target
databases, along with the recommended resource allocation for the
Google Cloud database product.

## What's next

- Learn how to [create groups of assets](https://docs.cloud.google.com/migration-center/docs/create-groups).