Data ownership in PM: where does your data actually live?
Every project management vendor says "your data is yours." It is right there in the terms of service. But what does that actually mean? Can you read it without their app? Can you query it? Can you move it somewhere else without their permission? For most tools, the answer is no.
Data ownership in project management means you can access, read, query and move your project data independently of the software that created it. Not just "your data is stored on our servers." Real ownership means the data lives in a format you control, on infrastructure you control, and you can use it with any tool that understands that format.
TL;DR: Most PM tools store your data in a proprietary cloud database you can never touch. Eigenfocus stores everything in a single SQLite file you can open, query and move with standard tools. Data ownership is not about where the server is. It is about whether you can actually read your own data.
What does "your data is yours" actually mean?
When a cloud PM tool says your data is yours, they usually mean one thing: you can export it. Typically as a CSV or a JSON dump.
That sounds reasonable until you think about what you lose. A CSV export of your issues does not include the relationships between them. It does not include your custom field definitions, your view configurations or your time tracking entries linked to specific issues. You get a flat file that resembles your data, not the data itself.
Try this exercise with your current tool. Export everything, then ask yourself:
- Can I import this into another tool and get back exactly what I had?
- Can I write a SQL query against it?
- Can I open it on a machine with no internet connection?
If the answer to all three is no, you have access to a copy of your data. You don't own it in any meaningful sense.
The difference between server location and data format
There is a common assumption that self-hosting automatically solves the ownership problem. It doesn't. If you self-host a tool that stores your data in a proprietary format or a complex multi-service database setup, you still depend on that specific software to make sense of your data.
Consider a tool that runs on your server but requires a separate database server, a caching layer and a search index. Your data is technically on your hardware. But it is spread across three different systems. To extract anything useful, you need to understand the schema, join tables across services and reverse-engineer the data model. That is not practical ownership.
Real data ownership comes from two things working together:
- You control where the data lives (self-hosted or your own infrastructure).
- The data format is portable (you can read it with standard tools without the application running).
Most tools give you the first one at best. Very few give you both.
How does data ownership in project management work with SQLite?
This is where the database format matters. Eigenfocus stores all your project data in a single SQLite file called eigenfocus.db. SQLite is not a proprietary format. It is a public domain file format recognized by the Library of Congress as a recommended storage format for datasets.
That means your data is not locked inside a running database server. It is a file. You can copy it, open it on any computer and query it with dozens of freely available tools.
Here is what it looks like to open your Eigenfocus database and list your projects:
bash
sqlite3 /data/eigenfocus.db "SELECT id, name, created_at FROM projects;"
1|Website Redesign|2026-01-15
2|Mobile App v2|2026-03-01
3|Q2 Marketing|2026-04-10
No special client. No authentication. No API tokens. Just a standard tool reading a standard file format.
You can go further. Want to see how many hours your team tracked on a specific project last month?
sql
SELECT p.name, ROUND(SUM(te.duration_minutes) / 60.0, 1) as hours
FROM time_entries te
JOIN issues i ON te.issue_id = i.id
JOIN projects p ON i.project_id = p.id
WHERE te.created_at >= '2026-05-01'
AND te.created_at < '2026-06-01'
GROUP BY p.id
ORDER BY hours DESC;
Website Redesign|47.5
Mobile App v2|32.0
Q2 Marketing|18.5
This is your data. You queried it directly, without going through an API, without the application running, without an internet connection.
See Eigenfocus pricing and editions.
Can you move your data without the vendor's help?
With most cloud PM tools, moving your data means: export what you can (usually incomplete), import it into the new tool (usually lossy) and accept that you will lose some structure along the way. Custom fields, time entries, view configurations, issue relationships. Something always gets left behind.
With a SQLite file, moving your data means moving a file. Here is the entire migration process:
```bash
Copy from your server
scp server:/data/eigenfocus.db ./eigenfocus-backup.db
That's it. You now have a complete, working copy of your data.
```
You can open that file on your laptop with DB Browser for SQLite and see every project, every issue, every time entry. You can run reports against it. You can write scripts that read from it. The file is self-contained.
Compare that to trying to get your data out of Asana or Monday.com. You would use their API to paginate through resources, handle rate limits, stitch together relationships manually and hope that nothing was missed. Even then, you end up with a pile of JSON files that need custom code to make sense of.
For more detail on how the SQLite file works in practice, see your project data is a single file: SQLite for self-hosting.
What happens to your data when a vendor shuts down?
This is the question nobody asks until it is too late. PM tools shut down, get acquired or change their pricing to the point where you need to leave. When that happens, the quality of your data export determines how much of your project history survives.
If your data lives in a proprietary cloud database, you are at the mercy of whatever export functionality the vendor built. Some tools offer decent CSV exports. Others give you a JSON blob with internal IDs that mean nothing outside their system. A few give you almost nothing.
If your data is a SQLite file on your server, the vendor's fate does not affect your data at all. The file is still there. It still opens. Every query still works. You could stop using Eigenfocus tomorrow and your data would remain fully readable and queryable indefinitely. SQLite files created 20 years ago still open with today's tools. The format is stable by design.
This is not a theoretical advantage. Think about how many project management tools have disappeared or been acquired in the last five years. Wrike was acquired by Citrix, then spun out again. Clubhouse rebranded to Shortcut. Several smaller tools simply shut down. In each case, users had to scramble to get their data out.
How does data ownership in project management affect compliance?
For organizations that handle regulated data, ownership is not just about convenience. It is a compliance requirement.
GDPR gives individuals the right to request that their data be deleted. If your PM tool stores user data in a cloud database you cannot access directly, you depend on the vendor to handle deletion requests. You cannot verify that the data was actually removed. You are trusting their process.
With a SQLite file, you can verify it yourself:
sql
-- Check if a user's data has been removed
SELECT COUNT(*) FROM users WHERE email = '[email protected]';
-- Returns: 0
For industries with data residency requirements, a cloud PM tool might store your data in a region you did not choose. With self-hosting and a local SQLite file, your data lives exactly where you put it. On your server, in your data center, in your jurisdiction.
What should you check before choosing a PM tool?
Before committing to any project management tool, ask these five questions:
- Can I access the raw database? Not an export. The actual database where the application stores data.
- What format is the database in? Is it a standard, open format like SQLite? Or a proprietary system that requires specific software to read?
- Can I query it without the application running? If the answer involves an API, that is not data ownership. That is data access at the vendor's discretion.
- Can I back up by copying a file? If the backup process requires special tools, dump utilities or a running database server, the simplicity of your data management is compromised.
- Will my data be readable in 10 years? If the vendor disappears, can you still open and read your data?
Eigenfocus answers yes to all five. Your data is a SQLite file. You can copy it, query it, back it up and move it with standard tools. No vendor dependency.
For a look at the infrastructure side, see what self-hosted project management actually costs to run.
Frequently asked questions
What does data ownership mean in project management?
Data ownership means you can access, read, query and move your project data independently of the software vendor. It goes beyond export functionality. True ownership means the data is in an open format, on infrastructure you control, and you can use standard tools to work with it without the application running.
Can I query my project data without using the PM tool's interface?
With Eigenfocus, yes. Your data lives in a SQLite file that you can open with the sqlite3 CLI, DB Browser for SQLite, TablePlus or any other SQLite-compatible tool. You can run SQL queries directly against your projects, issues, time entries and custom fields without the application running.
How is a SQLite file different from a CSV export?
A CSV export gives you a flat snapshot of some of your data. A SQLite file is your actual database with all tables, relationships, custom fields, time entries and configurations intact. You can join tables, run aggregations and get answers that a CSV export could never provide. The file is also the format the application uses directly, so nothing is lost in translation.
Is my data safe if Eigenfocus stops being maintained?
Yes. Your data is a standard SQLite file that any SQLite client can open. SQLite is a public domain format maintained independently of any single vendor. Files created decades ago still work with current tools. Even if Eigenfocus development stopped entirely, your project data would remain fully accessible and queryable.
Can I self-host Eigenfocus and keep all data on my own servers?
Yes. Eigenfocus runs in a single Docker container with no external database dependencies. All data stays in a SQLite file on your server. Nothing is sent to external servers. You control where the data lives, who can access it and how it gets backed up.
Take real ownership of your project data
Data ownership is not a checkbox on a vendor's feature list. It is a practical question: can you read your own data with tools you already have? With Eigenfocus, the answer is yes. A single SQLite file, on your server, readable with standard tools.
Eigenfocus is source-available, runs in a single Docker container and stores everything in SQLite. No database server, no vendor lock-in.
Explore how teams use Eigenfocus for self-hosted deployment or as a public-source alternative to closed-source tools. To understand how source-available licensing connects to data ownership, read what source-available means for your self-hosted tools.