> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate data after migration

export const RecipeBadges = ({badges = []}) => {
  const map = {
    "recipe": {
      label: "Recipe",
      color: "#A86400"
    },
    "ai-excellence": {
      label: "AI excellence",
      color: "#653EE8"
    },
    "production-readiness": {
      label: "Production readiness",
      color: "#226686"
    },
    "incident-mgmt": {
      label: "Incident management",
      color: "#86198F"
    },
    "migrations": {
      label: "Migrations",
      color: "#0E7C66"
    },
    "compliance": {
      label: "Compliance",
      color: "#475569"
    },
    "dora": {
      label: "DORA metrics",
      color: "#1D4ED8"
    },
    "security": {
      label: "Security",
      color: "#B42318"
    },
    "operational-readiness": {
      label: "Operational readiness",
      color: "#B54708"
    },
    "dev-onboarding": {
      label: "Developer onboarding",
      color: "#C11574"
    }
  };
  const items = badges.map(key => map[key]).filter(Boolean);
  if (items.length === 0) return null;
  return <div className="not-prose flex flex-wrap gap-2 mb-6">
      {items.map(b => <span key={b.label} className="rounded-lg px-2 py-1 text-xs font-medium" style={{
    backgroundColor: b.color,
    color: b.textColor || "#FFFFFF"
  }}>
          {b.label}
        </span>)}
    </div>;
};

<RecipeBadges badges={["recipe", "migrations"]} />

[Data verifications](/configure/settings/entity-settings/verification) ensure that entity data in the catalog (e.g., ownership and metadata) stays accurate over time.

As a best practice after migrating data (for example, migrating services from spreadsheets into Cortex), we recommend scheduling a data verification to ensure your entities are up to date.

## Set up a data verification after a migration

You must have the `Configure verification periods` permission to set up a verification.

1. In Cortex, navigate to the [Entity verification settings](https://app.getcortexapp.com/admin/settings/entities/verification) page. Click **+Add verification period**.
2. In the side panel, fill in the fields:
   * **Start date** and **End date**: Enter the start and end dates for the verification period.
     * The start date cannot be in the past. The end date must be at least one day after the start date.
     * Choose a timeframe that is reasonable based on the number of entities that each team will need to verify.
   * **Name**: Enter a descriptive name, e.g., `Validate data after migration`.
   * **Verification instructions**: Enter clear and concise instructions that will appear on the entity's details page, e.g., `These entities were recently imported from spreadsheets. Please review and verify whether they're accurate.`
   * **Require reason for verification**: Check this box to require the user to include a reason if they confirm that the entity's data is invalid.
     * We recommend requiring a reason, as it will allow you to quickly understand what needs to be fixed on an entity.
   * **Team member roles responsible for verification**: Select which Cortex users will be responsible for verifying data.
     * If you select multiple roles, any of those users can verify data.
     * If you do not select a team member role, any user who owns the entity can verify data.
   * **Entities to verify**: Specify which entities the verification policy applies to.
     * You can select a specific entity type to include (for example, you could apply the verification to all entities of the type `service`) or if your entities have groups assigned, you can filter by specific groups.
     * Under **Advanced options**, you can use CQL to refine which entities you want to verify. For example, you might narrow your selection to entities created in the last two weeks:<br />
       `entity.created() < duration("P2W")`
3. Click **Create verification period**.

Within a few minutes of saving the verification period, it will be visible to admins in the list of verifications on the [Entity verification settings page](https://app.getcortexapp.com/admin/settings/entities/verification). Entity owners will receive notifications to verify their entities.

## Remediate entities with incorrect data

After setting up the verification period, you can [create a CQL report to view all entities that have been verified as incorrect](/configure/settings/entity-settings/verification#view-all-unverified-or-incorrect-entities) using a prebuilt CQL report template.

Cortex also offers a prebuilt [Scorecard template to flag entities that have not yet been verified](/configure/settings/entity-settings/verification#flag-unverified-entities-via-scorecard).


## Related topics

- [Data verification](/guides/product-areas/data-verification.md)
- [Accelerate migration to K8s](/guides/migrations-and-modernization/accelerate-migration-to-k8s.md)
- [Validate a configuration](/api/rest/datadog-api/validate-a-configuration.md)