How do you export JobNimbus data for an AI data license?
JobNimbus keeps a contractor's leads, jobs, estimates, tasks and photos in one place. The built-in route out is the custom report, which exports a table to CSV or Excel. The full history, notes and files come through the open API, and the vendor itself says to build on it only with coding experience.
What a JobNimbus account usually holds
| Contacts and jobs | A homeowner or business, the job tied to them and the stage it reached. The pipeline from first call to close is visible in the dates. |
| Estimates and invoices | Scope, line items and amounts for each job. For roofing and restoration, this shows how scope is written for storm and insurance work. |
| Tasks | Follow-ups and production steps assigned to staff. They show what the crew and office did and in what order. |
| Activity and notes | A running log of calls, messages, status changes and comments on each contact or job. It is usually the richest text in the account. |
| Documents and photos | Inspection photos, signed forms, measurement reports and insurance paperwork attached to jobs. |
How records leave JobNimbus, route by route
| Tool | What an export gives you | What is missing or needs an admin |
|---|---|---|
| Custom report export | A saved custom report downloaded as CSV or Excel from the menu beside the report title, per the vendor's help article. | Only the records and fields in that report. Edits made later in JobNimbus do not update a file already exported, and the article does not say which permission is needed to export. |
| Contact grid and list views | The columns shown in a list of contacts, which a custom report can reproduce with addresses. | Contact-level fields, not the conversation. We did not find an official article for exporting every contact or job in one step. |
| The open API | Contacts, jobs and notes through the vendor's public API, with size, from, sort, fields and filter parameters. Other record types are listed in the vendor's Postman documentation. | Needs a developer and an API key. A key carries the permissions of the access profile chosen when it was made, and the help center says later profile changes do not reach existing keys. |
| Large queries over ten thousand items | A separate query document that the vendor's help article points to for result sets above that size. | We could not read that document, so how large pulls work is unconfirmed here. |
| Asking JobNimbus support | A route to ask the vendor about a full account export. | We did not find a published full-account export service, so treat this as a question, not a feature. |
Tool names belong to their owners and are used only to say where records usually live. Export features change by plan and version, so check the current rules for your account.
Who needs to be involved
Report access follows each user's permissions, so the account owner or an administrator should run the exports. API keys are created in the settings area under the API tab, and the help center page we read does not say which roles may create one. Ask your administrator who can.
Features differ by plan and by account setup. Check the current rules for the account before promising a particular file.
What to count: jobs, stages and attached files
Report jobs as the unit, with the earliest and latest creation dates, and the split between lead, estimate and completed stages if the account tracks them. Run a custom report over the full date range and note the row count. Call it verified if it came from the report, and estimated if it came from a dashboard or recollection.
Also note how many jobs have photos and how many have written activity notes. The vendor's documentation does not publish storage totals or record counts, so these numbers come from your own account.
Cleaning before anything leaves
Homeowner names, phone numbers, emails and property addresses run through every record, along with insurance claim numbers and adjuster names. Replace them with de-identified codes that keep one job together.
Photos can show faces, license plates, house numbers and documents on a table. Screen them before any file is licensed. This is general information, not legal advice, and counsel should review insurance and privacy rules for the states you work in.
What stays out for a JobNimbus set
| Homeowner identities and addresses | Replaced with de-identified codes, or the record is not licensed. |
| Insurance claim and policy details | Claim numbers, policy numbers and adjuster contacts are removed. |
| Signed contracts and payment records | Left out of the license, since they carry signatures and financial detail. |
| Photos that cannot be screened | Any image showing people, plates or paperwork that cannot be cleaned stays out. |
A sample, step by step
A restoration contractor has used JobNimbus for several years of water and storm jobs. The office manager saves a custom report of jobs and exports it to CSV for the count, and a developer pulls jobs and activity notes through the API with a key set up for the purpose. Names, addresses and claim numbers are replaced or removed, and photos are screened before any are included. The owner reads a sample of cleaned jobs and decides which stages and years go in.
Questions owners ask about this
Is the CSV from a custom report the whole job history?
No. It holds the fields and records the report was built with. Activity notes and files need the API or a separate pull.
Does a new API key see everything in the account?
Only what its access profile allows. The help center says the key keeps the permissions it had when created.
Our crews take photos on phones and not in JobNimbus. Does that matter?
It does, because only photos attached to jobs are in the account. Count the attached ones and treat the phone library as a separate source.
Didn't find your question? Ask us directly.
Sources
The vendor's own pages this guide draws on. Some help centers did not open for us, and where a step rests on a summary and not the page itself, the guide says so. Menus and limits change by plan and version, so check the current pages for your account.
Keep reading
Related kinds of records
- Work orders and dispatch notes: A job from request to fix, in a technician's own words.
- Quotes and estimates: A price and the argument behind it, with margins and current prices kept out unless the owner says.
- CRM history: Salesforce, HubSpot, Pipedrive and Zoho notes and timelines; fields alone say little.
- Inspection reports and photos: A finding beside its photos and its fix, with faces, plates and addresses removed first.