Home services and trades
ServiceTitan contract renewal: data and exit terms to negotiate
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A ServiceTitan contract renewal is the best moment to fix data and exit terms, because the vendor wants the signature and you can still walk away. Work from the non-renewal notice date, not the renewal date, and settle four terms before it passes: complete export on exit, a post-termination access window, AI data-use limits and deletion confirmation.
Key takeaways
- The non-renewal notice date, not the renewal date, is the real deadline for negotiating.
- Ask for a complete export on exit that includes photos, attachments, call recordings and change history, not only customer and invoice tables.
- Define a read-only access window after termination and require written deletion confirmation once it ends.
- Settle whether the vendor may train AI on your records, and keep your own right to license de-identified data to others.
- Run a test export before renewal so the exit terms are checked against what the account actually holds.
When should the ServiceTitan renewal review start?#
The ServiceTitan renewal review should start as soon as you know the non-renewal notice date in your order form, because that date, not the renewal date, ends your leverage. Field service subscriptions commonly renew automatically for a further term unless one side gives notice by a set point before the current term ends.
Pull the signed order form, the master subscription agreement, any data processing addendum and the online terms the agreement incorporates by reference. Note the notice method as well as the date: some agreements require written notice to a legal address, and an email to your account manager may not count.
Treat these points as general information rather than legal advice; terms differ by customer and by contract version, so read your own documents before relying on any of them.
- Non-renewal notice deadline and the required notice method.
- Current term end date and the length of the renewal term.
- Price change terms that apply on renewal.
- Dates when add-on modules or extra technician licenses were added, and whether they share the main term.
- An internal decision date set well ahead of the notice deadline, with the owner and counsel on the calendar invite.
The renewal checklist: data and exit terms#
The renewal checklist below covers the data and exit terms a CFO should settle before the notice date passes. Price and seat counts get attention anyway; these terms usually do not, and they decide what the company can do with its own job history later.
| Term | What to ask for | Why the CFO cares |
|---|---|---|
| Notice and renewal | A clear notice date and method, plus a renewal reminder from the vendor | A missed notice date can lock in another full term |
| Export on exit | A complete export of all account data in standard formats, with linking IDs | Job history supports warranty claims, audits, a sale and any future licensing |
| Post-termination access | A defined read-only window after the term ends | Large exports take longer than planned, and access may stop at termination |
| Deletion | Deletion after the window, with backups aging out on a stated cycle and written confirmation | Shows where customer data went after exit |
| AI and aggregated data | No training of shared models on identifiable data, a defined de-identification standard and an opt-out | Keeps your records from becoming part of the vendor's product without your choice |
| Your licensing rights | Confirmation that nothing limits you from licensing your own de-identified data to others | Preserves an option the company may want later |
| Changes to terms | Data and AI terms that cannot change mid-term without notice and a right to exit | Stops the deal you signed from shifting under you |
| Assignment | Consent to assign the agreement to a buyer or successor of the business | Avoids friction during a sale or recapitalization |
Export on exit and the retention window#
Export on exit should cover every record family your team created in ServiceTitan, linked by the IDs that connect a customer to a location, a job, an estimate, an invoice and the equipment serviced. Flat table exports without those links lose most of their value for audits, a new platform or AI use.
Ask the vendor to confirm in writing which records are included, in what format, at whose cost and with what help. If the answer depends on API access or a paid services engagement, write the scope and the pricing basis into the renewal instead of leaving it to a future quote.
Do not treat API access as an exit plan on its own. ServiceTitan's API Terms grant only a limited, non-exclusive license to use the APIs for an integration and let ServiceTitan revoke account credential permissions at any time and for any reason. Its API and Data Authorization Terms also make the customer and its authorized partners solely responsible for complying with export and privacy laws when customer data moves to those partners. Export rights written into the agreement are sturdier than an integration that can be switched off.
The retention window is the period after termination when your data still exists and your team can still reach it. Ask for read-only access during that window, so staff can look up jobs while a new system settles, then deletion at the end with a written certificate that the CFO keeps in the contract file.
- Customers, locations and contacts, including merged and inactive records.
- Jobs, appointments, dispatch history and technician assignments.
- Estimates with every option presented, sold and unsold.
- Invoices, payments, refunds and credits.
- Equipment, memberships and recurring service agreements.
- Forms, checklists, technician notes and job summaries.
- Attachments such as photos, signed documents and PDFs.
- Call recordings and transcripts, if the account holds them.
- Pricebook, tags, job types and campaign attribution.
- Change history, where the system keeps it, showing who edited key fields and when.
AI data-use terms to read and to ask for#
AI data-use terms decide whether the vendor may use your job records, technician notes, photos and call recordings to build or improve AI features offered to other customers. Field service platforms keep adding AI features, and the permissions behind them often sit in aggregated-data clauses, product-specific terms or a separate AI addendum rather than in the main agreement.
Also confirm that the agreement does not restrict you. Some contractors later choose to license de-identified job history themselves, and a clause that gives the vendor exclusive rights over data derived from your account would get in the way.
| Clause you may find | Question to ask | Position to seek |
|---|---|---|
| Vendor may use aggregated or de-identified data to improve services | How is de-identified defined, and does it reach free-text notes and recordings? | A written standard that excludes recordings and notes |
| Vendor may use customer data to develop new features | Does that include training models offered to other customers? | Service-only use of identifiable data |
| AI features governed by separate product terms | Can those terms change during the term without notice? | Terms fixed for the term, or a right to opt out |
| Vendor owns usage data and derived insights | Are job outcomes, close rates or pricing patterns treated as usage data? | Your job records and AI outputs remain yours |
| No mention of third-party sharing | Can the vendor share or license your data to model developers? | An express bar on sharing or licensing your data |
Early termination, downgrades and a sale of the business#
Early termination terms decide what the company owes if it leaves mid-term, shrinks or is sold, and a CFO forecasting the next few years needs them in the model. Read whether fees for the rest of the term fall due on termination, whether technician licenses can be reduced at renewal and whether add-ons carry separate commitments.
For a planned sale, check assignment and change-of-control language. A buyer will want the contract to transfer, or a clean exit with the data intact, so ask now for consent to assign to a successor and for export rights that survive any termination, including termination for nonpayment during a wind-down.
If a sale, a platform switch or a closure is already on the horizon, line the retention window up with that plan before you renew. Extending access after notice has been given is usually harder than writing it in while the vendor is still asking for a signature.
Illustrative: a multi-branch HVAC company renegotiates before renewal#
Illustrative: a fictional residential heating, cooling and plumbing contractor with branches across one metro area uses ServiceTitan as its system of record for booked calls, jobs and replacement photos. The CFO finds the non-renewal notice date early, sets an internal decision date well ahead of it and runs a test export for a single branch.
The test shows that customer and invoice tables come out easily, but photos and call recordings need a separate process. The CFO asks for a full-account export with linking IDs and attachments, a read-only window after termination, a deletion certificate, an opt-out from AI training on identifiable data and consent to assign the contract to a buyer. The vendor accepts the window, the certificate, the opt-out and the assignment language, and agrees to document the attachment export steps.
The company renews with those terms in a signed amendment. When the owner later explores a sale, the export rights and assignment terms are already in the file for the buyer's diligence team.
How SourceX reads field service contracts#
Field service vendor agreements shape two stages of the SourceX five-step transaction. In Supply, export rights decide which records can be pulled out at all; in Rights, AI and aggregated-data clauses can narrow what may be licensed. Preparation, Approval and Delivery follow, and the supplier approves each step.
Where a company proceeds, the licensing rights section of the SourceX Evidence Packet records which agreements were reviewed and any limits they set. The company keeps ownership of its records, licenses rather than sells them and approves each release.
Frequently asked questions
What if we already missed the non-renewal notice date?
Read the agreement first, since some renewal clauses allow changes at renewal even after the notice date. Even if the term has renewed, data and AI terms can still be raised, because vendors often agree to an amendment to keep a customer satisfied. Ask in writing, name the specific clauses and set a calendar entry so the next notice date is not missed.
Will the vendor negotiate with a smaller account?
Smaller accounts usually have less room on price, but data and exit terms are often easier to win because they cost the vendor little. A clear written request, a reason tied to audits or a planned sale, and a short list of priorities tend to get further than asking for a full rewrite of the agreement.
Should we run an export even if we plan to stay?
Yes. A test export before renewal shows what actually comes out, which fields lose their links and which attachments need a separate process. It turns the exit terms from a promise into something you have checked, and it gives you a dated baseline copy of your job history for audits and planning.
Who inside the company should sign off on renewal terms?
The CFO usually owns the commercial decision, the COO or operations lead confirms what the team relies on day to day, and counsel reviews any amendment. If the company has a board, investors or a lender with consent rights over material contracts, check those documents before signing a longer renewal term.
Does it matter which system we move to if we leave?
The destination matters less than the shape of the export. Most migrations need linked IDs, attachments and history in standard formats, whatever platform comes next. Agree those terms with the current vendor first, then ask the new vendor what import format it needs and test a sample before giving notice.
Sources
- ServiceTitan's API Terms grant a limited, non-exclusive, nonsublicenseable, nontransferable license to use the APIs only for an interconnection with the platform, and ServiceTitan may revoke Account Credential permissions at any time and for any reason. Source
- ServiceTitan's API and Data Authorization Terms say the customer and authorized partners are solely responsible for complying with export and privacy laws that apply to transferring customer data to authorized partners. Source
Related resources
- QuestionDo I need customer consent to license support tickets?
- QuestionCan I see a sample contract?
- InsightDo you need client consent to license de-identified RFIs and submittals?
- InsightOpt-in vs opt-out for AI training in B2B SaaS contracts
- InsightCan a distributor license its pricing and quote history?
- IndustryLegal data
See if your company qualifies
A short company assessment. No data uploads are needed.