Skip to main content
err:unkey:data:migration_not_found
The migrationId you sent to keys.migrateKeys doesn’t exist in your workspace. You get HTTP 404.
Example response

Likely causes

  • The migration ID is for another workspace, such as a staging ID used with a production root key.
  • You don’t have a migration ID yet. There’s no endpoint to create one: our support team sets up the migration and gives you the ID.

How to fix

  1. Use the migrationId we gave you, with a root key from the same workspace. Use the same ID for every batch of the import.
  2. If you don’t have one, contact support before you import.
Last modified on October 6, 2026