How home services roll-ups can license job records across brands

Why do roll-up platforms hold unusual job histories?#

Roll-up platforms hold unusual job histories because they combine many local service businesses across trades, regions and climates under one owner. An HVAC brand in a hot market, a plumbing brand serving older housing stock and an electrical brand doing panel upgrades together cover more equipment types, failure modes and customer decisions than any single contractor.

The same breadth makes the records hard to use. Each add-on arrived with its own field service platform, whether ServiceTitan, Housecall Pro, Jobber, FieldEdge or a set of spreadsheets, its own job types and its own habits for technician notes. No two brands describe the same repair the same way, and none of them was set up with a later license in mind.

Breadth helps only when each brand's records hold up on their own. A developer reviewing a combined package will check brand by brand whether calls link to jobs, jobs to invoices and invoices to callbacks, so the strongest single brand usually sets the standard the others are measured against.

The per-brand screen to run after every add-on#

A per-brand screen captures the facts that decide whether a brand's records can be licensed. Run it once for each brand and again after every add-on closes, so the platform's picture stays current as the group grows.

How the acquisition structure shapes rights to old records#

The acquisition structure largely decides which entity holds old records and on what terms. In a stock purchase, the acquired company generally keeps its records and its contracts, including any limits written into them. In an asset purchase, records usually move only if the purchase agreement lists them among the acquired assets, and some agreements leave pre-closing books or certain customer files with the seller.

Read each purchase agreement's definitions of purchased assets, books and records, and excluded assets, then check any transition services arrangement that kept a legacy system running after closing. If add-ons were later merged into one operating entity, that entity may sign for all of them, but each brand's pre-acquisition customer contracts, privacy notices and vendor terms may still apply to its records. Where the wording is unclear, counsel should confirm the position before a brand's history is offered to anyone.

Earnouts and rollover equity deserve a separate look. If a founder's earnout depends on brand revenue or margin, licensing income may raise questions about how it is counted, so agree on the treatment with the founder and counsel before any license is signed.

Rescue legacy archives before integration retires them#

Legacy archives are most at risk during integration, when teams move each brand onto the platform's chosen software and cancel old subscriptions to cut cost. Once an account closes, the vendor's retention terms decide whether anything can be recovered.

The export mechanics are the same as in any platform switch. What a roll-up adds is ownership, timing and one standard across brands, so build these steps into the integration playbook and assign them to the person who signs off on each cutover:

• 1Make a reconciled legacy archive a required gate before any add-on's old subscription is cancelled.
• 2Where possible, secure read-only or export access to the legacy platform for a set period in the purchase agreement or transition services arrangement.
• 3Keep a brand-to-entity map showing which legal entity owns each archive and under which purchase agreement it arrived.
• 4Use one export standard for every brand: the same file formats, original IDs, export log and data dictionary.
• 5Capture what the founder or office manager knows about custom fields, job types and workarounds before they move on.
• 6Build a crosswalk from each brand's job types and cause codes to the platform's scheme.
• 7Store archives in platform-controlled storage, with access limited by brand.

Who approves at the platform and brand level?#

Approvals in a roll-up run at two levels: the platform decides whether to pursue licensing at all, and the legal entity that holds each brand's records signs that brand's license. The operating partner or platform COO picks pilot brands and keeps the program moving, while the signature comes from each supplier entity's authorized signer.

Founders who stayed on as brand presidents are often the best source on what the old records contain and which customer relationships carry sensitivities. Bringing them in early also avoids the impression that their company's history is being licensed without their input.

Illustrative: a regional HVAC and plumbing platform screens four brands#

Illustrative: a fictional regional platform owns four brands acquired over several years. The first has run the same field service platform since its founding, with linked bookings, jobs, invoices and callbacks. The second kept jobs in spreadsheets until the platform moved it onto shared software. The third was bought in an asset purchase that left pre-closing customer files with the seller's holding company. The fourth operates as a franchisee of a national brand.

The operating partner pilots the first brand, whose history is deep and linked and whose entity is a clear signer. The second is parked because its older records lack outcomes. The third waits for counsel to confirm what transferred. The fourth is held until the franchisor's position on customer data is known. The platform also adds an archive export step to its playbook for future add-ons, so the next acquisition arrives with its history intact.

Mistakes that cost roll-ups their job history#

The costliest mistake is cancelling an add-on's old platform to save on subscriptions before anyone exports its history. The saving is real, but the brand's only record of past diagnoses, callbacks and equipment cannot be rebuilt once the account is purged.

Close behind are migrations that keep job summaries but drop original IDs, so notes, invoices and callbacks can never be relinked; quoting a group-wide figure to lenders or the board before any brand has been scoped; and assuming that owning the platform means owning every record each add-on held, when purchase agreements, customer contracts and franchise terms may say otherwise.

How SourceX works with multi-brand platforms#

SourceX runs each brand as its own transaction under the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Brands can be compared with the SourceX Enterprise Data Value Framework, which weighs drivers such as uniqueness, scale, data cleanliness, rights and privacy burden.

For each package, the SourceX Evidence Packet documents provenance, including the acquisition chain that brought the records to the current owner, along with licensing rights, permitted use, the privacy record and release authorization. Large archives stay in platform-controlled storage or ship on encrypted drives, and the first assessment of every brand runs on metadata only.