How to Switch from ServiceTitan to Jobber
Plan, execute, and survive the move. A practical 60 to 90-day playbook for HVAC, plumbing, and electrical shops cutting cost or right-sizing.
When this switch makes sense
Three signals justify the move. (1) Team size dropped below 12 techs and the per-tech ServiceTitan fee no longer pays back; ServiceTitan itself states the platform is not optimized for shops with 3 or fewer technicians, and its per-tech model gets expensive fast below 10 to 15 techs. (2) ServiceTitan implementation never fully landed; you use less than 30 percent of features but still pay for the full suite plus the original implementation fee, which commonly runs $5,000 to $50,000-plus. (3) Strategic shift away from commercial work toward residential one-call-close, where Jobber flat-rate per-plan pricing and lighter workflows fit better. If none of those apply, fix the ServiceTitan rollout instead of switching; a migration does not fix an adoption problem.
Phase 1: Data audit (week 1-2)
Export everything from ServiceTitan: customers, locations, jobs, invoices, service agreements, equipment records, payment records, employees, price book. Audit the export for three things. Duplicates: ServiceTitan installs accumulate duplicate customer records over time, often 5 to 15 percent. Bad emails and phone numbers: clean these now, not after migration. Service agreement state: pause, expire, or migrate each one explicitly. Skipping this audit imports the mess into Jobber and breaks reporting from day one.
Phase 2: Migration (week 3-6)
Migrate in this order, not parallel. (1) Customers and locations first; verify count matches expected after dedup. Jobber Import Clients takes a CSV with one row per property, so a customer with three service addresses becomes three rows, and the client export caps at 1500 rows per file, so split large lists. (2) Equipment records linked to locations. (3) Job history with invoices, last 24 months at minimum; Jobber Import Jobs handles up to 4999 jobs at a time and auto-matches each job to an existing client by name or property address. (4) Active service agreements with billing cycles. (5) Open jobs and scheduled work. Use Jobber CSV import for customers and jobs; equipment and any live two-way sync typically need a Zapier or custom GraphQL API push. Note ServiceTitan API access for Zapier requires The Works or Legacy package. Payments do not migrate cleanly; cards on file are stored as processor tokens tied to ServiceTitan payments, so plan to re-collect cards from customers rather than count on a token migration.
Phase 3: Parallel operations (week 7-9)
Run both systems for two weeks. New jobs go into Jobber. Open ServiceTitan jobs finish in ServiceTitan. Train techs on Jobber mobile app first; dispatchers second; CSRs last. Train each role for 4 hours minimum, with a live shadow shift. Review the dispatch board every morning for the first 14 days; small workflow gaps surface here and are easy to fix.
Phase 4: Cutover (week 10-12)
Set ServiceTitan to read-only the day Jobber goes full-live. Keep the ServiceTitan login for 6 to 12 months for historical lookup; do not cancel the day you cut over. Check your contract first: ServiceTitan agreements are 12-plus months and early termination fees have been reported in the $5,000 to $20,000-plus range, so time the cancellation to your renewal date rather than the cutover date. After 90 days in Jobber with no daily use of ServiceTitan, downgrade ServiceTitan to its lowest tier or cancel at renewal. Archive a full data export before any cancellation, because ServiceTitan API terms prohibit caching pulled content beyond 24 hours, so do the bulk export deliberately while access is live.
Common gotchas
Five recurring failures we see in client migrations. (1) Underestimating service agreement complexity; map every billing edge case before migration day. (2) Trying to keep ServiceTitan integrations live in parallel; pick one source of truth per integration. (3) Skipping CSR training because they "use the phone, not the software"; CSRs have the steepest learning curve. (4) Migrating partial price books; build the Jobber price book fresh from ServiceTitan as a reference, do not import 5 years of accumulated entries. (5) Ignoring marketing tool integration until week 11; rebuild it during phase 2.
Frequently asked questions
How long does the migration really take?
60 to 90 days for shops under 25 techs. 90 to 120 days for shops 25 to 50 techs. Past 50 techs the cost-benefit of switching usually flips back toward staying on ServiceTitan.
Can I migrate cards on file?
In practice, no. Cards on file are stored as encrypted tokens held by ServiceTitan's payment processor, not as raw card numbers you can move. A formal token migration between processors exists but is slow, conditional, and not worth chasing for most shops; customers re-authorizing on Jobber Payments is cleaner. Plan a 2-week customer outreach window during phase 3 to re-collect cards.
What about historical reporting?
Migrate 24 months of job history into Jobber for trend reporting. Keep full ServiceTitan exports as cold storage for older data; you will rarely query it.
Will my ServiceTitan integrations break?
Yes, every one of them. None carry over. Plan to rebuild integrations (QuickBooks Online, marketing tools, call tracking) on the Jobber side during phase 2. Jobber connects QuickBooks Online natively, and the rest typically run through Zapier or the Jobber GraphQL API, so budget a Zapier subscription if you do not already have one. Watch ServiceTitan API rate limits during any sync work; the standard limit is 60 calls per second per tenant.
How does Pineido help with the migration?
We run the migration as a fixed-scope 60 to 90-day sprint. Includes data audit, migration execution, parallel operations support, training, and post-cutover hypercare. Tool-agnostic; we do not resell either platform.
Get operations insights weekly
Join service-business operators who get one actionable insight on ops, automation, and growth every week.
No spam. Unsubscribe anytime.
You’re subscribed! Look for our next issue in your inbox.
That did not go through. Please try again, or email [email protected].
Ready to ship?
Tell us where you are stuck. We will review it and send a focused recommendation within one business day.