Seller field guide · 3 min read
Can you license company-owned Asana project history?
A permitted Asana collection should explain how work was planned, changed and completed, not simply list task names. Begin with internal projects your company owns and verify what the selected export contains. Client deliverables and project access require separate rights decisions.
Project exports and organization exports differ
Asana documents project exports in JSON or CSV, along with exports of search views and My Tasks. It separately documents organization-wide exports for eligible plans and administrators.
Choose the smallest permitted project scope that can answer a buyer’s evaluation question. Compare the output with an actual task that has important discussion and attachments. Do not assume a convenient CSV contains every element available through a different export route.
Source notes: Asana: project importing and exporting · Asana: privacy, security and organization exports
Identify the decisions behind project delivery
A useful sample might show a request, the team’s estimate, a change in scope, the resulting handoff and the final acceptance decision. Distinguish genuine commentary from recurring task templates and automatic status updates. Repetition can inflate record count without adding new reasoning.
For agency or client work, separate the firm’s internal operating process from commissioned deliverables and client feedback. An internal-only project may still quote confidential client requests. Review task descriptions and discussions rather than relying entirely on project visibility settings.
Choose a defensible evaluation scope
This is our suggested scoping framework, not a statement that a buyer accepts every record below. Review contractual rights and the intended use before preparing a sample. Technical access to a record does not establish permission to license it.
| Record or context | What to evaluate | Boundary to keep |
|---|---|---|
| Internal delivery task | Request, ownership and outcome | Exclude client deliverables and confidential instructions |
| Discussion or scope-change note | Why the team changed its plan | Check whether the selected format preserves it |
| Linked asset or attachment | Whether the task needs it for context | Review separately and keep restricted files out |
Keep completion and dependency meanings explicit
A completed task can mean a deliverable shipped, a review finished or a duplicate was closed. Explain your team’s conventions in a field guide. Preserve allowed task relationships when they are necessary to understand the sequence, and mark missing context.
Ask the buyer whether it needs project planning, execution or retrospective analysis. A sample focused on one of these is easier to evaluate than a broad export mixing all three. Do not infer a price from the number of tasks or the subscription tier.
Illustrative scenario · fictional company
Asana: a fictional scoping example
A fictional creative agency evaluates an internal Asana production-planning project. It excludes client deliverables, brand assets and shared client projects. The sample shows the agency’s own staffing decision and internal review handoff. A task whose description quotes confidential client feedback is removed even though the project is private. The team compares exported tasks with the source and labels discussion or attachment gaps before presenting the scope.
When to pause or narrow the scope
Client work and customer files are excluded from this starting scope. Assess company-owned internal records separately from personnel, health, privileged or NDA-restricted material.
- Most useful content is client-owned delivery material.
- Tasks are repetitive templates without meaningful decisions or outcomes.
- The available export omits the context needed for the intended evaluation.
Your preparation checklist
- Select internal projects and identify their owner.
- Test JSON or CSV output on a representative permitted task.
- Review descriptions, discussions and attachments separately.
- Define completion, cancellation and dependency conventions.
- Give the buyer a scoped sample with an exclusion manifest.
Start with a description of the records. The quote form does not ask you to upload a dataset.
Discuss your dataSources and further reading
- Asana: project importing and exporting · Checked October 26, 2026
- Asana: privacy, security and organization exports · Checked October 26, 2026
This is general information, not legal advice or confirmation that a buyer will accept your records. Published buyer ranges describe their programs, not an offer for your dataset. Buyers may pay QuoteMyData when a deal closes; see how we are paid.
