Switching field service software: what to do with old job history

What counts as job history in a field service system?#

Job history in a field service system is the chain of records built around every visit, not just the list of completed jobs. ServiceTitan, Housecall Pro, Jobber and FieldEdge use different names, but the shape is the same: a customer and service location at the top, equipment under the location, and jobs that connect to both.

What makes that history useful is the connection between records. A job record alone says a technician went to an address. The same job tied to the call that booked it, the options the customer declined, the repair they chose, the invoice and the callback that followed tells you how your business actually works.

• 1Customers, service locations and contacts.
• 2Equipment and installed base: make, model, serial number, install date and warranty status.
• 3Jobs or work orders with job types, statuses, technician assignments and timestamps.
• 4Technician notes, checklists, forms, photos and signed documents.
• 5Estimates with every option presented and the option that was sold.
• 6Invoices, payments, refunds and open balances.
• 7Memberships and service agreements with their visit schedules.
• 8Call logs, recordings and text threads tied to bookings.

Your options for old job history, and what each one breaks#

The options for old job history are to migrate the active records, import history into the new platform, archive the full history read-only, or review that archive for value, and each choice breaks different links. Most COOs combine migrating active records with a full archive, then decide later whether the archive deserves a closer review.

The table shows what moves and what you lose under each choice. Read it alongside the new vendor's import templates, because the templates decide which fields have somewhere to land.

Which links break when job history moves?#

The links between records break far more often than the records themselves. Import tools in most field service platforms are built around flat files, one sheet for customers, one for locations, one for equipment, and a job import tends to bring the job header while leaving behind what hung off it.

The fix costs little if you plan for it. Every export should carry the old system's internal IDs for customers, locations, jobs, estimates, invoices and equipment, and a crosswalk file should map old customer and location IDs to the new ones.

• 1Job to invoice: invoice numbers survive, but the job reference becomes free text or disappears.
• 2Job to equipment: service history no longer shows on the unit a technician is standing in front of.
• 3Estimate to sold job: you lose which option the customer chose and which ones they declined.
• 4Notes and forms to job: long notes get truncated and structured checklists get flattened into text.
• 5Photos and attachments: files stay in the old vendor's storage, and links stop working when the account closes.
• 6Calls and texts to booking: logs and recordings usually stay with the phone or messaging provider.

The export sequence to finish before you cancel#

The export sequence should be finished before cutover, because access to an old platform usually narrows once the subscription ends and the team is busy learning the new system. Read your current agreement for data return terms and any post-termination access window, and ask the vendor in writing which export formats and history limits apply to your plan.

Default report views can quietly cut history short. ServiceTitan's migration guide for FieldEdge says to set every filter at the top of the Invoices tab to All before exporting, so the file holds all invoice data rather than only the previous six months, and its Housecall Pro guide suggests running a jobs report in one-year batches if a full-range export errors. Whatever platform you leave, check the date range and filters on every export before you trust it.

Assign one person to own the sequence. In many companies that is the office manager or controller, with the COO signing off on completeness.

• 1Step 1: list record families and years of history in the old system, with record counts for each.
• 2Step 2: request a full data export or database backup from the vendor and ask exactly what it includes.
• 3Step 3: run your own report exports for jobs, estimates, invoices, equipment and agreements, with internal IDs as columns.
• 4Step 4: download photos, attachments and signed forms in bulk, in folders named by job or invoice ID.
• 5Step 5: export call logs, recordings and text threads from the phone or messaging provider.
• 6Step 6: compare record counts against the old system and trace a sample of jobs end to end.
• 7Step 7: store two copies in company-controlled storage and write down who may open them.

Illustrative: a plumbing and drain company's switch#

Illustrative: a fictional plumbing and drain company is leaving an older field service platform for a newer one. The new vendor's import service covers customers, locations, equipment, open jobs and active maintenance agreements, and the COO decides to migrate exactly that.

Before cancellation, the office manager exports jobs, estimates with all options, invoices, technician notes and the photo library, each carrying the old system's IDs, and stores them on the company file server with a crosswalk to the new customer IDs. Technicians look up older visits through a simple search sheet. When the owner later reviews the archive in a data licensing intake, the linked estimates, jobs and callbacks are what make it worth discussing; photo folders that never carried job IDs are set aside.

Who controls the old data after you leave?#

Your contract with the old vendor controls how long you can get your data back and in what form. Look for data ownership language, a data return or export clause, any post-termination access period, and whether the vendor keeps aggregated or de-identified data after you go.

Check the same contract for how the vendor may use your data for product development or AI, and read the new vendor's terms just as closely before you load anything. Inside your company, name one owner for the archive who approves access, sets the retention period and decides when copies are destroyed. A retention schedule tied to warranty terms, tax records and your trade's regulatory records keeps the archive from turning into an unmanaged copy.

Why old history can still be worth something#

Old job history can be worth more than warranty lookups because AI developers building tools for field work need real examples of how jobs unfold: what the customer reported, what the technician found, which options were offered, what was sold and whether the fix held. Records that keep those links are much rarer than raw job counts.

SourceX starts with a metadata-only fit check, so nothing leaves your archive in the first conversation. If an archive proceeds, the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery covers a rights review against old vendor terms and customer agreements, removal of customer names, addresses and phone numbers, your approval of the final package, and delivery from your own storage. The data is licensed, not sold, and your company keeps ownership.