The operating decision
Plan for analytical continuity, not just file export.
Build the workflow
| Step | Action |
|---|---|
| 1 | Inventory prompts, groups, projects, users, brands, competitors, and data objects |
| 2 | Export raw and derived data with definitions and timestamps |
| 3 | Recreate the same core panel and market scope in the new platform |
| 4 | Run both systems long enough to compare success rates and metric behavior |
| 5 | Mark the migration break and avoid splicing incompatible totals into one line |
Example handoff
Two tools may both report 'visibility' while using different denominators or ranking weights. A CSV migration cannot make those values comparable without a reconciliation layer.
Evidence, limits, and UnderAI's role in AI search platform migration
Keep these fields with the decision:
- trigger
- source identifier
- evidence link
- owner
- approval
- action
- status
- timestamp
- retry
- resolution
Exports, APIs, retention, and deletion behavior are vendor-specific. Confirm them before contract termination.
UnderAI public materials do not verify a public export/API contract, so migration requirements must be reviewed directly during procurement.