How ready are we to actually leave?
"We could migrate if we had to" is a comfortable thing to believe and an expensive thing to assume. This assessment turns it into a number. Pick the vendor, answer six honest questions, and it scores your readiness against that product's own lock-in profile, then hands back a prioritized plan that puts your biggest exposures first. 72 products covered.
Illustrative self-assessment based on the OffVendor Lock-in Index, not a statement about any specific contract or product version. It's a planning aid to focus your exit prep, confirm specifics with the vendor and your own architecture.
Why readiness has to be measured per vendor
Exit readiness isn't a single trait, it's your preparedness relative to a specific product's stickiness. The Lock-in Index scores every product on five dimensions: licensing power, data portability, proprietary surface, ecosystem and skills, and exit-path maturity. A gap on the dimension where your vendor is stickiest is a bigger risk than the same gap on one where it's weak. That's why this tool weights your answers by the vendor's profile instead of treating every gap equally, an untested migration path is a footnote for a product with a drop-in fork and a five-alarm risk for one without.
The six questions, and why each one predicts a stall
- Data export (D) — the migrations that fail late fail here: someone assumed the data would come out and it didn't. Prove it early with the Data Portability Checker.
- Proprietary surface (P) — the vendor-only code and config you'd re-express is usually the true long pole, and the easiest to underestimate.
- Skills (E) — ecosystem lock-in is a people problem; a target platform nobody owns is a project that won't start.
- Migration path (X) — an untested tool is a hope, not a plan. A small pilot converts unknowns into scope.
- Contract clock (L) — the renewal and its notice window set your real deadline; miss it and you've re-upped by default. Scan the terms with Renewal Redline.
- Target & budget — intent without an owner, a number, and a date is how "we could leave" stays theoretical forever.
Frequently asked
How is the score calculated?
You answer six preparedness questions (data export, proprietary surface, skills, migration path, contract clock, target). The tool combines your answers into a readiness score and then prioritizes your gaps by how sticky each dimension is for the specific vendor you picked, using the OffVendor Lock-in Index.
Why does the vendor choice change my plan?
Because the same gap matters more for a stickier vendor. Not having tested a migration path is a bigger risk leaving Oracle (deep proprietary surface) than leaving a product with a mature drop-in fork. The action list reorders accordingly.
Is my input saved anywhere?
No. The assessment runs in your browser and nothing is uploaded or stored. Reload the page and it resets.
What do I do with the result?
Work the action list top-down, the highest-priority items are your biggest exposure. Then price the move with the Switching Cost Calculator and test the timeline with the Renewal Planner.