Where your documents went
The conversion is not a lift-and-shift. When you open the document library after go-live, it will look reorganised, not merely relocated — and the instinctive reaction to that is “something was lost.” This page exists so you can check that instinct against what the migration actually does, rather than against a guess.
The three-level model
Section titled “The three-level model”Interact organised documents under a section, with up to two further levels of grouping beneath it, however your team’s own categories were labelled. ClearVue always uses exactly three fixed levels — Level 1, Level 2 and Level 3 — visible today in Library Search and the Documents filters (see Find the document you need).
A document attaches at the deepest level it reached in Interact. If a document only ever had a top-level section and one level of grouping beneath it, it lands at Level 2 in ClearVue, not Level 3 — there is no third level to invent one for.
Two things happen automatically during the mapping, and both are corrections rather than losses:
- Categories are matched by name, not by Interact’s internal codes. If the same category name was reachable under two different internal codes in Interact, it becomes one Level in ClearVue rather than two. That is a deliberate de-duplication, not a merge error.
- A category with no documents in it does not appear. Only categories that actually have content attached come across.
The MPIEncyclopedia language collapse
Section titled “The MPIEncyclopedia language collapse”One section of Interact’s library held English and Spanish versions of the same reference content as two separate document records, told apart by an internal marker rather than by anything in the filename. During migration, each such pair becomes one ClearVue document with both languages attached to it, rather than two separately findable entries.
If you used to find an English entry and a Spanish entry side by side in that section, you will now find one entry with both languages inside it. That is intentional, and it is the single biggest visible reorganisation in the conversion — worth saying explicitly to anyone who searches for the pair they remember and finds only one result.
Outside that section, an English/Spanish pair is recognised by a naming pattern on the file itself (a Spanish-language file is marked at the source). Where a Spanish file has no matching English counterpart, it stays as its own, standalone document — the migration only merges a pair when both halves genuinely exist; it never assumes one from the other.
Open: Confirm with an Interact-side reviewer that the MPIEncyclopedia section is described accurately here — specifically, whether “one entry per language” is really how MPI staff experienced it in Interact, or whether the two languages were already presented together in some other way. The written spec is confident about the data; it is not a substitute for how the screen looked.
What did not convert
Section titled “What did not convert”| Did not convert | What happens instead |
|---|---|
| Document owner | Left blank on every migrated document. Interact user accounts were never part of the migration, so there is no source to assign an owner from. Owners are assigned in ClearVue after load, as a deliberate post-migration task — not an oversight. |
| Read/acknowledgment history | Not migrated — there are no user accounts to attach it to. Every migrated document starts acknowledgment tracking from zero on the day it loads; see What changed from Interact. |
| Approval routing history | Not migrated. A migrated document carries an approved-on date where one could be established, and nothing about who approved it or in what order. |
| Tags | None migrate — Interact’s content had nothing that survives the conversion as a tag. Add them going forward if useful. |
| A review schedule | Not set automatically. Until your organisation sets a review cycle for a category, documents in it show no “next review due” date — that is a configuration step, not a data gap. |
| Per-document exceptions (e.g. a one-off override to a category’s default watermark) | Not modelled in Interact, so nothing to carry across. |
Document files arrive in a second step
Section titled “Document files arrive in a second step”The document records — number, title, classification, dates — load first. The files themselves (the actual PDFs and other attachments) load as a separate, later step against documents that already exist. If you open a newly migrated document and its file has not appeared yet, that is why — check back, or ask your administrator whether the file step has completed.
Open: Confirm the file step will have completed for all of MPI’s documents by go-live, or establish which documents (if any) may legitimately arrive without their file attached for a period, so the answer here can be definite rather than “usually.”
A few things you will see that are not errors
Section titled “A few things you will see that are not errors”- Some documents carry a generic, system-generated title (for example, a title that just names the file and a load date) rather than a human-written one. That reflects what was actually in Interact for that record — the migration reports it, but does not invent a better title.
- A document with no clear place in your facility structure lands visible to everyone in the tenant by default, rather than being hidden. Interact has no equivalent to ClearVue’s facility-level visibility model, so a document the migration cannot place narrowly is placed company-wide rather than guessed into the wrong facility. An administrator reviews and can narrow this during the import, before it is approved.
- A document you remember filing in several places in Interact now shows up once, carrying several classifications, instead of as several separate documents. Interact could only express “filed in more than one place” by duplicating the whole record; ClearVue can attach one document to more than one Level directly, so the migration consolidates those duplicates back into a single document rather than keeping the duplication. If you compare raw document counts between the two systems, this consolidation is the most likely reason ClearVue’s count is lower — not missing content.
- A small number of Interact records never become documents at all — specifically, temporary files that office software creates automatically (for example, a Microsoft Word autosave/lock file) and that were never meant to be a controlled document in the first place. These are filtered out during migration rather than loaded and later cleaned up.
Document numbers
Section titled “Document numbers”In the ordinary case, the number you already search by in Interact is the same number you will find the document under in ClearVue — the migration carries it across unchanged rather than minting a new one.
Open: Confirm this holds for every category of MPI document, not just the common case. The written conversion design leaves open how a document with no usable number in Interact’s export should be numbered in ClearVue, and that decision was not settled as of this page being written. If MPI has any document categories you suspect might hit that edge, flag them for the reviewer before go-live rather than after.