Housecall Pro and ServiceTitan are the two most common platforms field-service contractors leave when they switch to Exoserva. Both let you export your data, but each has its quirks — different schemas, different export tools, different gotchas. This guide is the competitor-specific specifics: what to click in HCP / ServiceTitan, what their CSVs look like, and where the friction points hide. The general migration playbook lives in Migrating from Another Platform — read that first, this guide second.
Estimated reading time: 12 minutes
Before You Begin
- Read Migrating from Another Platform for the universal playbook
- Owner / Admin access on your old platform (HCP / ServiceTitan), and Owner on Exoserva
- A 2-4 week parallel run window scheduled
- (Optional) A technical contact at HCP / ServiceTitan support to help with bulk export — both vendors have data-portability obligations but the support quality varies
Migrating from Housecall Pro
Where to find the export tool
In HCP: Settings (gear icon) → Account → Data Export. As of 2026, HCP supports CSV export for:
- Customers (with notes, tags, addresses)
- Jobs (with line items, status, technician)
- Invoices (with payment history)
- Estimates (with status, sent dates)
Equipment/Assets and Inventory are not in the standard export — if you’ve used those, file a support ticket asking for an extended export. Most HCP reps will provide one; budget 2-3 business days.
HCP CSV peculiarities
Three things to know about HCP exports:
- Phone numbers are formatted inconsistently — sometimes
(555) 123-4567, sometimes555-123-4567, sometimes5551234567. Run a normalization pass in a spreadsheet before importing into Exoserva (Exoserva’s importer is permissive but normalized data is cleaner). - Customer notes are HTML-escaped —
&instead of&, line breaks as<br>. Run a find/replace pass to clean these up before import. - Job line items are stored on a separate sheet — HCP exports jobs in one CSV and line items in another, joined by job ID. Exoserva’s importer expects them combined; you’ll need to merge them in Excel using VLOOKUP or a Python script before import.
HCP-to-Exoserva field mapping
| HCP field | Exoserva field | Notes |
|---|---|---|
first_name + last_name |
Customer Name |
Concatenate for individuals; B2B has company_name |
primary_phone |
Phone |
Normalize format |
primary_email |
Email |
|
address |
Service Address |
HCP has one address per customer; Exoserva supports multiple via Properties |
tags |
Tags |
Comma-separated; Exoserva accepts the same format |
notes |
Notes |
Strip HTML before importing |
customer_since |
Customer Since |
Date format YYYY-MM-DD |
HCP gotcha: Recurring services
HCP’s Recurring Services don’t have a clean Exoserva equivalent. Map them to Preventive Maintenance Schedules (guide — currently on hold; see your Account Manager).
For now: export the recurring schedule definitions as a separate CSV, recreate them as standard jobs with a “recurring” tag and a calendar reminder. When PM Schedules ship, migrate properly.
HCP gotcha: Online Booking
HCP’s online booking widget (your customer-facing booking page) doesn’t migrate. You’ll set up Exoserva’s booking page from scratch — the URL changes, so update your website / Google Business Profile / Yelp listings on cutover day.
Tip: Set up the Exoserva booking page 2-3 days before cutover, test it from your phone, then swap the link on your website on cutover day. Pre-tested redirects beat day-of fire-fighting.
HCP timeline expectation
A typical 1-truck HCP shop migrates in 2-3 weekends of part-time work. A 5-tech shop with 5 years of history needs 3-4 weeks of part-time plus 1-2 days of full-time on cutover.
Migrating from ServiceTitan
Where to find the export tool
ServiceTitan has more granular export capabilities than HCP, but the interface is more complex. Settings → Reports → Export offers:
- Customer Data (split into Tenants / Locations / Equipment)
- Job History (with extensive metadata)
- Invoice and Payment History
- Pricebook
- Memberships (recurring service contracts)
ServiceTitan’s three-tier customer model (Tenant → Location → Customer) doesn’t map 1:1 to Exoserva’s two-tier (Customer → Property). Expect manual mapping work.
ServiceTitan CSV peculiarities
- Customer/Tenant/Location — for residential customers, Customer and Tenant are usually the same person. For commercial / property management, they differ. Map carefully.
- Equipment is well-tracked — ServiceTitan stores model, serial, install date, photos for installed equipment. This data is gold; migrate it cleanly.
- Pricebook is hierarchical — categories → service types → services. Exoserva’s Price Book is flatter. Expect to flatten the hierarchy or accept some loss of structure.
- Membership data — ServiceTitan’s Membership is a sophisticated recurring-revenue product. No clean Exoserva equivalent yet — track in a spreadsheet for now or build custom workflows (Workflow Builder).
ServiceTitan-to-Exoserva field mapping
| ServiceTitan field | Exoserva field | Notes |
|---|---|---|
customer.name |
Customer Name |
|
customer.email, customer.mobile |
Email, Phone |
|
location.address |
Property → Service Address |
One Customer can have many Properties; ServiceTitan locations map to Properties |
equipment.* |
Asset |
Strong field correspondence; mostly direct map |
job.summary |
Job Title |
|
job.business_unit |
(skip or use Tag) |
No direct equivalent; Exoserva uses Service Type |
pricebook_service.code |
Price Book entry name |
ServiceTitan gotcha: Custom Forms
ServiceTitan supports custom forms attached to jobs (e.g. “Maintenance checklist” with 30 fields). Exoserva uses a simpler tagging system. Three options:
- Convert forms to Notes — flatten the form data into a free-text Notes field on the migrated job
- Convert key fields to Tags — turn the most-used custom fields into Tags
- Wait for Custom Forms parity — track in feature requests, migrate when shipped
Option 1 is the most common — preserves the data in human-readable form, just loses the structure.
ServiceTitan gotcha: Tech-specific permissions
ServiceTitan has fine-grained permissions per technician (which forms they can see, which jobs they can edit). Exoserva uses Roles + Approval Levels (R-Levels) which are simpler. Expect to:
- Map 30+ specific permissions onto 5-8 roles
- Use Approval Levels for any “this tech can sign off up to $X” rules
- Custom permissions that don’t fit get dropped — most contractors find they had over-engineered their old permission model
ServiceTitan timeline expectation
A typical 5-tech ServiceTitan shop migrates in 3-5 weeks of part-time work. A 20+ tech operation needs 6-10 weeks plus 2-3 days of full-time on cutover.
Side-by-side: which is harder
Both platforms support exit migration, but the effort distribution differs:
| Aspect | HCP | ServiceTitan |
|---|---|---|
| Customer data export | Easy | Easy |
| Job history export | Easy | Easy |
| Equipment / Asset data | Often missing | Comprehensive |
| Recurring services / Memberships | Manual recreation | Manual recreation |
| Permissions migration | Light (HCP simpler) | Heavy (over-engineered) |
| Custom forms | None to migrate | Manual flattening |
| Pricebook complexity | Light | Heavy |
| Estimated effort (5-tech shop) | 3-4 weeks | 6-8 weeks |
If you’re moving from ServiceTitan, budget more time, and consider hiring a migration consultant for the price book + permissions work specifically.
Common mistakes
Three patterns that bite contractors during HCP / ServiceTitan migration:
- Trying to migrate “everything” — you don’t need 8 years of completed jobs. Last 24 months is enough; archive the rest in cold storage.
- Underestimating the price book work — both old platforms accumulate hundreds of services / pricebook entries. Migrating means re-evaluating each. Most contractors find 30-40% can be deleted entirely.
- Cutting over before testing the booking flow — your customer-facing URLs change. Test before flipping. Lost weekend bookings during a failed cutover are real revenue.
Getting help
If you hit a snag the universal playbook doesn’t cover:
- HCP API access — for >5 years of data, the API is faster than the export UI; HCP support can grant API keys
- ServiceTitan API — same; their API is well-documented and rate-limited but usable
- Exoserva migration team — for tier customers, the migration team can run the CSV-cleaning + mapping pass for you (white-glove option)
What’s Next?
- Migrating from Another Platform — universal playbook
- Setting Up Your Price Book — the highest-effort migration step
- Roles, Permissions, and Security — permissions mapping
- Equipment and Asset Tracking — easy migration target if you’re coming from ServiceTitan
Need help? Post in the Tech Support category or contact support@exoserva.com.