Coming from Vistaly
Import
The closest thing to UPG in the market: OST-native, near 1:1 entity mapping.
The structural finding
Vistaly is built around the Opportunity Solution Tree. Every core entity (Outcome, Opportunity, Solution, Experiment) maps directly to a UPG type with HIGH confidence. No inference required. Vistaly is a UPG subset.
What UPG adds
The full product context Vistaly lacks: JTBD, PainPoint, Persona depth, Hypothesis, Learning, Competitor, and the entire engineering, GTM, and business model layers.
Typed relationships beyond the OST: your Vistaly tree becomes the anchor of a 360° product graph, not an isolated strategy artefact.
Portability: your OST becomes a git-tracked .upg file you own, not data locked in a SaaS platform.
Schema mapping
The key edge
The single most important semantic relationship this integration enables.
Defined in the UPG specification
Sample import
A typical continuous discovery tree: Outcome → Opportunity → Solution
Roundtrip
Import OST cards → enrich with research evidence and experiment results → push enriched descriptions back to Vistaly via API.
- ·Opportunity descriptions enriched with linked research evidence
- ·Experiment results written back to solution cards
- ·Key Result current values synced from connected metrics
How to import your Vistaly data
The Vistaly adapter is built and tested. A one-command import via the UPG CLI is in development:
This will fetch your Vistaly data, map entity types automatically, and write everything to your graph. Today you can use the Markdown import or the adapter directly in code.
▸ For developers: use the adapter directly
Get started
The Vistaly adapter ships in @unified-product-graph/adapters. Install it, then run the import command.
$ npm install -g unified-product-graph
# then import
$ upg import --from notion