How to export your data from FieldPulse (step by step)

FieldPulse gives an Admin three self-serve exports: customers, estimates and invoices. Job data comes out through its Raw Data reports. Your item list and pricebook don't have a documented one-click export, so that one needs a written request. Everything else you need you either download by hand or rebuild.

This guide walks through each export as FieldPulse's own help center describes it, shows the click path as an animated illustration, says what each file holds, and lists the contract dates that decide how long you have.

What you'll end up with

Here's the kit, and where each file goes if you move to TradesWork. TradesWork has no dedicated FieldPulse importer, so FieldPulse files come in through its Another system or a spreadsheet option, which takes customers and a price list. The rest is your archive.

Before you start: role, inbox and dates

Three checks save a wasted afternoon.

1. Your role. FieldPulse's help center says only users with an Admin role can export customers.¹ If you're an office manager without Admin, ask the owner to change it or run the exports.
2. Your inbox. Customer, estimate and invoice exports don't download in the browser. FieldPulse emails them to the address registered on your FieldPulse account.¹² Make sure that's an inbox you can open.
3. Your dates. FieldPulse's help center says customers who signed up after November 2023 are on an annual contract.³ Its terms say annual subscriptions renew automatically unless you give written notice at least 60 days before the term ends (§8.5).⁴ Find your renewal date first; it sets your whole timeline.

1. Export your customer list

The customer file is the one you'll import, so run it first.¹

1. Select Customers in the left-side menu.
2. Select Export at the top right of the Customers page.
3. Watch the bottom-right corner. The first message says you'll get an email with the export attached; a second says the export is complete.
4. Open the email from FieldPulse and save the CSV attachment.

FieldPulse's help center says your custom field data is included in exports.⁵ Check the row count against the number of customers you expect, and open a few customers you know well to confirm addresses and phone numbers came through.

Gotcha: the export runs in the background. If the email doesn't arrive, check spam and confirm which address is on your FieldPulse login before running it again.

2. Export estimates and invoices

Estimates and invoices export separately, each from its own list.²

1. Select Estimates in the left-side menu, then Export at the top right.
2. Select Invoices in the left-side menu, then Export at the top right.
3. Open each emailed report and save the attachment.

The help center lists the columns:²

That's a summary, not line items. It's enough to find an old invoice, answer a dispute, or total open balances. For line-level detail, use Raw Data reporting below.

3. Export job data from Raw Data reports

FieldPulse doesn't export jobs from the jobs list. Its help center says job data is exported after running a report.⁶

1. In the left-side menu, under Management, select Reporting.
2. Select the Jobs tab and then Raw Data.
3. If the tab offers a Date Type, choose one. Pick a date range with the calendar icon, or a preset.
4. Select Load Data.
5. Use Columns, Filters or Quick Reports to shape the table, and wait for it to update.
6. Select Export CSV. The file downloads to your device.

The export covers what's on screen, so set columns and filters before you export.⁶ For a long history, run one year at a time and name each file with its date range. The same Reporting area has other record tabs, such as Payments; export those the same way if your account shows them.

4. Your item list and pricebook

This is the gap. FieldPulse documents how to import items and a pricebook, and its item import tool has an Export to .xlsx button while you check records during an import.⁷ We couldn't find a public help article for exporting your full, current item list or pricebook on its own, so there's no click path to show here.

Don't guess. Email support@fieldpulse.com, or use the in-app chat, and ask for:

Keep the reply. If support can't provide it, you'll rebuild the price book from invoices and your supplier price lists, which takes real time. Find out early.

What you can't export yourself

Permissions and plan limits

FieldPulse doesn't publish prices or plan-by-plan feature limits for exports, so if Reporting is missing from your menu, ask support whether your plan includes it.

The 60-day window in FieldPulse's terms

FieldPulse's terms of service are clearer than most about data after you leave:⁴

• You own your data. As between you and FieldPulse, you own Customer Data (§24.2).
• Export for 60 days after the subscription ends, in a format FieldPulse makes available (§24.8).
• Deletion within 90 days after the end of the subscription, or within 30 days of a written deletion request (§24.8).

That's a useful safety net, not a plan. Run your own exports while you have full access, ideally before you give notice.

1. March

   First full export

   Customers, estimates, invoices, Raw Data jobs by year. Item list requested in writing.

2. April

   Test the new system

   Import customers and items into a trial. Check what's missing.

3. By May 1

   Written notice

   At least 60 days before a June 30 term end. Keep the confirmation.

4. May to June

   Side by side

   Both systems live. Re-run customers and invoices near cut-over.

5. Last week of June

   Final exports

   Everything that changed since March. Two copies stored.

6. July and August

   Backup window

   The 60-day post-term export window in §24.8, if you missed anything.

That example assumes an annual term ending June 30. Swap in your own dates.

Store, label and re-run

• Name every file with what it is and the date it was run, such as "fieldpulse customers 2026-10-15.csv".
• Store everything in a folder you control, with a second copy offline.
• Re-run what changes (customers, invoices, open jobs) near cutover and again on your last day.
• Spot-check row counts and totals against FieldPulse's own screens.

How TradesWork imports these files

If TradesWork is on your shortlist: choose Another system or a spreadsheet on the import page, drop the customer CSV and the item file, confirm what each file is, match the columns, and see a preview before anything is saved. You can import into a separate sandbox company first. Job, estimate and invoice history stays in your archive. The FieldPulse to TradesWork migration guide shows each screen, and TradesWork vs FieldPulse covers whether to switch at all.