How to switch from ServiceTitan without a big-bang cutover

Most failed software switches fail on a Monday. New dispatch board, new tech app, new invoices and new phone routing all go live at once, the board is full, and by 10 a.m. nobody can find last month's history. The fix isn't better software. It's a staged switch: one crew moves first, then the office, then the old system becomes a read-only archive.

That takes six to ten weeks instead of one weekend, and it takes far less out of your team. This post walks through the contract, the exports, the four things that won't move cleanly, and a week-by-week plan we'd follow ourselves.

Start with the contract, not the software

Before you look at a single export, find three dates in your agreement: the end of the current term, the deadline for giving notice of nonrenewal, and the date your access ends.

ServiceTitan doesn't publish its subscription agreement, so the only reliable source is your own copy. A competitor's write-up citing BBB complaints describes a standard 12-month initial term, with 24 and 36 month terms offered at small discounts, and notice commonly due 30 to 60 days before renewal.¹ ServiceTitan's published Terms of Use say that ending early means a termination fee equal to all remaining payments, so timing your switch to the renewal date is almost always the cheapest path.²

Two parts of the Terms of Use are worth reading closely before you give notice. On request at termination, ServiceTitan will make "commercially reasonable efforts" to export your data, fees may apply, and the format is its choice, such as a SQL Server backup file. And cancellation goes through your customer success manager.³

So, in this order:

1. Put your notice deadline in the calendar with a reminder two weeks earlier.
2. Request your full data export in writing before you give notice. Ask what format you'll get, when, and whether there's a fee. Keep the email.
3. Run your own exports (next section) while you still have full access.
4. Give notice in writing, by the method the contract specifies, before the deadline.

The exports to run while you have full access

Don't rely on a single end-of-contract backup. A .BAK file needs SQL Server and someone who knows it, and it may arrive after you've already needed something from it. Run these yourself, save them somewhere you control, and repeat the ones that change closer to cutover.

Two notes. Pricebook images may not come along in the spreadsheet. And creating some custom reports depends on your ServiceTitan package, so if a template is missing, ask your CSM in writing early.

Write the date on every file. When you re-run them later, you'll want to know which is newer.

What doesn't move cleanly, and what to do about it

Most of your data is rows in a spreadsheet and moves fine. Four things don't.

Stored cards

ServiceTitan stores a token and the last four digits; the card itself sits with the payment processor.⁹ Processors such as Adyen will only export card data to another PCI-compliant processor, as an encrypted file, through a formal request from the data owner.¹⁰ Whether that request can be made for a departing contractor's cards is not something to count on.

Plan to re-collect cards. Use the Saved Payment Methods report to list who has a card on file, prioritize members on autopay by next bill date, and send each a secure card-update link about 10 days before their next charge. Collect the rest on their next visit. Old autopay keeps running in ServiceTitan until each member updates, so nobody misses a payment and nobody pays twice if you track it.

Phone numbers

You can port numbers out of ServiceTitan; its help center lists what the new carrier needs, including a screenshot of your phone number settings, your account zip code and your Tenant ID as the account number.¹¹ Simple ports can take a business day, but carriers quote 3 to 7 business days for many and 3 to 4 weeks for complex ones, and toll-free numbers add more.¹²¹³

Start the port early and finish it late. Submit the port once you know the target date, keep your published numbers ringing on the old system until it completes, and don't schedule it in your busiest week. Map each call tracking number to the same campaign in the new system so your marketing reports survive.

Attachments, photos and call recordings

One switching guide warns that images, documents and call recordings may not export.¹⁴ Decide what you actually need. Usually it's photos and signed paperwork for open warranties and recent installs. Download those by hand for the customers who matter, ask for the rest in your written export request, and accept that some of it lives in the archive until it ages out.

Job and invoice numbers

If you sync to QuickBooks Online, duplicate invoice numbers cause rejected exports; ServiceTitan's own help center documents the error.¹⁵ Make sure your new system starts numbering above your last ServiceTitan job number, and agree a cutover date with your bookkeeper: ServiceTitan posts everything before it, the new system everything after. Never re-post history.

The parallel-run plan: one crew, then the office, then archive

The safest switch runs both systems side by side for a short, defined period.

Stage 1: one crew. Pick a lead tech who likes trying new things and one or two others. They take their jobs in the new system for a week or two while everyone else stays put. The goal is to find the gaps in your pricebook, forms and job types while they're cheap to fix.

Stage 2: the office. Once that crew is comfortable, move booking and dispatch. From this point new jobs start in the new system. Jobs already scheduled in ServiceTitan finish there, so nobody re-enters an appointment mid-flight.

Stage 3: everyone, and the archive. All crews move. ServiceTitan becomes a lookup-only system until your access ends. Run your final exports in that window and keep them somewhere permanent.

A competitor's guide puts a ServiceTitan exit at 6 to 10 weeks with 2 to 4 weeks of parallel running.¹⁴ Your pace depends on your size and season more than on the software. During the overlap, ServiceTitan can email scheduled reports as Excel files every day, but only to employees with an email on their profile, which is a cheap way to keep the new system current.¹⁶

A week-by-week plan

This assumes you start about 90 days before your renewal date. Compress or stretch it to fit, but keep the order.

1. Before week 1

   Dates and a written request

   Term end, notice deadline, access end. Request the full data export in writing. Choose a lead crew and one office owner for the switch.

2. Weeks 1 and 2

   Exports and setup

   Run every export above. Import customers, locations, equipment and pricebook into a sandbox first. Set up users, job types, business units and forms. One hour of training for the lead crew, on their own phones.

3. Weeks 3 and 4

   The lead crew goes live

   Real jobs in the new system. Collect every where-is-the question and fix setup daily. Re-run customer and pricebook exports.

4. Weeks 5 and 6

   The office moves

   New bookings and dispatch move. Submit the phone port. Bring memberships over and start card-update links. Give notice if you haven't.

5. Weeks 7 and 8

   Everyone, then archive

   All crews move. ServiceTitan is read-only. Final exports, open balances checked against AR Transactions By Customer.

Where TradesWork fits

We built a switch kit for exactly this file-based approach. You drop your ServiceTitan customer list, pricebook, locations and equipment exports, plus job, invoice and membership reports, in any order or as one ZIP, and preview everything before it's saved, optionally into a sandbox company first. Rows that need a look go to a downloadable list. Re-dropping a newer export updates the same records instead of creating duplicates, and new job numbers continue above your last ServiceTitan number.

app.tradeswork.app · Membership KPIs and visits due

Job and invoice history comes over with its job numbers and paid status, and memberships arrive with their visits due and billing held off until you press start, so nobody is charged twice. Imported history never posts to accounting. Connect the QuickBooks Online file ServiceTitan already syncs to and TradesWork reconciles counts and open A/R to the penny, listing every mismatch. For the parallel run, you can schedule ServiceTitan reports to email a TradesWork import address daily.

The limits, plainly: several of these layouts were built from ServiceTitan's screens and help docs and are still being validated against real exports, so keep your own files as an archive too. There's no API connection to ServiceTitan, by design, because ServiceTitan's API terms forbid apps whose purpose is migrating customers off the platform.¹⁷ And cards and phone numbers still need the steps above.

So you're never in this position again: owners can download everything in TradesWork as one ZIP, any time. Pricing is published per tech or sales seat, with month-to-month available.