Comparison
Who Owns Your PM Data? Export and Lock-In Compared 2026
Every PM vendor will tell you your data is yours. What differs is whether you can get it out before renewal — verified export ceilings for Asana, ClickUp, monday.com and Smartsheet, plus the exit cost nobody quotes.
AsanaClickUpmonday.comSmartsheetNotionWrikeJira
Every project management vendor’s security page contains some version of the sentence “your data belongs to you.” None of them are lying. But “you own your data” and “you can get your data out in a usable form before the contract renews” are two different claims, and only the second one shows up on a procurement risk register.
This page answers the second question. It compares six tools on what you can export, at what size, in what format, on which tier, and — the part vendors leave off the pricing page — what the exit actually costs in engineering time.
TL;DR
- The export ceiling is a tier feature, not a technical accident. Asana’s complete organization export in JSON is restricted to Service Accounts of Enterprise organizations, per Asana’s own API documentation. A Starter or Advanced customer cannot use the only complete export that exists.
- Asana publishes several ceilings that are never on the pricing page: 140,000 rows for a CSV export from a project, 5,000 rows for a CSV export from a search result, and 500 rows for the live Google Sheets sync. The 500-row sync ceiling is the one that surprises teams, because the sync is the feature people build reports on.
- ClickUp’s API is available on every plan with rate limits of 100 requests per minute per token on Free and the lower paid tiers, 1,000 on Business Plus and 10,000 on Enterprise — but user and guest management endpoints are Enterprise-only, so provisioning automation is a tier purchase.
- monday.com’s Board Export API is Enterprise-only and API version 2026-10+, exports one board at a time, and the response contract is explicitly unstable: “the same board can return
ExportFiletoday andExportAsyncJobtomorrow.” Its daily call limit is 200 on Free, rising to 25,000 on Enterprise. - The cheapest lock-in defence is not a better contract. It is a monthly export into storage you control, sized to the tier you already pay for — and, crucially, sized to the export ceiling, which most teams discover after they have passed it.
- If you are choosing today and exit risk matters: pick the tool whose export path is documented and available on the tier you are buying (Smartsheet, ClickUp), not the one whose complete export requires a sales-negotiated tier (Asana, monday.com Enterprise).
What “your data” actually means in a PM tool
Before comparing ceilings, separate four things that get bundled into the word “data”:
- Task content — titles, descriptions, assignees, dates, comments. Almost everyone can export this.
- Structure — the dependency graph, custom field definitions, status workflows, automation rules. Usually partially exportable and rarely re-importable.
- Attachments — files. Frequently the largest volume and the slowest to extract.
- History — who changed what, when. Typically the first thing lost in any migration, and per Asana’s own guidance, audit log retention runs 90 days unless you export to a SIEM.
A migration that preserves point 1 and loses points 2 and 3 is the normal outcome. That is not a vendor failure; it is the reason exit cost should be budgeted as engineering time rather than assumed to be zero.
Verified pricing and export path, per tool
Prices as published on each vendor’s own page, per user per month, billed yearly.
| Tool | Entry paid tier | Per seat | Complete/org export available on | Export mechanism |
|---|---|---|---|---|
| Asana | Starter | $10.99 (monthly $13.49) | Enterprise only (Service Account required) | JSON organization export via API |
| Asana | Advanced | $24.99 (monthly $30.49) | Enterprise only | Same |
| ClickUp | Core | $9 (regular $12) | All plans (public API) | API, per-space/per-list pagination |
| ClickUp | Business | $17 (regular $25) | All plans | Same; user/guest endpoints Enterprise-only |
| monday.com | Basic | $9 (3-seat minimum) | Enterprise only for board export API | GraphQL board export, one board per call |
| monday.com | Pro | $19 (3-seat minimum) | Enterprise only for the export API | Same |
| Smartsheet | Pro | $9 (monthly $12) | Per-sheet exports on all tiers | Sheet → Excel/CSV/PDF; API on Business+ |
| Smartsheet | Business | $19 (monthly $24) | Per-sheet exports on all tiers | Same |
| Notion | Plus | $10 (monthly $12) | All tiers | Markdown/HTML/CSV workspace export |
| Wrike | Team | $10 (2–15 users) | All tiers | Export per folder/project |
| Jira | Standard | $7.91 | All tiers | CSV per filter; full Jira Cloud backup is admin-only and instance-level |
Verified against the official pricing pages of Asana, ClickUp, monday.com, Smartsheet, Notion, Wrike and Atlassian on 2026-11-05.
Two observations that fall out of the table.
The price of the tier is not the price of exit. Asana’s cheapest path to a complete organization export is Enterprise, which is quoted. A 20-person team on Advanced at $24.99 has no published route to a full JSON export of its own workspace, at any price, without negotiating a tier it does not otherwise want. That is the strongest lock-in fact on this page and it comes from the vendor’s own API reference, not from a competitor’s marketing.
monday.com’s export ceiling is a different kind. Its published API is generous at the top and thin at the bottom: 200 calls a day on Free, 1,000 on Basic and Standard, 10,000 on Pro, 25,000 on Enterprise. A team on Standard with 200 boards that wants a nightly copy of everything is doing 200 board-exports a night against a 1,000-call budget shared with every integration and automation in the account. Mathematically possible, operationally fragile.
Asana: the export ceiling is a tier, not a file
Asana’s position is the most documented and the most misunderstood, so it is worth spelling out with the vendor’s own words.
The complete export exists. Asana’s API provides organization_exports, and the reference describes it as “an organization_export object represents a request to export the complete data of an organization in JSON format.” The workflow is asynchronous — create the request, poll until state reads finished, then download from download_url, which the documentation warns “may only be valid for 1 hour from the time of retrieval.” (Asana developer docs — Create an organization export request)
And then the restriction, in the same paragraph: “These endpoints are only available to Service Accounts of an Enterprise organization.” Service accounts are themselves an Enterprise capability. So the export that a departing customer would want — everything, in JSON — is behind the tier the customer was trying to leave behind.
Below Enterprise, what you have is per-project and per-search CSV, with ceilings that a community-maintained limitations index has catalogued because Asana’s own help centre does not put them in one place:
- 140,000 rows for a CSV export from a project
- 5,000 rows for a CSV export from a search result (raised from 2,000 in Q4 2024)
- 500 rows for the live Google Sheets sync
- 2,000 rows and 2,000 columns for a CSV import back in
Source: Asana Forum — List of technical and data limitations in Asana, a community thread maintained by a forum leader and last updated February 2026, with each item linked to its own evidence. Read that as a user-compiled index, not as a vendor statement — but the 500-row sync figure is corroborated independently below.
What users actually hit
The forum record here is unusually specific, and it is the reason this page exists. Paying customers describe the same pattern across nine years: they built a process on exports, and the ceiling moved underneath them.
Feb 2024 — the 250-row live sync. A user reported the limit directly: “the live updating spreadsheet function that pairs between Asana and Google sheets… at my job we have 100s of tasks that I would like to be able to have a live export for and currently it is limited to 250 for live updates.” (Asana Forum — “The live Google Sheet export from Asana - limited to 250 rows of data”)
Two years later, in a September 2026 thread, a regular forum contributor states the shipped limit as 500 rows per project for the native Google Sheets sync, and notes that sync “is not natively available for Excel.” (Asana Forum — “Selecting specific project fields to export”) Direction of travel is upward, but the ceiling still arrives well before any project a mid-size team would call big.
Jul 2024 — the export that silently omits what matters most. A user exported a workspace and found logged time missing entirely: “I clicked export and a list of projects was downloaded but none of the time logged was included. That is the most important aspect of the export.” (Asana Forum — “Current Workspace Export Missing Time Logged to Project/Tasks”)
2017–2018 — the truncation thread, and the reason it still matters. This is a 47-post thread that started when a customer discovered a CSV export was short by hundreds of tasks. Asana support’s answer at the time: “CSV exports are truncated at 3000 lines as the export limit. This is why you are seeing tasks missing.” When another user reported the ceiling had dropped to 2,000 rows, they wrote: “The workaround is very annoying and we had a good process going using the .csv that I’m afraid we have to revise now.” A third user put the procurement argument better than any analyst could: “truncating advanced search and project results is absolutely miserable. Why would you assume everyone using Asana can write some code/software if we want to make a backup or archive of our projects? … You can’t bury it behind code.” (Asana Forum — “Don’t truncate CSV project exports”)
And the exit itself, from a customer already leaving. “The company I work for has decided to completely abandon the asana product… we want to export the data and close and delete the account (for another few dozen people). How to do it? By the way, the fact that I am asking about this procedure on the forum only confirmed the right decision to leave this platform.” (Asana Forum — “we decided to completely abandon the asana product, how to do it?”)
A note on what these threads do and do not prove. They are dated — some are eight years old — and Asana has raised several ceilings in that period. They are not evidence that Asana’s export is broken in 2026. They are evidence of a pattern: the export ceiling is a moving target set by vendor performance decisions, communicated after the fact to customers who had already built on it. Plan around the pattern, not around any single number.
ClickUp: the ceiling is rate, not format
ClickUp’s position is structurally different and, for a team planning to leave, better.
Everything is available through the public API on every plan. ClickUp’s documentation states plainly that “Our Public API is available on all ClickUp Plans,” with some endpoints restricted by tier. Rate limits are per token:
| Plan | Requests per minute per token |
|---|---|
| Free Forever | 100 |
| Unlimited | 100 |
| Business | 100 |
| Business Plus | 1,000 |
| Enterprise / Enterprise Plus | 10,000 |
Source: ClickUp developer docs — Rate limits, updated 2026-09-17.
The tier gates that do exist are about people, not data. From ClickUp’s plan-availability page: the user and guest management endpoints — invite, get, edit, remove, and every guest-association call — are Enterprise-only. So is the admin_can_manage parameter on spaces. (ClickUp developer docs — API availability by plan, updated 2026-04-13.)
Practical translation: on Business at $17, you can read and write every task, list, doc and time entry you own at 100 requests per minute. You cannot programmatically manage seats or guests unless you are on Enterprise. For data portability that is fine. 100 requests a minute is 144,000 a day, and ClickUp’s API paginates — a 20,000-task workspace is a few hours of unattended script, not a negotiation.
Docs are the weak point. ClickUp’s own import/export limitation page lists what survives a Markdown round-trip: headings, lists, code blocks and quotes yes; toggles, checklists, banners, inline elements, views, embeds (including embedded tasks and docs), synced content, columns, sticky table of contents and text colours are all “No”; tables survive “but lose formatting.” (ClickUp developer docs — Docs API limitation, updated 2025-09-04.)
That is the honest ClickUp lock-in: tasks are portable, wikis are not. If your knowledge lives in ClickUp Docs, price the reformatting as real work before you sign.
monday.com: Enterprise-only board export, unstable contract
monday.com documents its export path in detail, and the documentation itself makes the case against relying on it.
Two restrictions in the first paragraph: the board export is “Only available in API versions 2026-10 and later, on Enterprise plans.” And it exports one board at a time — there is no organization-level export described. (monday.com developer docs — Board Export, updated 2026-11-04.)
The contract is explicitly unstable. The vendor’s own words: “Which branch you get is not part of the contract. The server picks ExportFile or ExportAsyncJob based on board size and current load, and the thresholds can change without notice — the same board can return ExportFile today and ExportAsyncJob tomorrow. Always select both branches.”
That is a documentation note to developers, but it is a procurement fact too: any backup pipeline you build against monday.com must handle both the synchronous and asynchronous shape on every call, forever, without warning.
And it competes with everything else on the call budget. monday.com’s daily limit covers personal tokens, private apps and public apps — and, per its own docs, “calls made through the hosted Platform MCP server also count toward this daily limit”:
| Tier | Daily call limit (resets midnight UTC) |
|---|---|
| Free | 200 |
| Standard / Basic | 1,000 |
| Pro / Trial | 10,000 |
| Enterprise | 25,000 |
Source: monday.com developer docs — Rate limits, updated 2026-10-28. The limit can be raised by purchasing an API add-on.
Here is the arithmetic that matters. A 40-person company on Pro at $19/seat — $760 a month — with 150 active boards and 30 integrations, a few automations calling the API, plus a nightly backup. A full nightly board copy is 150 calls, times 30 days is 4,500 calls a month, against a shared budget that every automation is also drawing on. It fits at Pro. It does not fit comfortably at Standard’s 1,000 a day once the MCP server and the integrations are in the count. The backup plan is a tier decision you make three years before you need the backup.
Smartsheet, Notion, Wrike, Jira: the boring, workable middle
The rest of the field is unremarkable in a good way.
Smartsheet exports sheets to Excel, CSV and PDF on every tier, which means the smallest possible plan can still get its data out in a format somebody else’s tool can read. The API is available from Business upward for automation. An Excel export is not a database export — cross-sheet formulas, reports and workflow automations do not travel — but the rows do, and at $9 (Pro) or $19 (Business) per member/month the entry cost of a defensible exit plan is low.
Notion exports a workspace to Markdown and HTML with a CSV per database, on every tier. The result is faithful for text and lossy for relational structure: relations become links, formulas become values, and any database view logic is gone. For a team whose knowledge base is the asset, this is the best of the field; for a team whose plan is the asset, it is close to useless.
Wrike exports per folder and project, and its published tiers are Team $10 (2–15 users) and Business $25 (5–200 users), with Pinnacle and Apex quoted. Wrike’s data residency and export options improve at the top of the range, so a Wrike exit is easier from a lower tier than an Asana exit — but the same rule applies: per-folder exports do not preserve portfolio rollups.
Jira is the outlier because the low-level option exists: a full Jira Cloud backup is an admin-level instance operation, not a per-project export. Per-filter CSV is available to everyone. The practical lock-in is not extraction, it is workflow configuration — statuses, screens, permission schemes and automation rules are rebuilt by hand, and that rebuild is measured in weeks, not hours.
What exit actually costs, in hours
No vendor publishes this, so here is a working model with stated assumptions. Price the engineering at your own rate.
| Workspace size | Tasks | Attachments | Structure rewrite | Total engineering |
|---|---|---|---|---|
| 2–10 people, 1 year of use | ~3,000 | <5 GB | 3–5 custom fields, 1 workflow | 8–16 hours |
| 10–30 people, 2–3 years | ~20,000 | 20–80 GB | 10–20 fields, 3–6 workflows, automations | 40–80 hours |
| 30–100 people, 3+ years | 100,000+ | 200 GB+ | Portfolios, OKRs, permission schemes | 150–400 hours |
Assumptions, stated plainly: extraction is scripted rather than manual; attachments move at network speed; and the destination tool accepts CSV. Drop the “scripted” assumption and the 20,000-task case becomes months rather than weeks — which is exactly the situation the 2017 Asana thread was describing.
The line that matters for budgeting: the cost of exit is not paid at exit, it is paid every year you fail to keep the export pipeline running. A team that tests extraction once a quarter pays 4 hours a quarter. A team that has never tested it pays the full rebuild, at the worst possible moment — when they have already decided to leave and the renewal date is three weeks away.
Team-perspective judgement
Under 10 people. Do not build a pipeline; run the vendor’s native export on the first of every month and drop the file in storage you control. The whole exercise is under an hour a quarter. Choose whichever tool fits the work — see best PM software for small teams — and treat lock-in as a non-issue at that scale, because at 3,000 tasks you can rebuild in a fortnight.
10–40 people, considering Asana. Before you sign, get one thing in writing: what is on the roadmap for organization export below Enterprise, and can we get a trial of the Service Account export. If the answer is no and data portability is a board-level requirement, choose Advanced only if you accept per-project CSV with a 140,000-row ceiling as your recovery plan. This is the single highest-value question on this page.
10–40 people, considering monday.com. Budget Pro at $19/seat, not Standard, if you want a nightly backup. Standard’s 1,000 calls a day is shared with every integration and the MCP server. If the budget forces Standard, run the backup weekly against a rotating subset of boards rather than nightly against all of them.
Any size, heavy documentation in the tool. Assume Docs and wikis will not survive a migration in usable form. ClickUp loses toggles, checklists and embeds; Notion loses relations and formulas; Asana does not carry comments in every export path. Keep anything genuinely irreplaceable — contracts, policy, client deliverables — in storage outside the PM tool. The wiki you cannot export is the wiki you should not have built there.
Regulated or publicly-listed buyers. Ask for the audit log retention period and the export of it, not just the export of tasks. Asana retains audit logs for 90 days and expects longer retention to be handled through a SIEM; that is a compliance design constraint, not a bug, but it must appear in your evidence plan.
The checklist to run before renewal
- Get the row count. Every project, every board, every sheet. Compare it against the vendor’s published or documented ceiling.
- Export one full project in the format you would need on exit. Time it.
- Check what is missing — comments, time entries, attachments, custom field definitions, automation rules.
- Restore it somewhere you do not control. The restore is where migrations actually fail.
- Write down the ceiling you just measured and the tier it applies to, and put the date on it.
- Repeat at three months. Ceilings move, mostly upward, occasionally down.
Related reading on this site
- The overall ranking and pricing baseline: best project management software 2026 and the Asana vs ClickUp vs monday head-to-head.
- Pricing that drives the renewal decision: ClickUp plans explained, monday vs ClickUp vs Asana pricing, ClickUp vs monday vs Asana for enterprise.
- Metered costs that look like lock-in: Asana vs ClickUp vs monday AI features and the AI pricing and feature update tracker.
- Migration in practice: migrate from Asana to ClickUp, migrate from Trello to Asana, import data into Asana without losing fields.
- Single-tool depth: Asana review, ClickUp review, monday.com review, Smartsheet review, Notion review, Wrike review, Jira review.
- Release tracking that changes ceilings: Asana new features and pricing 2026, ClickUp pricing changes 2026, monday.com plans and pricing 2026.
How this content was prepared
Transparency note: This comparison draws on three sources. (1) Vendor primary sources, read on 2026-11-05 and linked at each claim: Asana’s API reference for organization exports, ClickUp’s rate-limit and API-availability documentation, monday.com’s Board Export and rate-limit documentation, and each vendor’s public pricing page. (2) Paying-customer evidence from vendor community forums, quoted inline with links and dates: four Asana Forum threads spanning 2017 to 2026, including one where an Asana support reply states the CSV truncation limit. Where a forum source is user-compiled rather than vendor-published — the limitations index — this page says so. (3) Editorial judgement about which export constraints actually affect teams, expressed as the exit-cost model and the team-size recommendations.
We have not independently tested these export paths. No vendor paid for or influenced the rankings, and we hold no paid seats on any platform described here as a benchmark. We have not run a full organization export on any of the six tools, and the hourly figures in the exit-cost table are a stated model with visible assumptions, not measurements. Where a vendor does not publish a number — Asana Enterprise, monday.com Enterprise — this page says the figure is quoted rather than substituting one. Export ceilings and plan boundaries change without notice; the dated verification blocks and linked vendor documentation are authoritative.
One thing we will say without hedging: a data portability plan that has never been tested is not a plan. Export one project this month and try to restore it. The result will tell you more about your renewal risk than any comparison, including this one.