Colocation company acquisition: separating operator records from customer data
In a colocation company acquisition, the operator's own records can support an AI data license: incident tickets, maintenance and change records, capacity plans and remote-hands logs. Customer equipment details, customer data and site-security information stay out. Sponsors should screen the operator during integration, before legacy ticketing, maintenance and DCIM tools are consolidated and their archives disappear.
What part of a colocation operator can be licensed
A colocation operator's own records can support an AI data license: incident and service tickets, preventive maintenance and failure histories, methods of procedure and change records, capacity plans and remote-hands logs. Customer equipment details, anything stored on customer equipment and anything about site security stay out, whatever else the contracts allow.
That split matters most right after an acquisition. A regional operator may carry years of history across several sites, and integration plans often retire legacy ticketing, maintenance and DCIM tools, taking their archives with them.
Which operator records are worth screening
| System | Records | Why AI buyers value them |
|---|---|---|
| Ticketing or ITSM | Incidents, escalations, service requests, root-cause write-ups | Fault-to-resolution chains with timestamps |
| Maintenance management (CMMS) | Preventive maintenance on UPS units, generators, chillers and CRAH units, failures, parts, vendor visits | Asset histories with failure and repair outcomes |
| Change management | Methods of procedure, approvals, rollback plans, post-change reviews | Planned work with explicit steps and results |
| Operating procedures | Standard and emergency operating procedures, drill records, after-action notes | Procedures tested against real events |
| Capacity planning | Space, power and cooling forecasts, expansion cases | Long-horizon decisions that can be checked against actuals |
| Remote-hands logs | Requests, tasks performed, time spent, follow-ups | Hands-on technical work described step by step |
| NOC chat and email | Shift handovers, alarm triage, vendor coordination | The reasoning between an alarm and an action |
| Sales and quoting | Quotes by kilowatt and cabinet, deal outcomes, renewal notes | Pricing decisions with outcomes |
Records like these show how people run critical facilities: triaging an alarm, sequencing a generator test, deciding when to add cooling. That is the multi-step, tool-heavy work AI developers need for training and evaluating agents, and it rarely appears in public sources.
The cage-line rule: operator records vs customer data
Draw the line at the cage door. Records about running the building sit on the operator's side; anything about what is inside a customer's cage, or about who can get into the building, does not.
| Record | Side of the line | Treatment |
|---|---|---|
| Generator, UPS and cooling maintenance | Operator | Candidate |
| Incident tickets about building systems | Operator | Candidate, with customer names removed |
| Remote-hands tickets | Mixed: operator work on customer equipment | Candidate only after customer identities and equipment details are removed under agreed rules |
| Customer equipment lists, network diagrams, IP plans | Customer | Out |
| Data stored on customer equipment | Customer | Out, always |
| Cross-connect orders naming customers and carriers | Customer commercial information | Out unless contracts and customers allow |
| Per-cabinet power draw in DCIM | Attributable to individual customers | Out at cabinet level; discuss any aggregates with counsel |
| Badge logs, CCTV, visitor lists, security procedures | Site security | Out |
| Customer contracts and pricing | Confidential | Out, except as agreed |
Promises count as well as contracts. FTC staff have stated that commitments not to use customer data for undisclosed purposes, such as training or updating models, are enforceable whether they appear in privacy policies, terms of service or promotional materials (FTC technology blog, January 2024). Review the operator's customer agreements and its published security and privacy pages before anything is scoped. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.
The general method is set out in the guide on telling company data apart from data owned by its customers.
Which colocation operators fit
- Multi-site regional operators with a NOC, facilities engineering, sales and a central office are the most likely to reach 50+ full-time employees at peak (contractors excluded). Many single-site and edge operators run lean and fall short, so check headcount first.
- Several years of operating history, including tickets and maintenance records from before any rebrand or system change.
- Many connected systems: ITSM, CMMS, DCIM and building management, change management, email and chat, CRM and finance.
- Operators that were acquired or wound down can still qualify if the records survive and someone with authority over them will sponsor a license.
Weaker fits: wholesale facilities where tenants run their own operations, managed hosting and cloud businesses whose work is mostly processing customer data, and sites with government or defense tenants whose security terms reach operating records.
When integration is the moment
Illustrative timeline; the integration plan sets the real dates.
| After close | Integration step | Records step |
|---|---|---|
| First 30 days | Transition services agreement in place, access to the seller's systems confirmed | List every system holding operating history and who administers it |
| Days 30-90 | Ticketing moves to the platform's ITSM | Export the full legacy ticket history, including closed tickets and attachments |
| Days 90-180 | CMMS and DCIM consolidated, procedures rewritten to platform standards | Keep the old procedures and maintenance histories before they are replaced |
| Months 6-12 | Brand and NOC consolidation, legacy tools cancelled | Confirm exports are verified before subscriptions lapse |
| Before exit | Equity story assembled | Decide whether a records license belongs before or after the sale |
Carve-outs need extra care. If the seller's parent keeps the systems under a transition services agreement, exports have to be negotiated before that agreement ends. The same before-cutover logic applies to warehouse automation integrators, whose commissioning and service archives are also at risk during integration.
Who makes the introduction
The operating partner or the platform's integration lead is best placed, because they control the systems calendar. A data center operations executive on the platform's board, or the deal team's IT diligence adviser, can also spot the moment. The partner role is the same in each case: introduce the sponsor and let the operator's team handle the inventory. The page for private equity operating partners explains how that works across a portfolio.
What to say to the operator's leadership
How the process and reward work
Once introduced, the operator is qualified by SourceX on size, history, data breadth and rights; it then lists its systems and years of records in a data inventory, agrees price and terms, and only then do AI labs and data buyers review a description. The operator is paid when the deal closes and the data is delivered. You never touch tickets, logs or drawings yourself.
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; no reward is guaranteed, and it is never deducted from what the operator receives. Check your fund's policies before registering.
Next step
Ask the integration lead for the date the legacy ticketing system will be switched off, and run the company fit checker against the who qualifies baseline before then. If the operator passes, register as a partner and introduce its CEO, or have the CEO apply at sourcex.si/apply with your referral link.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Can an edge data center operator qualify for a data license?
Only if the operating company had 50+ full-time employees at peak (contractors excluded) and has several years of documented operations. Many edge operators run remote sites with small teams, so headcount is the first check. A platform that has rolled several edge operators together may qualify where a single site would not.
Do colocation customers have to consent before operator records are licensed?
Not for records that are purely about running the building and never identify a customer, though counsel should confirm against the customer agreements. Records that name customers, describe their equipment or reveal their commercial terms need either customer consent or removal of those details under redaction rules agreed before any work begins.
Are DCIM and building management trends licensable?
Building-level power, cooling and environmental trends are operator records and can be candidates. Cabinet-level or circuit-level readings can be tied to individual customers, so treat them as customer-attributable and keep them out unless counsel and the customer agreements allow an aggregated form.
Will a records license complicate the transition services agreement?
It can if the seller's parent still controls the systems. Exports for retention or licensing should be written into the TSA exit plan, and the parent may need to cooperate. Where the platform already controls the systems outright, the license runs as a separate agreement between the operator and SourceX.
Does SourceX need site addresses, floor plans or security details?
No. Site security information is excluded from any license, and the introduction itself only needs basic fit facts like staff size, operating history and the systems in use. Partners never export or describe confidential records; the operator's own team prepares the data inventory directly with SourceX.
Related pages
- How to distinguish company data from data owned by its customers
- Material handling integrator acquisition: commissioning and service records to screen
- Referral opportunities for private equity operating partners
- Check Company Fit for Data Licensing
- Which US businesses are a fit for a SourceX data licensing introduction
Free resources
- IRR calculator — Internal rate of return on annual cash flows.
- Business valuation calculator — Enterprise and equity value from EBITDA, your multiple, cash and debt.
- Portfolio data opportunity scanner — Screen several companies in one session.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment