# MigrationError

> For the complete documentation index, see [llms.txt](https://ensforge.com/llms.txt).

What MigrationError means, which codes it carries and how to catch it in ensforge. ENSv1 to ENSv2 migration is blocked for this name.

Source: https://ensforge.com/docs/reference/errors/migration-error

<ApiMeta kind="Error class" summary="5 codes · @ensforge/sdk" source="packages/sdk/src/errors/classes/MigrationError.ts#L36" />

ENSv1 to ENSv2 migration is blocked for this name.

## Fields [#fields]

| Field | Type | Description |
| --- | --- | --- |
| `blockers` | `readonly string[]` |  |

## Codes [#codes]

| Code | Meaning | Retryable |
| --- | --- | --- |
| [`NOT_ELIGIBLE`](/docs/reference/errors/NOT_ELIGIBLE) | The name cannot be migrated to ENSv2 yet. | No |
| [`ALREADY_MIGRATED`](/docs/reference/errors/ALREADY_MIGRATED) | The name is already on ENSv2. | No |
| [`NAME_NOT_LOCKED`](/docs/reference/errors/NAME_NOT_LOCKED) | The wrapped name is not locked, so it cannot use the locked migration route. | No |
| [`RECORDS_UNKNOWN`](/docs/reference/errors/RECORDS_UNKNOWN) | The name's records are not known, so they cannot be copied to its new resolver. | No |
| [`VERIFICATION_FAILED`](/docs/reference/errors/VERIFICATION_FAILED) | The migration was sent, but the name's ENSv2 state differs from the plan. | No |

## Catch it [#catch-it]

`Effect.catchTag("MigrationError", …)` or `error instanceof Errors.MigrationError`. See [Handle errors](/docs/sdk/handle-errors).