Field MigrationCopy Anchor Link

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: four numbered steps take you from picking the two fields to running the migration across your whole selection, with a safe test on one document on the way.

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

Before you startCopy Anchor Link

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 connected and Claira holds one you can use, the Field Migration screen offers to connect it with one click; otherwise it shows a shortcut to Settings. See Connecting a token from a scan or Field Migration.
2. Selected documents. In Nuix Discover's browse list, select the documents to migrate. The migration runs on your current selection.

Open Field MigrationCopy Anchor Link

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.

The four stepsCopy Anchor Link

The screen walks you through four numbered steps, and each one opens only when the step before it is answered. A step's heading shows its number, and a tick once it is done; when a step is collapsed, its heading also says what you chose, so you can check your settings without opening anything. In a narrow panel only the step you are on is open at a time.

The Start migration button sits in a bar at the bottom that stays in view however far you scroll. When it is greyed out, the sentence beside it says exactly what is still missing.

Step 1: FieldsCopy Anchor Link

Claira opens on the From field alone. The To field appears as soon as you have chosen what to migrate from, because a destination is not a decision you can make before you know the source. If you clear From again, the destination you already picked is remembered and comes back with it.

The From list has the three sections it has always had:

• 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.

Fields Claira recognizes as your case's Date and Title fields appear pinned in a Recommended group at the top, so the most common migration targets are always one click away.

From opens on the field you were last working in. If you have picked a destination field elsewhere in Claira on this case, for a scan, a Multi-Code row or an Insight, Field Migration opens From on that field and says so in a short note under the picker. It is a convenience, not a decision: the picker is fully editable, the note disappears as soon as you choose for yourself, and the field stays where it is until you press through the checks and run. Field Migration only reads that memory and never sets it, so nothing you do here changes where your next scan writes. If nothing has been picked yet, or if the remembered field has been disconnected, From simply opens empty.

The To list is grouped by how well the types fitCopy Anchor Link

Once From is chosen, the To list groups every field under one of four headings, each with its own icon:

• Best match: the same kind of field on both sides.
• Compatible: a safe conversion, for example anything into a memo field.
• Works with limits: the copy runs, and values that don't fit are skipped and flagged, for example a value that matches no pick-list choice.
• Not verified: Nuix Discover may refuse the value, for example text into a date field. Try it on one document first.

Nothing is hidden. Every field in the case is in one of those groups, including the ones we cannot vouch for, and the source field is excluded from its own destination list.

Under the To picker, one line says how the pair reads, with a Why? you can hover for the detail.

Splitting one value into severalCopy Anchor Link

Split each value on a delimiter appears under the two pickers once both are chosen, and only when the From field is a memo. Type any separator (for example ;), and a value like smith@example.com; jones@example.com becomes two separate values in the destination instead of one blob.

While you type, a small Preview shows a real value from your selection and the entries it would become, so a separator that does not actually appear in your data tells you so immediately instead of after the run.

Splitting needs a To field that can hold several values. When the destination you chose can only hold one, the option is not offered at all: a single line explains why instead.

Step 2: OptionsCopy Anchor Link

• Copy or move: a dropdown with two choices. Copy leaves the source values in place; Move clears the source field after each successful copy. Whichever you pick, its consequence stays written under the dropdown.
• If the destination already has a value: the same shape. Skip the document (it's left untouched and flagged in the results) or Overwrite it.
• When the destination is a pick list, the value-matching table is part of this step too (see below).

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.

Matching values to pick-list choicesCopy Anchor Link

When the To field is a pick list, Claira lists every distinct value found in your selection's source field, with the number of documents carrying it. Values that exactly match a destination choice are paired automatically (marked Auto). Each remaining value is left at No match: skip the document until you decide what it should be:

• Pair it with a choice: the value migrates.
• Skip this value: that one value is dropped and the document's other values still migrate. On a Move, those documents keep their source field: a value you left behind is never deleted, and the result flags the document so you can see the source wasn't cleared.
• Leave it unmatched: every document carrying that value is skipped and flagged, so nothing is written from a value you haven't accounted for.

Several source values can point at the same destination choice (that's the usual way to consolidate spellings like "Conf" and "Confidential") and the choice is written once per document.

The counter above the table always shows how many values are matched, skipped, and still unmatched, and the confirmation dialog repeats it before anything is written.

New choices can't be created from here: a pick list's choices are managed in Nuix Discover's administration. Add any missing choice there first, then use Reload values to pick it up.

For very large selections Claira reads as much of your selection as it can and lists what it finds there, most common first; a note above the table tells you how many documents were read and when the list is partial. Values that aren't listed still migrate whenever they exactly match a destination choice, and are skipped and flagged when they don't.

Step 3: ReviewCopy Anchor Link

Claira reads your selected documents without changing anything and shows what would happen: how many will migrate, how many will be skipped and why. You don't have to ask for it. The review runs on its own a moment after you change a setting, and if you change something while it is running, the earlier answer is abandoned rather than allowed to land late.

When you change a setting, the numbers you were just reading are kept on screen, greyed out and marked "Out of date", with a line saying so. They are not deleted out from under you. Check again refreshes them, and is also how you retry if the check could not finish.

Step 4: Try on one documentCopy Anchor Link

Optional for every pair of field types, and strongly suggested for anything under Not verified.

Before you press it, the step says plainly what the button does: it writes to one real document in Nuix Discover, and you can undo it. Claira picks a document at random from the ones that have a source value, performs the real write, and 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.

The result then stays on screen as a banner naming the document by its Document ID, with two buttons:

• Undo test puts the document back the way it was.
• Keep change accepts it and moves on.

That banner does not go away when you change something else. This is the important part: whatever you adjust afterwards, the document you wrote to is still named, and its Undo is still there. A second test waits until you have chosen one or the other. If you keep the change and then start the migration, the confirmation reminds you which document is already changed and carries on.

Note that Nuix Discover's own coding history still records the brief change, and that a date field is restored to its previous calendar date: Discover only accepts a date on write, so any time of day the old value carried is not restored.

Starting the migrationCopy Anchor Link

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.

While a migration is running, the four steps lock: they collapse to read-only and say which migration is running, so the run cannot change under itself. They unlock when it finishes.

When the run finishes, the button becomes Start another migration. Your fields and options are kept exactly as they were, and Claira asks for a fresh review before it will run again, so a second migration can never start from the first one's numbers.

The migration IDCopy Anchor Link

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 historyCopy Anchor Link

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.

Search by migration ID, by person or by field name in the box at the top. The filter icon beside it narrows the list by:

• Status, several at once.
• Date, as a rolling window (last 7, 30 or 90 days).
• Field, matching migrations where that field was on either side.
• Run by, so you can see just your own runs or a colleague's.

A count on the icon says how many filters are on, and Clear filters removes them all. When your filters match nothing, the list says so, rather than telling you the case has no migrations. If the history itself can't be loaded, you get a message and a Try again button instead of an empty list.

Good to knowCopy Anchor Link

• A migration is not reversible once it runs (only the one-document test can be undone). Use the review, the one-document test, and the skip option to be confident before you start.
• Values going into a pick list migrate when they exactly match one of the destination's choices, or when you pair them in the matching table; anything left unmatched is skipped and flagged.
• Long values are shortened to their first few lines in the test result, the matching table and the migration history. Show more displays the whole value, and Show less folds it away again. This only changes what you see: nothing is cut from what is written.
• 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.