Your free Vera AI trial opens the benchmarking database, the negotiation guides, and the tools this demo walks through, on your own agreements.
Start your free Vera AI trialMost estates do not live in a system. They live in a spreadsheet someone has kept for years.
By the end of this lesson you will know what actually migrates and what does not. The documents come across as files, and your register, that master spreadsheet of vendors, values, and dates, comes across as rows. Nothing is retyped, and terms are read again from the paper itself.
One honest note before the studio. If you are carrying only a handful of contracts, this is the wrong door. Upload them, or drop them on the Archive, and skip the guided run entirely.
The studio is built for the other case. Hundreds to thousands of agreements, plus the register that lists them. It runs in stages, it holds everything out of sight until you sign off, and it writes nothing to your live workspace until then.
This lesson is the heart of the run: teaching the platform what your columns mean. You map each one to the estate model. The column headed Contract Value is read as the whole term and divided to a year, so if yours is already annual, say so, or every multi-year deal inflates.
This lesson covers licensing data, what you own and run. It arrives three ways into one place: a live push from an API, a sync from your SAM tool, or a CSV when a connection is not approved. However it comes, it reconciles entitled against deployed, per vendor.
The studio scrolls back to that same note, a useful reminder. Volume is what earns this guided path. For everything smaller, the faster doors already covered are the right ones.
One thing the studio does that no spreadsheet can. It reads the documents behind the register and reconciles them: duplicates by content, vendors that are the same company under different legal names, and agreements that supersede each other.
By the end of this lesson you will not trust a migration until the numbers agree. Before anything is written, the dry run states how many contracts it would create, how many it would update, and how many rows it cannot use. You reconcile before you sign off.
A finished migration lands here, on data health. This is the scoreboard. Migrated is not a feeling; it is the share of your data checks that pass, and it recalculates on every load.
The top of the screen names what is already connected and feeding the score. That is your foundation, the sources the rest of the plan builds on.
Below it, a plan you can act on. Each open gap names the feature it would unlock, and the whole list is ranked so the biggest payoff sits at the top.
Two questions. One, why divide a total-value column by the term? Two, what must the dry run show first?
If either is fuzzy, replay it. Now you: run the survey on your export. Twenty minutes. Next, Course 11, Connectors and integrations.