Home services and trades
Exporting job history from Housecall Pro and Jobber
By SourceX Editorial · Updated
Short answer
Exporting job history from Housecall Pro or Jobber usually means pulling customer, job, estimate or quote, and invoice lists into spreadsheets, then handling photos, attachments, notes and messages as separate steps. Export before you cancel or switch, keep the IDs that link each customer to jobs and invoices, and check row counts against the app's own reports.
Key takeaways
- A complete job history is more than the job list: it includes estimates, line items, payments, notes, photos, messages and timesheets.
- Customer, job and invoice IDs are the glue; an export that drops them cannot be stitched back together reliably.
- Photos and attachments are the records most often left behind, so ask the vendor about bulk options early.
- Read the data ownership, export and post-cancellation terms before you cancel a subscription.
- A documented export with counts and dates is useful later for a sale, a migration or a data license.
What does a complete job history include?#
A complete job history in Housecall Pro or Jobber includes every record that connects a customer's first contact to the final payment and any follow-up visit. Most export guides stop at customers and jobs, which is enough to migrate a schedule but not enough to keep the story of the work.
Before exporting anything, list which of these record families your company actually uses. A shop that never used checklists or in-app messaging can skip them, while one that photographs every job has a large attachment archive to plan for.
- Customers, service addresses and contact preferences.
- Requests or leads, including how the customer found you.
- Estimates or quotes, with options offered and which one was approved.
- Jobs and visits, with scheduled and actual times, assigned technicians and status changes.
- Line items and pricebook items used on each job.
- Invoices, payments, refunds and any financing records.
- Job notes and internal notes written by technicians and office staff.
- Photos, attachments, checklists and signed forms.
- Customer messages, texts, emails and any call records.
- Timesheets, service plans and equipment details recorded at each property.
What usually exports cleanly and what gets left behind#
List-style records usually export cleanly, while unstructured records attached to a job are the ones most often left behind. Export options, field coverage and date limits differ by vendor, plan and over time, so treat the table as a checklist of what to confirm in your own account and the vendor's help center, not as a description of either product.
The two products also name the same records differently, which matters when you match files later or merge two companies. Jobber organizes work as clients, requests, quotes, jobs and the visits within each job, while Housecall Pro talks about customers, estimates and jobs. Map the terms once in a short glossary saved with the exports, so anyone reading the files later knows that a quote and an estimate play the same role.
| Record family | Where to look first | Common gap | How to check |
|---|---|---|---|
| Customers and addresses | Customer list export or reports | Multiple addresses per customer flattened into one | Compare customer count with the app's total |
| Estimates or quotes | Reports or export options | Declined options and approval dates missing | Spot-check approved and declined examples |
| Jobs and visits | Job reports filtered by date range | Actual start and finish times missing | Count jobs per year against in-app reports |
| Line items | Detailed invoice or job reports | Only invoice totals exported | Rebuild one invoice from line items |
| Invoices and payments | Financial reports or accounting sync | Refunds and partial payments separated | Tie annual totals to the accounting ledger |
| Notes | Job detail views or detailed reports | Internal notes not included | Open a few jobs and compare to the export |
| Photos and attachments | Vendor support or integration options | No bulk download in your plan | Ask support in writing what is available |
| Messages and calls | Communication logs or connected phone tools | Stored by a separate phone or texting vendor | Identify which system holds them |
A step-by-step export plan#
An export plan runs from the master list outward, so every later file can link back to it. Work in a fixed order and record what you pulled, when, and with which filters.
- Step 1: confirm who has admin access and which modules your company has used over the years.
- Step 2: export customers and service addresses first, keeping every internal ID.
- Step 3: export estimates or quotes, jobs or visits, invoices and payments, in date ranges small enough to avoid truncated files.
- Step 4: export line item detail, not just totals.
- Step 5: collect notes, then plan photos and attachments with the vendor, an integration or a developer using the API if your plan allows it.
- Step 6: find where messages and call records live, which may be a separate phone or texting service.
- Step 7: check counts and totals against in-app reports and the accounting ledger.
- Step 8: store everything read-only in encrypted storage with a short note describing each file.
Keeping records linked after export#
Records stay linked after export only if each file keeps the keys that connect it to the others. Without those keys, an invoice cannot be matched to the job that produced it, and a photo becomes an unlabeled image.
Pay particular attention to photos. Rename or folder them by job number at the moment of download, because recovering that link later is slow and error-prone.
| Link | Key to keep | Common mistake |
|---|---|---|
| Customer to address | Customer ID and address ID | Matching on names, which repeat and change |
| Estimate or quote to job | Estimate or quote number on the job | Exporting only approved estimates |
| Job to invoice | Job number on each invoice | Combining invoices across jobs in one sheet |
| Job to technician | Technician ID, not only name | Renamed or departed technicians losing history |
| Job to photos and notes | Job number in file names or folders | Bulk downloads with system-generated names |
Read your terms before you export or cancel#
Your subscription terms decide who owns the data, what the vendor may do with it, and how long it stays available after you cancel. Read the sections on customer data ownership, the vendor's license to use your data, export rights and deletion after termination before you give notice.
If anything is unclear, ask the vendor in writing how long your account data remains accessible after cancellation and whether attachments can be exported in bulk. Keep the answer, and a dated copy of the terms you read, with your export files.
Illustrative: merging a Jobber shop into a Housecall Pro company#
Illustrative: a fictional HVAC company running Housecall Pro acquires a smaller plumbing shop that runs Jobber. The plan is to move the plumbing crews onto Housecall Pro and close the Jobber account at the end of a transition period.
The integration lead exports the plumbing shop's customers, quotes, jobs, visits, invoices and payments with all IDs, then confirms with support how to retrieve job photos. A mapping sheet pairs old Jobber IDs with new Housecall Pro customer records, and the original exports are archived untouched.
When the Jobber account closes, nothing is lost. Warranty questions on older plumbing jobs can still be answered from the archive, and the combined company has a single, documented history it can use for planning, a future sale or a data license.
What a documented export is worth beyond migration#
A documented export is useful long after the migration ends. Buyers in a sale ask for job and invoice history that reconciles to the ledger, and AI developers who license operational records ask where each file came from and how it was produced. The Data & Trust Alliance's Data Provenance Standards, for example, organize dataset metadata into three groups, Source, Provenance and Use, for selecting data for AI model training.
SourceX starts with a fit check that collects metadata only, such as systems, years and record families. If a company proceeds, the export log becomes part of the provenance section of the SourceX Evidence Packet, alongside licensing rights, permitted use, the privacy record and release authorization.
Frequently asked questions
Do I lose my data if I cancel my subscription?
It depends on your vendor's terms. Many software providers keep account data for a limited period after cancellation and then delete it. Export everything you need before giving notice, and ask the vendor in writing how long your data remains retrievable.
Can I download all job photos at once?
Options vary by vendor and plan. Some companies use a vendor-supported bulk option, an integration or the API, while others download job by job. Ask support early, because photo archives are often the largest and slowest part of an export.
Is an API export better than spreadsheet exports?
An API can reach more fields and keep links between records, but it needs a developer and may be limited to certain plans. Spreadsheet exports are faster to start. A common split is spreadsheets for core lists and the API or an integration for attachments and detail.
How far back can I export job history?
Usually as far back as your company has used the system, subject to any report date limits. History from before you joined lives in the previous system, so check whether that archive still exists and export it too.
What format should I keep the exports in?
Keep the original spreadsheet files, the photos and attachments in folders named by job number, and a short note that describes each file, its date range and filters. Store the set read-only in encrypted storage with a separate backup.
Sources
- The Data & Trust Alliance's Data Provenance Standards (version 1.0.0 specification) define dataset metadata in three groups: Source, Provenance and Use, needed to enable proper dataset selection for AI model training. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.