Legacy Contract Migration demo
Old contracts loaded into the new CLM with every field measured, renewals found first. 1:31
What the demo shows
Inventories, dedupes and extracts legacy contract data to load a clean CLM repository
The file inventory folds into stacks, one per contract family: the parent agreement with its amendments, SOWs and duplicate copies fanned behind it, the golden copy marked and the extracted fields on the face. A rail runs Found → Deduplicated → Linked → Extracted → Sampled → Loaded, with the count at each step. A sampling agent measures each field against a person's spot-check of 200 files and holds back any field under its threshold; the migration lead approves each batch with a reason code, and every batch reconciles and rolls back in one step.
Transcript
- Legacy Contract Migration moves a legal team's old contracts into a new CLM.
- One published migration began with 98,000 files, 60,000 belonged.
- Here, 18,406 files became 6,212 contract families.
- Brackwater's stack assigned golden copy for amendments, three duplicates.
- Every field cites its page.
- Amendment 2 moved the expiry to May 2027.
- A sampling agent scores each field against a person's check of 200 files.
- Counterparty name passes at 98.7%, governing law at 91% is held.
- Dana Ortiz approves batch 1, 2,000 families with a reason code.
- It loads, reconciles to the last document, and can roll back.
- Every merge, link, and approval is cited, signed, and logged.
- 37 forgotten renewals surfaced before go-live.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.