# Migrations in action

You've prepared your Cortex workspace for a migration — what can you do now to maintain entity health and encourage completion of the migration?

Learn more below on how you can prioritize migration tasks and gain insights to improve your practices.

## Review, prioritize, and complete tasks

<div align="left"><figure><img src="/files/XJ8qPNFducoW5WKAdLyG" alt="Review tasks on the homepage." width="413"><figcaption></figcaption></figure></div>

<details>

<summary>Prioritize and complete work from the homepage</summary>

<figure><img src="/files/NX2sgpO81Bch95Yq7aNL" alt=""><figcaption></figcaption></figure>

Engineers use the [Engineering homepage](/streamline/homepage.md) as their personalized daily starting point. It provides a centralized view of key signals and tasks related to migrations, including:&#x20;

* **Active work**: See your open PRs, PRs assigned for review, active Jira tickets, and action items from Scorecards and Initiatives, ensuring you are aware of your responsibilities and can quickly address migration-related tasks.
* **On-call status**: See current and upcoming on-call shifts, helping you stay prepared for incident response.
* **Scorecards and Initiatives**: See real-time progress toward migration and modernization standards and initiatives.
* **Shortcuts**: Use direct links to quickly access your owned entities.&#x20;

</details>

<details>

<summary>Act on failing Scorecard rules</summary>

<div align="left"><figure><img src="/files/BFTtOkoA6D3lStVHUhmk" alt="The rule &#x22;resource limits are defined&#x22; is failing."><figcaption></figcaption></figure></div>

#### Review failing rules

When a Scorecard rule is failing, this information is surfaced to you in multiple ways:

* Scorecard rules that require your attention appear on the [Engineering homepage](/streamline/homepage.md).
* You can receive notifications via Slack, Microsoft Teams, or email when a Scorecard rule is failing.
  * Learn more in the [Notifications docs](/configure/settings/notifications.md).
* You can review a Scorecard's progress in [reports](/improve/reports.md) or by [viewing the Scorecard](/standardize/scorecards/evaluate.md) in Cortex.

#### Remediate failing rules&#x20;

When a service falls short of standards, there are different ways you can approach remediation:

* Use [Cortex MCP](/get-started/mcp.md) to get suggestions for remediations. Ask a question such as *What are some quick wins for my Migration Scorecard?* and the MCP will respond with a prioritized list for you to focus on during remediation efforts.&#x20;
* [Set up an Initiative](/improve/initiatives.md) to assign and track remediation tasks. For example, you might create an Initiative that asks teams to reach compliance within the next month. In other words, they would need to ensure that their owned entities have achieved all rules on your migration Scorecard.&#x20;
  * You can also automatically create issues in Jira, ClickUp, Azure DevOps, and GitHub based on Initiatives. Learn more in [Creating issues based on Initiatives](/improve/initiatives/issue-config.md).
* Identify and troubleshoot trends in Scorecards, and consider scalable remediation efforts. Learn more in [Review and evaluate Scorecards](/standardize/scorecards/evaluate.md).

</details>

## Analyze trends in Eng Intelligence and reports

### Eng Intelligence

Eng Intelligence allows you to view organization-wide and historical data, making it easy for leaders to validate the impact of readiness programs and for teams to see their progress toward readiness goals.

<div align="left"><figure><img src="/files/u5t0gB403DCo0cQUmQzQ" alt="Analyze trends in the DORA dashboard." width="563"><figcaption></figcaption></figure></div>

View [Eng Intelligence](/improve/eng-intelligence.md) metrics to see how your services are doing before, during, and after a migration, then take action to promote continuous improvement.

* **Establish a baseline**: Before the migration, monitor metrics to understand your organization's baseline.&#x20;
* **See impact**: During a migration, monitor the metrics to understand trends, validate improvements, or identify regressions. Launch a [Scorecard](/standardize/scorecards.md) or [Initiative](/improve/initiatives.md) for the migration and watch as metrics like MTTR, cycle time, or deployment frequency shift in real time.
  * For example, you can see how migration adoption (e.g., moving to a new cloud platform) impacts metrics. You might notice that as more services become compliant, MTTR drops, giving you data-driven validation of your migration's success.
* **Drive action**: If you identify a regression after a migration, or you notice some services are slower to meet migration requirements, you can create a targeted [Initiative](/improve/initiatives.md) to fix it.
  * Initiatives send notifications to users asking them to complete tasks by the deadline you configured. Learn more in [Initiatives and action items](/improve/initiatives.md).

### Reports

Use reports in Cortex to track migration progress and drill down by team or service.

* Use the [Bird's Eye report ](/improve/reports/birds-eye.md)to visualize entity scores as a heat map for your migration Scorecard, giving you a high level overview of progress.<br>

  <div align="left"><figure><img src="/files/EfcW1Pz13GLD9ZQM864g" alt="The Birds Eye report shows a heat map of entity progress for a Scorecard." width="525"><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cortex.io/solutions/migrations/in-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.