How to Switch from Housecall Pro or Jobber Without Losing Customers

This is a different migration than ServiceTitan

Most 1–25 tech shops are not leaving ServiceTitan. They are leaving Housecall Pro or Jobber because the subscription grew add-ons, the processing rate sits at 2.7–2.99%, and Voice AI is a paid extra. The data path is simpler than ServiceTitan — CSV, not OAuth — and the calendar is usually live in two weeks if you don't try to boil the ocean.

If you are on ServiceTitan, use the API playbook instead. Same cutover idea, different export.

Why shops leave (without the punch-down)

• Per-user add-ons. The advertised plan is for a handful of seats. The fifth or ninth user is where the bill jumps. Flat user-limit math.
• Processing. Housecall Pro publishes 2.99% on emailed invoices and 3.49% on keyed or Amex. Jobber Payments is typically 2.9% + $0.30 on cards. On a $40k/month card book that line is larger than the software. Rate comparison.
• The phone is an extra. Answering and booking after hours is an add-on or a partner on both platforms. If that is the feature you actually need, you are stacking a second vendor on top of the CRM.

Stay if you live in Housecall Pro's marketing suite (review postcards, consumer app) or Jobber's marketplace and the switching cost is real. Leave if you are paying for shelfware and a processing rate you never shopped.

What actually exports

Housecall Pro

In Housecall Pro, Account Settings → Export Data (wording moves occasionally) will generate CSVs for customers, jobs, invoices, and — if you use them — estimates and service plans. Download each file while the account is still active. Do not cancel first.

Jobber

In Jobber, Gear → Data → Data export. Request clients, quotes, jobs, and invoices. Jobber emails a download link, usually within half an hour. Same rule: export while you still pay for the seat.

What carries vs what you rebuild

• Customers and properties. These migrate cleanly via CSV. Dedup on email + phone before you import. Multi-address customers are the records to spot-check.
• Pricebook. Export line items and re-import with the same SKUs so old invoices still make sense next to new ones.
• Open jobs and open invoices. Bring these over or re-enter the ones still in flight. Do not start a job in two systems.
• Paid history. Usually cheaper to keep as a dated CSV (or leave the old account read-only for 90 days) than to force every closed job into the new CRM.
• Recurring plans / service agreements. Rebuild. Intervals, next-visit dates, and what is included almost never map 1:1.
• Cards on file. Never migrate. PCI. Budget a “new payment link, same company” SMS for anyone on autopay.
• Custom forms, automations, review flows. Rebuild on the new primitives, or drop the ones nobody used.

The 14-day cutover

Days 1–3: Empty tenant, real data

1. Start the new platform's trial. Connect Stripe. Add the team and roles.
2. Import customers. Spot-check 25 records — especially multi-property accounts.
3. Load the pricebook and tax codes. Invoice one fake job to yourself and pay it.
4. Turn on SMS templates and the phone / AI if you're adopting one. Test STOP/HELP.

Days 4–7: One tech, real jobs

1. Pick one technician or one job type. New work goes on the new board only.
2. Finish in-flight work in Housecall Pro or Jobber. Do not split a job across systems.
3. Fix whatever breaks — usually taxes, durations, or a missing property note — while the old system is still the safety net.

Days 8–14: The rest of the board

1. Move the remaining techs. Keep the old account read-only for history.
2. Rebuild recurring plans from a printed list, not from memory.
3. Reconcile open A/R. Send the card-on-file SMS to anyone on autopay.
4. Stop creating new work in the old system. Cancel at the end of the billing period, after one clean paid week.

Housecall Pro–specific gotchas

• Marketing suite and review postcards. If those campaigns are actually producing booked jobs, plan a replacement (or keep HCP for marketing only for a month). Most shops discover they were paying for the habit, not the pipeline.
• Consumer financing partners. If you close replacements on in-app financing, confirm the new platform's path — or keep a standalone financing partner — before you cut the estimate flow.
• Price Book add-on. Export it. A lot of the “we can't leave” feeling is a pricebook nobody wants to retype.

Jobber-specific gotchas

• Marketplace integrations. List every connected app (QuickBooks, routing, reviews, phones). Anything mission-critical needs a replacement on day one, not week three.
• Route-heavy days. If Jobber's routing is how you build the morning, test a real Monday on the new board before you move the whole crew. Drag-and-drop is not the same as optimized routes.
• Requests / client hub bookmarks. Customers who book from an old Jobber link will hit a dead end. Put the new booking URL on the website and the Google Business profile the morning you cut over.

How GridBoss handles these imports

Customer CSV import is built in. Jobs, invoices, and payment history from Housecall Pro or Jobber are a mapped import — email a sample export to hello@gridboss.io and the team will tell you what lands automatically vs what you should rebuild. Book a 30-minute migration call if you'd rather walk the files live.