
This data readiness checklist walks you through everything to confirm before you sell business data: what you own, where it lives, how much history you have, what must be stripped out, and how to send a header sample so buyers can bid.
Most owners who ask whether their data is worth anything are really asking a second question: is it ready? The good news is that readiness is mostly an inventory exercise, not an engineering project. You do not need a data team, a warehouse or a migration. You need an honest list of systems, a rough count of what is in each one, and a clear line around what never leaves the building.
Why readiness matters more than size
Buyers who train machine learning models do not pay for gigabytes. They pay for records they can actually use: consistent, long-running, clearly owned, and cleanly de-identified. A company with six years of tidy help desk tickets is often a better seller than a company with ten times the files scattered across personal drives.
Readiness also controls speed. According to founder Jeff Cline, bids tend to come back within 72 hours when the data is described correctly and a header sample is provided. Results vary; not a guarantee. When the description is vague, or when nobody can say who owns the export, the same request can stall for weeks.
The short version
If you can answer these three questions today, you are most of the way there:
- Which systems hold our day-to-day operational records?
- Roughly how many years and how many records sit in each?
- Who in the company has admin rights to export them?
Everything below expands those three questions into a checklist you can work through in an afternoon.
Checklist part 1: Ownership and rights
Before anything else, confirm the business actually has the right to license what it holds. This is the step most likely to need a lawyer, so start it early.
- Confirm the data is the company's. Records you created in the ordinary course of business (tickets, invoices, project tasks, internal email) are usually company records. Data that belongs to a client under contract may not be yours to license.
- Read your customer contracts and privacy notice. Look for language about how you may use information collected from customers. Promises you made still apply even after de-identification is discussed.
- Read the SaaS vendor terms. Your CRM or help desk vendor's terms usually confirm that you own your content, but check for export or use restrictions.
- Check employee policies. Many companies already state that work email and chat belong to the business. If yours does not, ask counsel how to handle it.
- Flag anything regulated. Patient records, payment card data, student records and similar categories are out of scope. Write them down so they are excluded from the start.
For a deeper walk-through of these questions, read is it legal to sell business data. It is general information, not legal advice, and it ends where your attorney's review should begin.
Checklist part 2: System inventory
Now list every system that holds operational history. Use the same nine buckets buyers use, because that is how bids are organized.
- Email: Microsoft 365 or Google Workspace mailboxes. See selling Outlook data and Gmail data.
- Team chat: Slack, Microsoft Teams, Google Chat.
- Shared files: SharePoint, Google Drive, Dropbox, Box, an office server.
- CRM: Salesforce, HubSpot, Zoho, Pipedrive.
- Support and requests: Zendesk, Freshdesk, ServiceNow, Jira Service Management.
- Projects and tasks: Asana, Monday.com, Jira, Notion.
- Accounting: QuickBooks, Xero, NetSuite, Sage, FreshBooks.
- Phones and calls: RingCentral, Zoom Phone, Dialpad.
- Industry software: Clio, ServiceTitan, Procore, dealer systems, Toast, and the admin side of practice systems.
Do not skip systems you stopped using. A retired help desk with seven years of archived tickets can be one of the most valuable things a company owns, as long as you can still export it. The full list of supported systems is on the sell my data hub.
Checklist part 3: Volume, history and seats
For each system, write down four numbers. Estimates are fine at this stage; buyers expect ranges.
- Years of history: the date of the oldest record you can still export.
- Seats: how many people used the system over that period.
- Volume: emails, messages, tickets, records, transactions or call hours, depending on the category.
- Continuity: whether there are gaps, migrations or periods when the tool was replaced.
Where to find the counts
Most systems show totals in an admin report. A few examples from our intake sheet:
- QuickBooks: Reports > Transaction List by Date, set to All dates (row count).
- Zendesk: the "All tickets" view shows the total.
- Slack: Workspace owner: Tools & settings > Workspace analytics > Messages.
- Microsoft 365: admin center > Reports > Usage > Mailbox usage (item counts per mailbox).
Each tool page on this site lists where to find the number for that specific system. Once you have rough figures, the valuation calculator turns them into an illustrative range.
Checklist part 4: What stays out
Readiness is as much about exclusion as inclusion. Decide now what never leaves your control, and write it down so everyone on the deal sees the same list.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
In practice that means:
- No patient records. For clinics and practices, only the admin side (scheduling patterns, billing operations) is in scope, and even then identifiers are removed. See PHI in the glossary.
- No personal customer data. Names, emails, phone numbers, addresses, account numbers and similar fields are removed or replaced before delivery. See PII.
- No payment card numbers, government ID numbers or credentials. These should never be in an export in the first place.
- No privileged or confidential client material you are not permitted to share.
What remains is the operational shape of the business: the sequence of steps, the timing, the categories, the outcomes. That is what buyers want. Our guide to de-identified data explains the techniques in more depth.
Checklist part 5: Export access and format
A buyer can only bid on what you can deliver. Confirm three practical things:
- Admin access: someone with owner or admin rights can run a full export, not just a report.
- Export path: the system offers a native export (CSV, JSON, mailbox archive) or an API. Most mainstream SaaS tools do.
- A person who owns the task: one named employee or contractor who can answer questions about fields and dates.
You do not need to export everything now. In fact, you should not. The full export happens only after a bid is accepted, inside a process that de-identifies the data first. At this stage, you only need to prove that the export is possible and show what its columns look like.
Checklist part 6: The header sample
The single most useful thing you can send a buyer is a header sample: the column names from an export, with no rows of actual data. It tells a buyer what fields exist, how granular the records are and how much de-identification work is needed, without exposing a single customer.
A help desk header sample might look like this:
- ticket_id, created_at, updated_at, status, priority, channel, group, assignee_role, tags, first_response_minutes, resolution_minutes, satisfaction_score
That is all. No ticket text, no requester names, no email addresses. The step-by-step version, with example headers for every category, is in our header sample how-to.
Checklist part 7: Value signals buyers look for
Once the basics are in place, these factors tend to separate a modest offer from a strong one:
- Long, unbroken history. Five or more years in one system shows how operations change through seasons and cycles.
- Linked systems. Tickets that reference projects, or invoices that trace back to CRM deals, let a model learn whole workflows.
- Industry depth. Vertical systems such as Procore or Clio capture work that general tools never see.
- Uniqueness. Data that is hard to find elsewhere is worth more while it is still rare.
In Jeff Cline's experience, small companies have received more than $100,000 for their data, and offers from multiple buyers mean the seller sees the highest bid. Results vary; not a guarantee. The guide on what data buyers want goes deeper on these signals.
Checklist part 8: Timing
Readiness has a clock attached. Buyers want real operational records now, while the models that will use them are being trained. Once a category of business behavior is well represented in training sets, new sellers of that category have less to offer.
That is why the founder's line is worth remembering: "Every industry is a geek away from being uberized." - Jeff Cline. The businesses that hold unique operational records today have leverage that may not last. According to Jeff Cline, deals typically close in about 90 days from first request. Results vary; not a guarantee.
What to do next
Once your checklist is done, the path is short:
- Describe what you have (tool, years, seats, volume) on the request a bid form.
- Send a header sample: column names only, no records.
- Review competing offers from buyers.
- De-identify, sign a license, deliver, and get paid.
If you want to understand the mechanics first, how it works covers each step, and how to sell my business data is the full overview.
How to get your business data ready to sell
- Confirm ownership and rights. Review customer contracts, your privacy notice, SaaS vendor terms and employee policies, and have your attorney confirm the company may license de-identified operational records.
- Inventory your systems. List every email, chat, file, CRM, support, project, accounting, phone and industry system that holds operational history, including retired tools you can still export.
- Record years, seats and volume. For each system, note the oldest exportable record, the number of users over time and the total count of emails, tickets, records, transactions or call hours.
- Define exclusions. Write down what never leaves your control: patient records, personal customer data, payment and ID numbers, and confidential client material.
- Confirm export access. Make sure an admin can run a native export or API pull, and name one person who can answer questions about fields and dates.
- Send a header sample and request a bid. Export only the column names from each system and submit them with your counts on the request-a-bid form.
Frequently asked questions
What does it mean for business data to be ready to sell?
Data is ready to sell when you know you own it, can export it, can describe its history and volume, and have a plan to de-identify it. It does not need to be cleaned, merged or moved into a warehouse first; buyers mainly need an accurate description and a header sample.
Do I need to clean my data before selling it?
No, you usually do not need to clean it yourself. Buyers want real operational records, including the messy parts, because that is how work actually happens. What must happen before delivery is de-identification, which removes personal and sensitive fields.
How many years of data do I need?
There is no fixed minimum, but longer history is generally more valuable. Several years in a single system shows seasonal patterns, process changes and outcomes over time, which is what model builders want to learn from.
What is the fastest way to find out if my data is worth anything?
The fastest route is to submit your tools, years, seats and volume on the request-a-bid form and include a header sample. According to founder Jeff Cline, bids often come back within 72 hours when the data is described correctly. Results vary; not a guarantee.
Is customer or patient information included?
No. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control. For healthcare practices, only admin-side operations such as scheduling and billing patterns are considered.
Can I sell data from a system I no longer use?
Yes, if you can still export it and you still have the right to license it. Retired systems often hold the longest, most complete history a company has, which can make them attractive to buyers.
Who in my company should own this checklist?
One person with admin access and authority to sign off should own it, usually an owner, operations lead or IT manager. Bring in your attorney for the ownership and contract questions in part 1.
Sources
Updated November 19, 2026.
OpenDataPolicies.org connects businesses with buyers of de-identified operational data. We are not a law firm, broker-dealer or investment adviser, and nothing on this site is legal, tax or financial advice. Statements about amounts, timing and outcomes are Jeff Cline's statements based on past transactions. Results vary; nothing here is a guarantee of any bid, price, buyer or closing. Every deal depends on the data, its quality, its rights and buyer demand at the time.