What happens to my customer data if I leave ServiceTitan?
Last updated 2026-11-05
The short answer
You can get your data out — ServiceTitan supports CSV export from the Reporting module — but only while your account is still active and your credentials still work. Once a termination is in process, account access can be restricted.
So the order is: export, verify, then give notice. Not notice, then export. Contractors who reverse those two steps end up in a billing dispute with no way to run the reports.
Why the order matters more than the export
Exporting is not hard. Exporting *after* you have told a vendor you are leaving is the failure.
Complaint records at the Better Business Bureau describe disputes running for months after notice, and account access is precisely what you cannot count on during one. A report you can no longer run is a report you do not have.
The practical rule: your data must be out of the platform, checked, and stored somewhere else before the word "cancel" appears in an email.
What to export
Pull every one of these from the Reporting module while the account is live:
- Customer records, including contact history and service addresses
- Job and work-order history
- Invoices and payment records
- Pricebook items and task codes
- Technician records
- Membership and service-agreement data, including expiry dates
Keep two copies — one local and one in cloud storage — and open the files before you trust them. A CSV that downloads successfully and contains the wrong columns is worse than one that fails, because you will not look again.
The three fields that quietly break migrations
Most of a ServiceTitan export maps cleanly into another system. Three things usually do not:
| Field | Why it breaks | What to do |
|---|---|---|
| Preferred-technician assignments | Rarely a first-class field elsewhere | Export separately, map by hand |
| Membership expiry dates | Often a calculation, not a stored value | Rebuild the dates in a spreadsheet |
| Pricebook task codes | Vendor-specific codes, not transferable | Keep the code as a text note |
A dirty import here produces billing errors and callbacks in your first week on the new system — which is exactly when you have least appetite for them.
The contract side, briefly
Leaving mid-term is expensive in a specific way: the early termination fee is the full remaining balance of the contract, not a flat penalty. BBB complaint filings documented by third parties include demands of $67,230, $32,160 and $16,121 — the last being seven remaining months at $2,303 per month. These are second-hand summaries; verify against the BBB directly if you are relying on the pattern.
The only zero-cost exit is the renewal window. Find your renewal date on your signed order form, count back the notice period (commonly 30 to 60 days), and work from there. There is no free trial, so there is no cheap exit at the start of a term either.
If implementation never worked, the Statement of Work is the lever. Several filings turn on contracted deliverables — data migration and pricebook setup are the recurring ones — that were never completed. That is a contract dispute, not a support ticket, and it belongs with a lawyer before you invoke it.
A sequence that works
- Export every dataset above while the account is active
- Open each file and check the columns, not just the row count
- Rebuild the three problem fields by hand
- Start the new system and run both in parallel for at least a week
- Reconcile invoice totals against ServiceTitan line by line
- Only then send written notice, copying your account manager, and ask for written acknowledgement
- Keep the thread — if it becomes a billing dispute, the timestamps are the case
A straight migration for a ten-technician shop typically runs about two weeks in parallel. Budget three to four weeks for multi-location setups or complex membership tiers.
FAQ
Can ServiceTitan refuse to give me my data?
The export is self-service from the Reporting module, so in practice the risk is not refusal — it is timing. Access can be restricted once a termination is in process. Exporting before you give notice removes the problem entirely.
What format does the export come in?
CSV, from the Reporting module. That is enough for migration but it means relationships between records are held in columns rather than enforced, so check that customer, job and invoice IDs line up before importing anywhere.
Do I need to export my attachments and photos?
Yes, if job photos or signed documents matter to your records. CSVs carry the record, not the file. Ask specifically how attachments are delivered, because it is the part most migrations forget until a customer disputes a completed job.
What if I have already given notice?
Ask for written confirmation that export access will remain available for a defined period, and get it before access changes. If that is refused, escalate in writing immediately rather than at the point you discover the reports no longer run.