Switching from Housecall Pro, Jobber, Kickserv & Zenbooker | FieldCamp

Step-by-step guide to switching from Housecall Pro, Jobber, Kickserv, or Zenbooker to FieldCamp with bulk migration of clients, jobs, and invoices.

Under the hood — the FieldCamp data model shows how every record connects, how you can customize it, and how it maps to your trade.

Switching from Housecall Pro, Jobber, Kickserv, or Zenbooker to FieldCamp is designed to be fast, predictable, and low-risk. This guide walks you through preparing your data, running the bulk migration, and verifying everything once you land inside FieldCamp. Whether you are a solo operator or a 50-tech crew, you can be up and running with your historical clients, jobs, and invoices in a single afternoon.

Why teams switch to FieldCamp

Most teams move to FieldCamp because they want the modern automation, AI-powered dispatching, and unified inbox they cannot get from legacy platforms. Common reasons we hear:

They want true AI-driven dispatching instead of manual drag-and-drop scheduling.
They are tired of paying for add-ons that should be standard (texting, online booking, route optimization).
They want a single workspace where estimates, invoices, and payments live alongside the calendar and CRM.
They need real automation through a workflow builder, not just templates.

The bulk migration tools described below are available on all paid plans. See Plan and billing for details.

What gets migrated

FieldCamp supports bulk import from Housecall Pro (HCP), Jobber, Kickserv, and Zenbooker. The following record types are migrated automatically when you upload the source export files:

Clients & contacts

Customer names, addresses, phone numbers, emails, notes, and tags.

Jobs & visits

Past and upcoming jobs, visit schedules, line items, and statuses.

Invoices & payments

Outstanding and paid invoices, including dates, amounts, and references.

Products & services

Your price book, services, and inventory items where available.

Custom fields, file attachments, and recurring job schedules are also mapped where the source platform exposes them in its export.

Before you start: pre-migration checklist

A clean migration starts with a clean source. Spend 15 minutes on these items before you run the import.

Create your FieldCamp account

Set up team members

Invite techs and dispatchers so jobs can be reassigned to the right owner during import. See adding and managing team members and review roles and permissions before assigning access.

Decide on a cutover date

Pick a date to stop creating jobs in the old system. Most teams choose a Friday so they have the weekend to verify data.

Export from your current platform

Generate fresh CSV/JSON exports for clients, jobs, and invoices from Housecall Pro, Jobber, Kickserv, or Zenbooker.

Back up attachments

Download a copy of important client documents and job photos. FieldCamp imports references, but keeping originals locally is good insurance.

Exporting from your current platform

Each platform exposes exports differently. Use the path below that matches your current tool.

Housecall Pro (HCP)

In HCP, go to Account Settings → Export Data. Generate exports for Customers, Jobs, and Invoices. Download each CSV when ready. If you use HCP Estimates and Service Plans, export those as well.

Jobber

In Jobber, go to Gear icon → Data → Data export. Request exports for Clients, Quotes, Jobs, and Invoices. Jobber emails a download link when the file is ready (usually within 30 minutes).

Kickserv

In Kickserv, navigate to Settings → Imports & Exports. Run exports for Customers, Opportunities, Jobs, and Invoices. Save each file as a CSV.

Zenbooker

In Zenbooker, go to Settings → Account → Export data. Generate the Customers, Bookings, and Invoices exports.

Always export with the most-detailed option available. FieldCamp can ignore columns it does not need, but it cannot create columns that were never exported.

Running the bulk import in FieldCamp

Once you have your export files, the migration runs inside FieldCamp's import wizard.

Open the import tool

From the sidebar, open Settings → Data Import. You will see a tile for each supported platform. If you cannot find it, the settings overview lists every menu in FieldCamp.

Choose your source platform

Pick Housecall Pro, Jobber, Kickserv, or Zenbooker. The wizard tailors its field mapping to that platform's export format.

Upload clients first

Always import clients before jobs and invoices so relationships link correctly. Review the field mapping screen and adjust if needed.

