Consolidating field service software across home services add-ons

What moves when an add-on joins the platform system?#

A ServiceTitan migration after an acquisition usually moves the records a dispatcher needs tomorrow morning: customers, service locations, equipment, active memberships and open jobs. Closed job history, call recordings and the narrative notes behind each visit tend to come across partially or not at all, because migration templates are built around active operations rather than archives.

Integration leads who plan from the migration template alone often find the gaps months later, when a warranty claim or a callback dispute needs a record from the old system. Decide record family by record family what migrates, what is archived and what is deliberately left behind, and write that decision into the integration plan.

Separate account, merged account or archive only?#

The account decision for each add-on comes down to how independently the brand will operate after the deal. Some platforms keep an acquired brand on its own account for a period, some fold it into the platform's account as a new business unit, and some move only active records and freeze the rest in an archive.

Whether two ServiceTitan accounts can be merged, and what carries across if they are, is a question for the vendor's implementation team and your contract. Plan as if full history will not come across. That assumption forces the export work to happen while the old system is still live and someone who knows it is still on staff.

Export checklist before cancelling an add-on's old system#

The export checklist should be finished, and the archive opened and checked, before anyone gives notice on an add-on's subscription. Vendor documentation is specific about the traps. ServiceTitan's guide for teams moving from Housecall Pro says to set the jobs Date Range back to when the company started, select all table columns, and run the report in one-year batches if it errors.

The same vendor's FieldEdge guide says to set every filter on the Invoices tab to All, or the export covers only the previous six months. Jobber's help center says cancelling an account preserves it so reports can be retrieved later, while permanently closing it is final. Each of those details decides whether history survives the cutover.

• 1Customers, locations and contacts, including secondary service addresses.
• 2Equipment with serial numbers, install dates and linked service history.
• 3Full job history from the first day the system was used, with line items and invoice numbers.
• 4Estimates, including the ones homeowners declined.
• 5Technician notes, forms, checklists and photos attached to jobs.
• 6Call recordings and transcripts from the phone system, which is often a separate vendor.
• 7Memberships, warranties and callback records linked to the original job.
• 8A data dictionary explaining each column and the job type and outcome codes the brand used.

Which records are easiest to lose, and why they matter#

Call recordings and note history are the records most often lost in a field service consolidation. Recordings frequently live with a separate phone or call-tracking vendor whose contract ends with little attention, and note history sits in free-text fields that migration templates flatten or skip.

Those records explain why a job went the way it did: what the homeowner reported, what the technician found, why an estimate was declined, why a callback happened. For operations they settle warranty and quality questions. For any later licensing review they are the part of the archive that links a request to a decision and an outcome, which is what makes job records useful to AI developers.

Use vendor-supported exports rather than handing credentials to outside tools. ServiceTitan's terms of use say users must not let any third party, expressly including an AI agent, access or use ServiceTitan technology, so read the platform terms before connecting anything new to pull history.

Keep brand, entity and source tags on every record#

Provenance tags are the cheapest protection a consolidation can buy. Each migrated or archived record should carry the acquired brand, the legal entity that collected it, the source system, the legacy record ID and the migration date.

Those tags matter because a combined platform account blurs who collected what. Each add-on was a separate company with its own customer terms, privacy notices and sometimes franchise obligations, and those terms travel with its records even after the trucks are repainted. Without the tags, a later rights review has to reconstruct the history from invoices and memory.

Illustrative: a platform folds three add-ons into one system#

Illustrative: a fictional HVAC and plumbing platform runs ServiceTitan and buys three add-ons within a short period. One runs Housecall Pro, one runs FieldEdge and one runs Jobber. The integration lead moves customers, equipment, active memberships and open jobs into the platform account, with each add-on set up as its own business unit.

Before giving notice, the team exports each add-on's full job history, estimates, invoices and notes, pulls call recordings from two separate phone vendors, and opens every file to confirm it is complete. The Jobber account is cancelled rather than permanently closed until the archive is checked. Every record gets brand, entity and source-system tags.

When the group later considers licensing de-identified job records, the archive answers the first questions quickly. Two brands have connected history from first call to callback. The third lost its notes in an earlier software change and is parked.

How SourceX approaches consolidated field service records#

SourceX treats each acquired brand's archive as a separate supply within the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check collects metadata such as systems, date ranges and record families, not files, so it can run while the archive is still being assembled.

Where a package proceeds, the SourceX Evidence Packet captures provenance, including the source system and migration path, together with licensing rights, permitted use, the privacy record and release authorization from the entity that collected the records. Large archives stay in the company's own storage.