Home services and trades
Platform vs add-on: what your role in a roll-up means for systems and data
By SourceX Editorial · Updated
Short answer
In a home services roll-up, the platform company's systems usually become the group standard and each add-on migrates onto them. A platform owner inherits the data model and the archive duty for the group. An add-on owner must preserve its own history before old systems are shut off, ideally with record access agreed before closing.
Key takeaways
- The platform sets the systems, job types and reporting definitions that add-ons adopt.
- Migrations usually move customers, open jobs and balances, not the full closed job history.
- Add-on owners should export and archive everything before cutover, especially when an earnout depends on later reporting.
- Each acquired company's contracts and privacy notices travel with its records, even inside a group.
- Access to records after closing belongs in the purchase agreement, not in a later favor.
What is the difference between a platform and an add-on?#
A platform is the anchor company a private equity sponsor or holding group buys in a sector, usually first, chosen as the base that later acquisitions join. An add-on is a company acquired afterward and folded into the platform's operations, brand or reporting.
The roles carry different expectations. A platform usually keeps its leadership team, systems and processes and becomes the template for the group. An add-on is usually expected to adopt that template, sometimes quickly, so the group can report on one set of numbers.
For owners, the difference shows up most clearly in software. Whether your field service platform, phone system and accounting setup survive the deal depends heavily on which role you play.
How each role changes your systems and records#
Each role changes systems and records in a predictable way, and the two-column comparison below shows the typical pattern. Integration plans vary from sponsor to sponsor, so confirm the specifics with the buyer before signing.
| Area | Platform company | Add-on company |
|---|---|---|
| Field service system | Usually becomes the group standard | Usually migrates to the platform's system |
| Accounting | Often moves to a group chart of accounts | Adopts the platform's setup and close calendar |
| Phone and call tracking | May be extended across the group | Often replaced, which puts recordings at risk |
| Pricebook and job types | Defines the shared definitions | Maps legacy job types to the platform's list |
| Membership programs | Sets the group program | Converts or honors existing agreements |
| Historical archive | Responsible for its own and inherited archives | Must export history before the old system closes |
| Reporting | Builds group KPIs | Reports on platform definitions, which can shift baselines |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
What happens to an add-on's job history during migration?#
An add-on's job history usually stays behind during migration, because new systems import customers, equipment, open jobs and balances far more readily than years of closed jobs, notes and photos. The old system's history survives only if someone exports it.
Export defaults can quietly hide history. ServiceTitan's own guide for migrating from FieldEdge says to set every filter on the Invoices tab to All before exporting, so the export includes all invoice data rather than only the previous six months. Its Housecall Pro guide says to set the jobs date range back to when you started and to run reports in one-year batches if a report errors.
| Record | Usually migrated | Often left behind |
|---|---|---|
| Customers and locations | Active customers | Old contacts and duplicates |
| Equipment records | Installed equipment | Service history per unit |
| Estimates | Open estimates | Declined and expired options |
| Closed jobs and invoices | Balances and summaries | Line items, notes and technician detail |
| Memberships | Active agreements | Renewal and cancellation history |
| Photos and attachments | Rarely | Most of the archive |
Records an add-on owner should secure before closing#
The records an add-on owner should secure before closing are the ones that prove past performance and support any earnout or holdback. Once the old system is shut off, getting them back may depend on the buyer's goodwill.
If part of the price depends on future results, keep a copy of the baseline reports and the definitions behind them. When the platform's definitions differ from yours, a saved baseline is the clearest way to compare like with like.
- Full exports of customers, jobs, invoices, estimates and memberships from the field service system.
- Call recordings and call logs from the phone and call tracking systems.
- Job photos and documents, organized by job number.
- Accounting history and the reports used to build your financial statements.
- Warranty registrations and manufacturer claim history.
- A purchase agreement clause covering your access to records after closing.
What the platform owner takes on#
The platform owner takes on the job of making many companies' records comparable. That means a shared data model: one list of job types, consistent membership types, common call outcome tags and one expected way of writing technician notes.
The platform also inherits a stack of legacy archives and the obligations attached to them. Each acquired company collected records under its own customer terms and privacy notices, and those terms do not change because the company was bought. A consolidated archive should keep track of which company and which system each record came from.
Platforms that document these decisions early spend less time later reconciling branch reports, answering lender questions or preparing the group for its own eventual sale.
Systems questions to ask before you sign#
Systems questions asked before signing give an owner leverage that disappears after closing. The answers shape the integration timeline, the earnout mechanics and how much of the company's history survives.
Ask platform owners the mirror image: which add-on records they are prepared to archive, for how long, and who inside the group will be able to read them.
- Which of our systems will be replaced, and in what order?
- Who runs the migration, and which records will be imported versus archived?
- How long will the old systems stay readable, and who pays for that?
- Which job type, membership and revenue definitions will our earnout reports use?
- Who in the group can access our archived customer records, and under which privacy notice?
- Will our call recordings, photos and documents move, and where will they live?
Illustrative: an electrical add-on joins an HVAC platform#
Illustrative: a fictional electrical and generator service company agrees to join an HVAC platform backed by a private equity sponsor. The add-on runs Jobber, while the platform runs ServiceTitan and plans to migrate the add-on soon after closing.
Before closing, the add-on's owner exports clients, jobs, invoices and reports from Jobber, saves call recordings from the phone provider and archives job photos by job number. The purchase agreement gives the owner read access to the archive while an earnout runs.
After migration, the platform's reports classify some generator maintenance as service rather than installation work, which changes the earnout baseline. The owner's saved reports and written job type mapping settle the question quickly, and the archive later joins the group's consolidated history.
How SourceX treats roll-up records#
SourceX treats roll-up records company by company, because the supplier in a data license is the legal entity that holds the records and can approve their use. In the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery, each acquired company's contracts and notices are reviewed in the Rights step.
A platform can coordinate several companies, but each package gets its own SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. Consolidated legacy archives can be assessed from metadata first, without moving any files.
Frequently asked questions
Can an add-on owner keep a copy of company data after the sale?
Only if the purchase agreement allows it. Once the business is sold, its records generally belong to the buyer, and keeping copies without permission can breach confidentiality terms. Negotiate defined access, such as read-only archive access during an earnout period, rather than relying on informal copies.
Who pays to keep legacy systems running?
That is a deal point. Some buyers keep a legacy subscription in read-only mode for a period, some pay for a full export and archive, and some ask the seller to finish exports before closing. Settle it in writing during integration planning.
Does a stock or asset purchase change how records move?
It can. In a stock purchase the company itself, with its records and contracts, changes hands. In an asset purchase the agreement lists what transfers, and some contracts may need consent to assign. Counsel should review how records and customer contracts transfer in your specific deal.
Should job types be standardized before or after migration?
Map them before migration and standardize as part of it. A written mapping from each legacy job type to the platform's list keeps history comparable and prevents reclassification disputes later, especially when reports drive earnouts or bonuses.
Do technicians lose their job history after migration?
Often they lose easy access to it. Technicians rely on equipment history and past notes at each visit, and a migration that imports only customers and open jobs leaves them starting cold. Ask whether service history per equipment record can be imported, or at least attached as a document.
What if the add-on stays on its own system?
Some groups leave smaller add-ons on their existing software for a while. The records then stay intact, but group reporting depends on exports or integrations. The add-on should still document its definitions, because a later migration raises the same questions.
Sources
- ServiceTitan's FieldEdge migration guide says to set every filter on the Invoices tab to All before exporting, so the export includes all invoice data rather than only the previous six months. Source
- ServiceTitan's Housecall Pro migration guide says to set the jobs Date Range back to when you started, and to run a report in one-year batches if it errors. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.