Migrating from ServiceTitan

01Pre-requisites

ServiceTitan migrations have a few prerequisites that don’t apply to other platforms:

1. Active ServiceTitan API access. Your ServiceTitan account needs to be on a tier that includes API access. If you’re on the smallest plan, you may need to contact ServiceTitan support to enable it.
2. An admin role in ServiceTitan. The OAuth handoff requires admin-level permissions to authorize Conduit’s read access.
3. Tenant ID. Conduit asks for your ServiceTitan tenant ID during the connect step. You can find it in your ServiceTitan URL (the subdomain) or in Settings → Integrations.

If any of these aren’t in place, the wizard will prompt you with the specific blocker. Most fixes are 5-10 minutes; getting API access enabled can take a day or two.

02Connect to ServiceTitan

1. Open Conduit’s migration wizard at Settings → Import Data → Import from Another Tool.
2. Click the ServiceTitan tile.
3. Click Connect Account. A new window opens to ServiceTitan.
4. Sign in with your ServiceTitan admin account.
5. ServiceTitan asks you to authorize Conduit’s read access. Confirm.
6. Enter your ServiceTitan tenant ID when Conduit prompts (if not auto-detected).
7. The popup closes. Conduit’s wizard advances to Pull Data.

03What transfers

Conduit pulls 6 data types from ServiceTitan:

1. Customers. Names, contact info, addresses, customer type (residential/commercial), tags, lifetime value notes.
2. Locations. ServiceTitan’s “Location” model attaches to customers. Each location becomes either the primary address or a secondary record on the customer.
3. Jobs. Work orders, scheduled date and time, technician assignment (mapped by email if your Conduit team includes the same emails), status, type.
4. Invoices. Line items, totals, payment status, customer link, issue date.
5. Estimates. Imported as Conduit bids.
6. Pricebook items. Service codes, descriptions, units, list price. Cost is pulled when ServiceTitan exposes it.

Each record gets a servicetitan_external_id for re-import idempotency.

04What doesn’t transfer

ServiceTitan is the most feature-rich source, so the most things don’t transfer one-to-one:

• Membership/recurring service plans. ServiceTitan’s membership model (annual contracts, scheduled visits) flattens. Recreate as Conduit recurring schedules.
• Dispatch board state. Your dispatch board doesn’t transfer; recreate scheduling in Conduit’s calendar.
• Inventory tracking. ServiceTitan’s truck inventory and warehouse data don’t transfer. Conduit handles inventory differently (committed cost on POs).
• Custom forms. ServiceTitan supports per-job custom forms. These don’t have a Conduit equivalent.
• Marketing campaign data. Lead source transfers as a tag on the customer; campaign analytics don’t.
• Call recordings, audit logs. Operational data, not data records, doesn’t transfer.

05After import

ServiceTitan migrations need extra verification because of the volume:

1. Run a customer count check. ServiceTitan total customers should match Conduit’s count (within a few because of duplicate-detection logic).
2. Check 10 random customers. Verify name, address, lifetime spend roughly matches.
3. Verify invoice totals. Pick three large customers; their lifetime invoice totals should match.
4. Reconnect Stripe in Settings → Payments.
5. Re-create memberships. Anything you sold as an annual or recurring plan needs a Conduit Recurring Schedule.
6. Update technicians. Email addresses on your Conduit team should match the email addresses on ServiceTitan technicians for job assignment to flow through.

Run both systems in parallel for at least a week before deactivating ServiceTitan. The volume makes it especially worth verifying.