Most HVAC contractors running 20 to 100 technicians keep their working life in one platform: ServiceTitan, Housecall Pro, FieldEdge, Jobber, Service Fusion or Successware, with accounting in QuickBooks or something like it and call records in the phone system. Getting years of that out in a form a buyer can use is less about clicking export and more about doing things in the right order.
This post does not describe any platform’s export screens. They differ by plan and they change. Ask your account manager what your plan allows, and get the answer in an email.
What should you read before exporting anything?
Your subscription agreement. Look for three things.
Who owns the data. Most agreements say the customer owns what it enters. You want to find that sentence and keep a copy.
What you may do with exports. Some agreements limit use of exported data, or data taken through an API, to operating your business. Licensing it to a third party may need the vendor’s agreement. If the wording is unclear, ask.
Limits on extraction. Rules against scraping, rate limits and API terms can decide how records are allowed to leave. A buyer that proposes connecting to your software directly needs to fit inside them.
While you have the contracts out, read two more: any commercial service agreement that says who owns records about a client’s buildings, and any franchise agreement that covers your systems.
Which records should you plan to pull?
Think in record types, not in screens. A buyer’s scoping call will ask for some of these and not others.
| Record type | Usually found in | Linked by |
|---|---|---|
| Work orders and technician notes | Field service platform | Job number |
| Dispatch and schedule history | Field service platform | Job number, technician code |
| Estimates and proposals | Field service platform, pricebook | Job number, estimate number |
| Invoices and payments | Platform and accounting software | Invoice number |
| Equipment records | Field service platform | Location and equipment ID |
| Maintenance agreements | Field service platform | Customer code |
| Call booking records | Phone system, CSR notes | Date, time, job number |
The links matter as much as the records. A work order that can be joined to its estimate, invoice and equipment record is worth more than four separate piles.
In what order should the work happen?
Take your own complete copy first
Export everything you are entitled to, every record type, every year, and store it somewhere you control. This is your archive. It never goes to a buyer as it stands. If you ever change platforms, you will be glad of it.
Write a one-page description
For each file: what it holds, the date range, the row count, and what each column means. Buyers ask for this early, and writing it shows you where the gaps are.
Wait for a buyer to scope
The buyers publish what kinds of records they take. Nyne’s list is the most specific for a service business, from service histories and dispatch through to estimates and invoices. micro1 and Scale AI describe operations, CRM, ERP and support records more generally. None tells you the years or fields it wants before a conversation, so preparing a full delivery up front is effort you may waste.
Remove personal details yourself
Customer names, service addresses, phone numbers, emails, gate codes in the notes, payment details. Replace customer and technician identities with codes so records still link. Buyers clean data too (Scale AI on your own systems, before anything moves), but the records are yours and so are the customers.
Deliver only under a signed license
The agreement should say what is delivered, how, and how acceptance works. Deliver that way and no other.
What should you never do?
Give a buyer your login. Scale AI’s page rules out credentials and raw system access, and nobody on our list asks for a password. Share a sample containing real customer details “just to show what it looks like”. Send exports to anyone, ourselves included, before there is an agreement. Company records have no business coming to us, and we turn them away.
Does this need IT?
For a one-off historical export, usually not; the office manager who runs your reports can do most of it. For a recurring feed, or anything through an API, one person should own it who understands both the contract and the system. Before any of that, it is worth knowing whether you clear a buyer’s floor at all. The homepage covers how to sell HVAC data from the start, and the export checklist page puts the contract questions in one table.
Get the order right and the export is the easy part.