Migrating your pricebook to ServiceTitan

You’re moving to ServiceTitan. Good call. It’s the platform that runs the whole business, and once your book is set up right inside it, your techs present cleaner and your job costing finally holds.

Here’s the one thing that decides whether the move pays off: do not drag your old pricebook in as-is. The migration is the cheapest moment you will ever have to fix the book, because you’re rebuilding it anyway.

Is this you? This is worth getting right if you’re coming to ServiceTitan from Housecall Pro, Jobber, FieldEdge or a spreadsheet, if you’ve been told to “just import the old book,” or if the data export looks nothing like what ServiceTitan expects.

What actually moves when you migrate

A pricebook isn’t a flat list of prices. It’s a set of relationships, and most of those relationships do not survive an export.

What comes across cleanly:

• Your service names and prices, as a flat list.
• Your material costs, if the old tool tracked them.
• A rough sense of your categories, usually flattened or renamed.

What does not export, and has to be rebuilt inside ServiceTitan:

• The links between a service and the materials and equipment it consumes.
• Your tiered options, the good-better-best sets a tech presents.
• Proposal layouts and how options are grouped on the screen.
• Any pricing logic, dynamic pricing and price rules included.

Flat lists travel. Structure doesn’t. That gap is the whole job of a migration.

Why you should not import your old book as-is

ServiceTitan is deliberately flexible. It hosts your pricebook and presents it beautifully, but it doesn’t decide how that book should be built to sell. That structuring is on you, and it’s exactly the work that makes the move worth it.

So here’s the trap. If you lift and shift, every problem you had in the old tool walks in the front door with you:

• Items priced at or near cost that quietly lose money on every ticket.
• A labor rate that’s really a wage with a round number on top, so every labor-driven price is too low.
• Duplicate services and overlapping categories that became a maze in the old app and stay a maze here.
• Service names a customer can’t read on a tablet in their kitchen.

A stronger platform doesn’t fix a weak book. It just presents the weak book more clearly.

The old book is the problem, not the old software and not ServiceTitan. The switch is your one clean shot to leave that book behind.

The order to migrate in

You rebuild a migrated book in the same order you’d build one from scratch, because each step rests on the one before it. (The full order is here.)

1. Categories first. Map your old categories onto a clean, unique ServiceTitan category skeleton. Merge the overlaps now, while it’s a list, not after you’ve loaded a thousand services under them.
2. Services, on a real loaded labor rate. Bring in the services you actually sell, and build their prices on a true, fully burdened cost of an hour, not the wage-plus-cushion number you carried over. (How to get that number right.)
3. Materials and equipment, linked. Attach the parts each service consumes so cost rolls up and job costing means something. This is the connective tissue the export dropped, and it’s where a migration earns its keep.
4. Tiered options. Build good-better-best on the jobs that carry them, where the tiers answer different homeowner questions, not just different prices.
5. Proposals. Lay out how options are grouped and presented, so the tech presents instead of configuring in the driveway.

Why this order matters: build tiers before you’ve linked equipment and you get option sets with nothing real underneath them, just prices floating in the air. Set prices before you’ve fixed the labor rate and you re-price everything twice.

The common pitfalls

These are the ones that bite during a migration, in roughly the order shops hit them.

• Lift-and-shift everything. The single biggest one. You inherit the old mess and waste the one clean chance to fix it.
• Trusting the export’s structure. Housecall Pro, Jobber, FieldEdge and spreadsheets each export in their own shape. The data is useful as a reference for what you sell. The structure is not ServiceTitan’s structure, so don’t expect it to map one-to-one.
• Importing in one giant pass. Big single imports surface a wall of errors at once. Import in clean, smaller passes so a bad row doesn’t take the whole file down. (The import errors to expect, and how to clear them.)
• Skipping the links. Loading services and prices but never linking materials and equipment. The book looks done and your margins are a guess.
• Carrying the bloat. Dragging along every service you’ve never sold because deleting feels risky. A focused book migrates faster and gets used in the field.

DIY or done-for-you

Both are real options. It comes down to whether you have the hands and the time, because the migration window is also when you’re learning a new platform.

Do it yourself if you’ve got someone who knows your trade and your numbers cold, time to sit with categories, pricing, linking and tiers, and the patience to import in passes and clear errors as they come. The order above is your map.

Have it done for you if you’d rather your team learn the new book than build it. You hand over the old export, and the structuring, the part ServiceTitan leaves to you, comes back done. We take that heavy load off you so you stay in the field, and the book that lands in ServiceTitan is built to present from day one. That’s the done-for-you build.

Either way, start by seeing what you actually have. The free Pricebook Health Audit reads your current book and flags the at-cost items, missing links, duplicates and thin names, so you know exactly what to leave behind in the move instead of carrying it across.

The platform’s the easy part. The book is the work, and the move is the moment to get it right. For the full picture of what a book that sells looks like inside ServiceTitan, start with the complete guide.