Export ServiceTitan Plumbing Records: A Migration Review Checklist

Distinguish reporting from migration data

ServiceTitan's report documentation describes exporting reports, including XLSX and PDF options. Report filters and choices about detail versus aggregated information affect what the output contains. Consult the current official instructions for the report you are using. Official source

A readable summary can be useful for reconciliation but may not contain the row-level identifiers needed to recreate linked customer, job, invoice, and payment records.

This guide does not claim a universal ServiceTitan export button that produces a complete migration. Account permissions, available reports, and destination support must be verified.

Define the datasets you need

ServiceTitan migration inventory
Dataset: [customers / properties / estimates / jobs / invoices / payments]
Source report or export: [name/reference]
Export date and filters: [details]
Detail rows or summary only: [status]
Source identifiers present: [list]
Relationship identifiers present: [list]
Amount and status definitions: [notes]
Attachments or notes included separately: [reference]
Known gaps: [exception list]

Keep a separate inventory for each entity rather than assuming one report covers the entire business workflow.

Preserve report context

Record the date field used, date range, business-unit or status filters, and any scope restrictions. A report filtered by completed work will not represent all open jobs, even when its title sounds broad.

Do not compare two exports with different filters and interpret the difference automatically as missing data. Align the scope first, then reconcile the records.

A PDF may preserve a readable report, while a structured spreadsheet may be more useful for mapping rows. Choose the representation appropriate to the task and retain the original output.

Map meaning, not just column names

Check whether an amount is an original invoice total, remaining balance, payment total, or another metric. Review whether a job status means scheduled, completed, canceled, or something more specific in that report.

For a fictional example, a summary showing $10,000 of invoiced work and another showing $7,500 outstanding do not necessarily disagree. They may measure charges and remaining balances. The migration needs the relevant underlying records, not a forced equality between different metrics.

Test relationships in the destination

Choose representative records with multiple jobs per customer, more than one invoice where applicable, and partial payments or adjustments. Confirm that the destination preserves the links rather than merely importing similar-looking rows.

Do not claim that GoPlumber supports every ServiceTitan field or transaction type without testing the current import path. Preserve unsupported information in a documented archive and list any operational gap explicitly.

Reconcile the cutover package

Compare record counts, active-job lists, outstanding balances, and sampled historical documents. Keep rejected rows and ambiguous mappings visible until they are resolved or intentionally preserved elsewhere.

Before ending old-system access, verify the data and contractual requirements that apply to your business. Document how work entered after the export date will be captured.

A migration review is complete when the team can trace the necessary business records and explain remaining limitations. The existence of a downloadable report does not by itself prove that continuity.