For many companies outside tech, Teams is the company's memory: shift handovers, approvals, the chat where an operations lead talks a new hire through an exception. It holds the same kind of written reasoning buyers look for in Slack, often in businesses that have never thought of it as an asset.
The largest operating-company archive we know of was mostly Teams. Spirit Airlines' internal records, about 500M Teams messages alongside 100M emails, drew a $10M bid from Google, a $7.5M bid from Mercor and a late $12.5M bid from micro1. Mercor lists Teams among the tools it buys from. This page covers what in Teams buyers value and what to ask before export.
Buyers
Who buys Microsoft Teams data
Each reason is the buyer's own published statement naming Microsoft Teams or the kind of data it holds.
Featured partners
micro1
Lists internal comms, and filed a late $12.5M bid for Spirit Airlines' archive.4,3
- $100K to $2M+, micro1 says5
Watch out for: Says it removes personal details only "when relevant", so ask exactly how.6
Polyshares
Buys chat history alongside email, tickets and ERP records.7
- $100K to $2M+, Polyshares says8
- None, Polyshares says9
- An offer in 1 to 2 weeks, then paid in 30 to 60 days10
Watch out for: Exclusive by default, and every deal it lists is exclusive with no end date.11,12
Everyone else we reviewed
By score, with full reviews. We have no referral agreement with these companies, so we do not link out to them.
What buyers value
What in Microsoft Teams buyers value
The column on the right is not legal advice: it lists what to raise with the buyer before anything is exported.
| Data | Why a buyer values it | Raise with the buyer |
|---|---|---|
| Team channels and their files | Work organised by function, with documents attached to the conversation about them. | Nothing specific |
| Group chats around a process | Approvals and hand-offs between roles, step by step. | Nothing specific |
| Meeting chat and recordings | Decisions and the discussion behind them. | Whether recordings and transcripts are in scope. |
| Frontline and shift chats | Operational exceptions handled in real time. | Employee names, schedules and personal details. |
| External (guest) conversations | Customer and vendor service in writing. | The other organisation's messages. |
Process
How it works with each buyer
In each buyer's own published words. Where a buyer publishes nothing, we say so rather than guess.
micro1
- Internal docs, SOPs and playbooks, knowledge bases, project management workflows, internal comms, templates, CRM and workflow metadata, task histories4
- 30 to 200 employees19
- $100K-$2M+ per data package; over $1M for unique data5
- PII removed "when relevant"6
- The company keeps ownership of its data and reviews samples before release20
- Not published
Polyshares
FAQ
Microsoft Teams data: questions, answered
Only if you offer them. Polyshares lists call recordings among the data it buys; others do not say. Recordings raise more personal-data questions than text, so decide early whether they are in scope.7
Buyers do not publish this. Ask each one how it extracts Teams data, who runs the export, and where it is held before personal details are removed.13
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
Before you sign
Legal questions go to the licensing company
We do not answer legal questions. Ask the licensing company before you sign: their team reviews these with you.
Questions for this kind of business
- Which export method will you use, and does our Microsoft agreement allow it?
- How are guest and external messages handled?
- Are recordings and transcripts excluded unless we opt in?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?