I wrote the standard for making websites AI-operable. Learn More
Migration · ServiceTitan to Housecall Pro
Businesses move down as well as up. The operation got smaller, the cost stopped making sense, or the platform turned out to be more system than the business needed. That is a legitimate decision and it is remarkably badly served — every guide on the internet assumes you are migrating the other way.
The honest framing is that this migration is about loss, deliberately chosen. A simpler destination cannot hold everything a richer source recorded. The value of doing it properly is deciding what to drop on purpose, rather than discovering six months later which parts silently did not come.
ServiceTitan is cloud-hosted with structured data and defined export facilities, so extraction is clean and the assessment can produce complete record counts. Housecall Pro is cloud-hosted with a simpler model and its own intake. The engagement is almost entirely a reduction problem: mapping a rich structure onto a flatter one, and documenting precisely what is being set down so the decision is recorded rather than accidental.
Each of these gets its own record count in the assessment and its own line in the reconciliation report. Depth of history is a scope decision made with real numbers in front of you, not an assumption baked into a quote.
Customers and addresses
Customer records with their service addresses, collapsed from the source's customer-and-location model into the destination's flatter structure, with the collapse rules agreed in advance.
Job and service history
Historical jobs with dates, technicians, and work performed, to an agreed depth.
Invoices and open balances
Invoice history and open balances, reconciled against a source-side control report before load. Open balances are the object that must be exactly right.
Estimates
Outstanding estimates, so quoted work in flight is not lost.
Recurring service plans
Agreement terms and billing schedules mapped onto the destination's recurring plan structure, with the entitlement detail that has no home documented explicitly.
Price book, simplified
Services and materials flattened into the destination's structure — a genuine simplification, agreed rather than automatic.
Technicians
Technician records including inactive technicians whose historical work must stay attributed.
Written down before you spend anything, because the alternative is finding out in week six. This list is specific to ServiceTitan to Housecall Pro; the assessment turns it into your list, with record counts attached.
— The equipment-at-location model, in the depth the source held it. This is usually the single biggest loss, and it deserves a direct conversation before you commit — if equipment history is central to how you sell replacements, that is an argument against the move rather than a detail of it.
— Membership entitlement tracking at the same granularity. Terms and billing carry; the visit-by-visit entitlement ledger generally does not have a home.
— Custom checklists, forms, workflows, and dispatch configuration.
— Reporting depth. The source's reporting is a substantial part of what you are paying for there, and it does not have an equivalent. Expect to lose analytical capability, and decide before cutover whether anything you rely on needs an external home.
— Configuration and automation generally. A simpler system does simpler things.
— ServiceTitan internal record IDs. The destination issues its own; anything keyed externally needs the mapping table.
None of this is in either vendor's documentation. It is the category of thing that looks fine in a test load and produces a wrong number in month two, which is why the process puts a full sandbox load and a reconciliation you sign in front of any production cutover.
01
The mapping document on this pair is mostly a list of deliberate losses. That is uncomfortable to read and it is the entire value of the exercise — a business that signs it knows exactly what it traded for the cost saving, and does not spend the following year rediscovering it item by item.
02
Once the source subscription ends, so does your access to the depth you are leaving behind. A complete export, retained as an archive, is what makes the equipment and reporting history answerable later even though it is no longer operational. This is cheap and almost everyone skips it.
03
Historical detail is negotiable on this migration. What customers currently owe is not. Balances are reconciled to the dollar against a source control report and signed off before cutover.
04
If your replacement pipeline is driven by knowing every unit's age and service record, the loss here is strategic rather than administrative. I would rather raise that during the assessment and have you decide against the move than deliver a technically clean migration that quietly damages the business.
01 — 02
A read-only audit of your ServiceTitan instance produces record counts, a risk register, and a fixed quote. Then a field-by-field mapping document you sign before any code runs.
03 — 04
The complete migration runs into a Housecall Pro sandbox — not a sample. You spot-check records you choose, and sign a written reconciliation. If the counts don't tie, we don't cut over.
05 — 06
Scheduled around your calendar with the rollback plan written in advance, followed by 30 days of included corrections for the things that only surface in real use.
Standard Migration in most cases — extraction is clean and the work is reduction rather than reconstruction. Larger operations with substantial agreement bases move upward. The assessment is what makes a fixed migration price possible, and its fee is credited toward the migration if you proceed.
Tier
Scope
Price
Migration Assessment
A read-only audit of your source system.
$1,500 – $2,500
Standard Migration
One source system to one destination.
$6,500 – $15,000
Complex / Multi-Entity Migration
Multiple locations, systems, or long history.
$18,000 – $40,000
Not inherently. If the platform is more system than the business needs, moving down is a rational cost decision and I will help you do it properly. It becomes a bad idea when equipment history and reporting depth are load-bearing for how you generate revenue — and that is a question the assessment answers explicitly, before you commit.
Equipment-at-location depth, membership entitlement tracking, custom workflow configuration, and analytical reporting, in roughly that order of significance. The mapping document lists every item specifically and you sign it, so the losses are chosen rather than discovered.
Yes, and this is the recommendation people most often skip. A complete export retained after cancellation is what lets you answer a question about a unit's history in three years. It costs almost nothing at the time and it cannot be recreated afterwards.
They are reconciled to the dollar against a source-side control report and signed off before cutover. Historical depth is negotiable on this pair; what customers owe today is not.
The assessment is the read-only audit — what data exists, what is extractable, what will be lost, and a fixed-price quote for the migration itself. It is priced at $1,500 – $2,500 depending on scope, fixed before anything starts, and the report is yours whether or not you go further.
Tell me what you're moving. I read every one of these personally and reply within one business day, usually with a couple of specific questions about your source system — the answers change the price, so it's worth asking early.
Nothing is committed by this form. No payment, no contract, no scheduling sequence. It starts a conversation.
If your destination vendor can handle it, I'll say so. Some conversions genuinely don't need an independent migration.
Standard – Complex
Equipment records and service agreements.
Standard
Creating structure that never existed.
Complex
Job costing has no destination.
Every pair
Twenty-odd pairs are written up across seven industries — and the written ones are not the limit of the work. Search the full list, or just ask.
ServiceTitan and Housecall Pro are trademarks of their respective owners. This page describes independent data migration work involving those systems and does not imply any affiliation with, partnership with, or endorsement by either vendor.
Before you give notice on ServiceTitan
The most expensive mistake in this category is losing source-system access before the extraction is done. The assessment is read-only, fixed-price, and yours to keep either way.
I respond personally within 1 business day. No pitch — just a real conversation.