Opik gives you several ways to export the data you’ve logged — pick the one that fits your workflow.
The Python and TypeScript SDKs let you search and export traces, spans, and threads programmatically.
All search methods accept a filter_string / filterString using the Opik Query Language (OQL):
AND (OR is not supported)"2024-01-01T00:00:00Z")metadata.model, feedback_scores.accuracyCommon filter examples:
The full list of supported columns per entity type is documented below.
Use the /traces and /spans endpoints to export data. Both endpoints are paginated.
The REST API filter parameter has limited flexibility as it was designed for use with the Opik UI.
For complex queries, use the SDK instead.
Select the traces or spans you want to export in the Opik dashboard and click Export CSV in the Actions dropdown.

The UI exports up to 100 traces or spans at a time. For larger exports use the SDK or CLI.
The opik export and opik import commands let you export traces, spans, datasets, prompts, and experiments to local JSON or CSV files, and import them back — useful for migrations, backups, and cross-environment syncs.
TYPE is one of: all, dataset, project, experiment, prompt
Imports are automatically resumable — if interrupted, re-run the same command and it picks up where it left off using a local migration_manifest.db.
See the CLI help (opik export --help / opik import --help) for all options and troubleshooting.