Coming from Productboard
Import
Productboard captures features and insights. UPG adds the formal structure that makes them queryable and portable.
The structural finding
Productboard has strong alignment at the feature/discovery layer: Feature, Objective, Key Result, Insight, and User Segment all map with HIGH or MEDIUM confidence. The gap is the validation layer (no Hypothesis, no Experiment, no Learning entity). And no portability: your data stays in Productboard's cloud.
What UPG adds
The validation layer: hypotheses, experiments, and learnings that close the loop between insight and decision.
Portability: a .upg file you git-track, diff between quarters, and take anywhere.
AI-native querying: 89% fewer tokens than Productboard's REST API for agent-driven tasks.
Schema mapping
The key edge
The single most important semantic relationship this integration enables.
Defined in the UPG specification
Sample import
Productboard feature hierarchy: Objective → Feature → Notes
Roundtrip
Import features and insights → enrich with hypotheses and experiments in UPG → push validation evidence back to Productboard via API.
- ·Hypothesis and experiment nodes linked back to features as validation evidence
- ·Learning summaries written back to feature notes
- ·Outcome connections surfaced in Productboard objective descriptions
How to import your Productboard data
The Productboard adapter is built and tested. A one-command import via the UPG CLI is in development:
This will fetch your Productboard 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 Productboard 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