How do you export AccuLynx data for an AI data license?
AccuLynx organizes a roofing company's work by job and by milestone, from lead through to closed. Built-in reports give summaries, and one job's history page has export options. A full pull of jobs and their related records goes through the API, which needs an account with API access, so ask your account manager what your plan includes.
What an AccuLynx account usually holds
| Jobs by milestone | Each job moves through lead, prospect, approved, completed, invoiced, closed or cancelled. The dates on those moves show how long each stage takes. |
| Estimates and measurements | Roof scope, materials and pricing prepared for a homeowner. They show how a roofer turns a measurement into a bid. |
| Supplements and insurance paperwork | Requests for added scope after an insurer's first estimate, with the reasons. This is specialized text that few other sources contain. |
| Photos and documents | Inspection images, contracts and permits attached to each job. |
| Messages and job history | Texts, emails and comments logged against a job, plus the activity trail of changes made to it. |
How records leave AccuLynx, route by route
| Tool | What an export gives you | What is missing or needs an admin |
|---|---|---|
| Built-in reports | Pre-built and custom reports on sales, production, payments and expenses. The vendor's marketing pages describe more than twenty of them. | We did not find an official help article on exporting a report or a full job list, so export formats and limits are unconfirmed. |
| Job History page export | The activity trail of a single job, with filtering and export options, according to the vendor's product update notes. | One job at a time, so it does not scale to a whole account. |
| The Jobs endpoint of the API | A list of jobs filtered by created, modified or milestone date and by milestone, with contact details expandable inline. The page limit is 25 jobs per request. | Job-level fields only: number, name, address, trade, lead source, milestone and dates. Estimates, photos and messages come from other endpoints, which we did not read in full. |
| Other API endpoints | The vendor's API reference lists further resources for a developer to read. | We did not review each one, so check the reference for estimates, supplements, documents and messages. |
| Webhooks | Event notifications from the vendor's webhook documentation. | They signal new changes going forward and do not replay history. |
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
The vendor's authentication page says a Location or Company Administrator creates API keys in Account Settings. If you cannot see that screen, an administrator makes the key for you, and each integration should have its own named key. That page does not describe key scopes, so ask what a key can read.
The vendor's contact page says customer support covers the web and mobile apps only. API questions go to a separate API support team.
Limits the vendor sets
The rate limit page sets a per-IP ceiling for each application, and once it is crossed requests are refused with a 429 error for a short ban. After that, a valid key has its own lower per-second ceiling. A developer should add retries, and higher limits are available by asking through the vendor's partner form.
A pull of many thousands of jobs at 25 per request is a long run of requests. Plan for it to be slow, and check current limits at the time of the pull.
What to count: jobs by milestone and date range
Count jobs, by milestone, with the earliest and latest created dates. The Jobs endpoint returns a total count for a filtered query, so a developer can report it exactly. Mark that number verified. A figure taken from a dashboard or remembered is estimated.
Add how many closed jobs have a final invoice, how many have supplements, and roughly how many have photos. The vendor's documentation does not give a retention period or a storage figure, so we did not find a published one.
Cleaning before anything leaves
Homeowner names, addresses and phone numbers sit on every job, with insurance claim numbers on storm work. Replace them with de-identified codes that keep a job's records together.
Messages may hold payment talk and personal remarks, and photos may show people or documents. This is general information, not legal advice, so ask counsel about messaging consent and insurance rules before any set is built.
What stays out for an AccuLynx set
| Homeowner identities and addresses | Replaced with de-identified codes or not licensed. |
| Claim numbers and adjuster details | Removed from supplements and messages alike. |
| Payment records and signed contracts | Left out of the license. |
| Messages that mention private matters | Texts about health, family or money are left out when they cannot be cleaned. |
Choosing closed roofing jobs for a sample
A roofing company has used AccuLynx for many years of storm and replacement work. A developer with a key from the company administrator pulls jobs by milestone and the related estimates and supplements, noting the total job count. Homeowner details and claim numbers are replaced or removed, and message threads that cannot be cleaned are left out. The owner reviews a sample of closed jobs and decides which years are included.
Questions owners ask about this
Can any user create an API key?
The vendor says Location or Company Administrators create keys. Others have to ask one.
Do cancelled jobs come out with the rest?
The Jobs endpoint documentation says cancelled jobs, also called dead, need a separate setting. Ask your developer to include them if they matter.
Is the job history export enough for a whole company?
It covers one job's activity. For many jobs, the API is the practical route.
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.
- Claims and underwriting files: A risk decision, its reasons and what happened next, with every policyholder removed first.
- Inspection reports and photos: A finding beside its photos and its fix, with faces, plates and addresses removed first.