Field Migration

Nuix Discover has no built-in way to move coded values from one field to another — for example, moving the notes you coded on 25 documents into the notes field your teammate is using. Claira's Field Migration does exactly that: pick a From field and a To field, choose how to handle existing values, test it safely on one document, and run it across your whole selection.

Field migrations are free — they don't use AI or consume tokens.

Before you start

1. A saved Nuix API token for the case. Migrations run on Claira's servers, so they keep working even if you close the tab. This uses the same token as background processing — see Background processing setup. If no token is saved, the Field Migration screen shows a shortcut to Settings.
2. Selected documents. In Nuix Discover's browse list, select the documents to migrate. The migration runs on your current selection.

Open Field Migration

Open the Claira menu (the ☰ icon), hover over More at the bottom, and choose Field Migration. The More menu is also where Multi-Code, Case Context, and Settings now live.

Choose your fields

Both field pickers show the same three sections:

• Claira fields — the fields already connected to Claira for this case (any type).
• Pick list fields — every pick list field in the case, listed automatically.
• Add a field by ID — other field types (memo, text, date…) can't be listed automatically. Enter the field's ID and its type to use it anyway.

The destination list excludes whichever field you chose as the source.

As soon as both fields are chosen, Claira tells you whether the two field types work together — for example, anything can go into a memo field, but text into a date field is unverified and should be tested first.

Options

• Copy or Move — Copy leaves the source values in place; Move clears the source field after each successful copy.
• If the destination already has a value — Skip the document (it's left untouched and flagged in the results) or Overwrite it.

Documents whose source holds several values are copied value-by-value when the destination supports it; if the destination can only hold one value, those documents are skipped and flagged rather than losing data silently.

Check, test, then run

1. Check selection reads your selected documents (no changes) and shows what would happen: how many will migrate, how many will be skipped and why.
2. Test on one document performs a real write on one randomly chosen document that has a source value, then shows the before and after values. If the destination rejects the value (the text-into-date case), you find out here — on one document, not a thousand. Undo test restores the document's previous values. Note that Nuix Discover's own coding history still records the brief change.
3. Start migration confirms the summary and runs the migration on Claira's servers. You can watch progress live, cancel at any time (documents already migrated stay migrated), or close the tab and come back.

The migration ID

Each run gets an ID like MG012. If your case has a Log Field connected (the same field bulk scans stamp), every migrated document is tagged with the migration ID — so you can search Discover for everything a specific migration touched. See Fields for connecting fields.

Migration history

The Migration history list on the same screen shows every run for the case: who ran it, when, from and to which fields, its status, and per-document results — including exactly which documents were skipped or failed and why. Use the search box and status filter to find a specific run.

Good to know

• A migration is not reversible once it runs (only the one-document test can be undone). Use Check selection, the test, and the skip option to be confident before you start.
• Values going into a pick list only migrate when they exactly match one of the destination's choices; everything else is skipped and flagged.
• Migrations run entirely through the Nuix Discover API with your case's saved token — Claira does not keep copies of your documents' field values after the run.