Housecall Pro is one of the most common platforms our customers migrate from. Conduit pulls 5 data types from your Housecall Pro account: customers, jobs, invoices, estimates, and pricebook items. Authentication is via API key, which you copy from your Housecall Pro account settings and paste into Conduit’s migration wizard.
This guide walks the full migration end-to-end: getting your API key, connecting, what transfers cleanly, common gotchas, and what to verify after.
01Get your Housecall Pro API key
Log into your Housecall Pro account in a browser tab. The API key lives in your account settings (the exact menu name has changed a few times across Housecall Pro UI versions; look for “API,” “Integrations,” or “Developer”).
- Open Housecall Pro in a separate tab from Conduit.
- Navigate to Settings → API & Integrations (or the closest equivalent in your version).
- Generate a new API key if one doesn’t already exist. Copy it to your clipboard.
- Keep the tab open in case you need to regenerate the key.
02Connect to Conduit
Switch back to Conduit. Open the migration wizard at Settings → Import Data → Import from Another Tool.
- Select Provider. Click the Housecall Pro tile.
- Connect. A form asks for your API key. Paste the key you copied. Click Connect.
- Conduit validates the key and advances to Pull Data.
If the key is invalid or revoked, the wizard shows an error. Re-copy the key from Housecall Pro and try again.
03What transfers
Conduit pulls 5 data types from Housecall Pro:
- Customers. Names, emails, phones, addresses, customer type, notes.
- Jobs. Title, description, scheduled date and time, technician assignment (mapped by email if your Conduit team includes the same emails), status.
- Invoices. Line items, totals, paid/unpaid status, customer link, issue date.
- Estimates. Same shape as invoices, used as the source for Conduit bids.
- Pricebook items. Name, description, unit, price. Cost is not pulled if Housecall Pro doesn’t expose it on the API.
Each record gets a housecall_pro_external_id so re-importing later updates rather than duplicates.
04What doesn’t transfer
Some Housecall Pro features don’t have a Conduit equivalent or aren’t on the public API. Plan for these manually:
- Job photos. Conduit has photo upload, but Housecall Pro photos are not bulk-pulled. Re-attach important ones manually.
- Custom fields. Housecall Pro supports per-account custom fields. These don’t map cleanly to Conduit’s customer or job models. Capture in notes if needed.
- Recurring schedules. Pulled as a one-time job, not a recurring template. Recreate the recurring schedule in Conduit if you need it.
- Payments history. Imported invoices show their paid/unpaid status, but the individual payment records (transactions, refunds) don’t transfer. Stripe Connect history is separate from your Housecall Pro Stripe account.
- Time entries. Conduit’s time tracking starts fresh after migration.
05After import
Once the wizard finishes, verify before going live:
- Spot-check 5-10 customers. Open them in Conduit, confirm contact info and address are correct.
- Verify totals. Look at one of your larger customers. Total spent should roughly match Housecall Pro’s lifetime revenue figure for them (small differences are expected because of date-range and tax handling).
- Reconnect Stripe. Conduit handles payments through your own Stripe Connect account; Housecall Pro’s Stripe relationship doesn’t carry over. Connect Stripe in Settings → Payments.
- Invite your team. Each technician needs their own Conduit login; team membership doesn’t transfer with the data import.
- Update your customers about the change if you send invoice reminders by SMS or email. The “from” sender changes once you move to Conduit.
If something looks wrong, your Housecall Pro account is untouched. You can compare the two side by side before deactivating the Housecall Pro subscription.