Upload jobs and visits

Next, upload your jobs export. FieldCamp links each job to the matching client by email or phone. Multi-day jobs are converted to multi-day job records.

Upload invoices and payments

Finally, upload your invoices file. Status (Paid, Partial, Outstanding) is preserved, and Stripe payment references are kept for reconciliation.

Review the import summary

The wizard shows a summary of created records, skipped rows, and any rows that need manual review. Click into any flagged row to fix and retry.

Do not run the same import file twice. FieldCamp uses email and phone to detect duplicates, but importing the same file two times can still create extra job records. If you need to re-run an import, use the Undo last import action first.

Mapping fields between platforms

FieldCamp's import wizard auto-maps the most common fields. Use this table when something looks off.

Source field (HCP / Jobber / Kickserv / Zenbooker)	FieldCamp field
Customer / Client / Contact	Client
Job / Work Order / Booking	Job
Line items / Services	Products & services
Tags / Labels / Categories	Client tags
Quote / Estimate	Estimate
Invoice / Bill	Invoice
Assigned employee / User	Team member

If you used custom fields in your previous tool, create matching custom client fields in FieldCamp before importing so the data has somewhere to land. For non-standard records like equipment or properties, consider custom objects.

After the import: verification checklist

Take 30 minutes after the import to confirm a clean cutover.

Open the clients table view and spot-check 10 random clients.
Open the dispatch calendar and confirm upcoming jobs show on the right days and right techs.
Run an outstanding invoice analytics report and compare totals to your old system.
Confirm your price book and services carried over with correct pricing and taxes.
Test that a brand-new job, estimate, and invoice can be created end-to-end.

Run both systems in parallel for one week. Keep the old tool read-only and use FieldCamp for all new jobs. This gives you a safe rollback path while your team adjusts.

Turning on automation and AI features

Once your historical data is in, this is the right time to enable the features that make FieldCamp different.

Configure AI Dispatcher so new jobs get smart routing.
Set up online booking and point your website to the new widget.
Build your first workflow automation for follow-ups, review requests, and reminders.
Connect Stripe for online payments and turn on auto-pay where appropriate.
Browse the full add-ons catalog to enable Job Forms, Timesheets, Calls, and other modules you used in your old platform.

Cancelling your old subscription

Once you are confident in FieldCamp (typically 7-14 days after cutover), cancel your old subscription. We recommend keeping a read-only export of your old system in cloud storage for at least 12 months in case you need to reference legacy records for tax or warranty purposes.

Troubleshooting

My clients imported but their jobs did not

Jobs only attach to a client if the email or phone number matches exactly. Re-export your jobs file, ensure every row has a populated email or phone column, and re-run only the jobs step.

Some invoice totals are off by a few cents

This is usually a tax-rounding difference between platforms. Open tax settings and confirm your tax rates exactly match the old system. Re-importing with corrected taxes is not required — adjust new invoices going forward.

My recurring jobs did not come over

Some source platforms do not include recurring-job rules in their exports. Recreate them inside FieldCamp using a contract and terms attachment or by setting up the job as a recurring job or multi-day job.

Team member assignments are wrong

If technicians had different names or emails in your old system, FieldCamp may assign jobs to an unassigned bucket. Re-assign in bulk from the calendar or filter the jobs list by "Unassigned" and assign by region.

Duplicate clients appeared

This usually means the same person was stored under two different emails in the old tool. Use the client merge tool from the client detail page to combine them.

FAQs

How long does a typical migration take?

Most small teams (under 1,000 clients) are fully migrated in under two hours. Mid-sized teams typically complete migration in a single workday including verification.

Can FieldCamp pull data directly from Housecall Pro or Jobber via API?

For most teams, the CSV-based bulk import is faster and more reliable. If you have a large dataset (10,000+ jobs) and want a guided migration, contact support to discuss assisted onboarding. Developers can also use the FieldCamp API to push records programmatically.