You've got the carrier's PDF scope on your desk, Xactimate is open, and you're about to spend the next three hours rebuilding the estimate line by line. There's a better way, and in this guide I'll walk you through the entire process of getting a PDF estimate into Xactimate as an ESX file, step by step, including the parts most tutorials skip.
Converting PDF scopes to ESX files is our entire business. This is the workflow our team runs every day, not the theory.
Key Insight: The entire PDF-to-ESX workflow, from raw carrier PDF to an import-ready .esx file, takes about two minutes with modern conversion tools. Done by hand, the same scope typically takes several hours. The difference isn't the typing; it's the code resolution.
What You Need Before You Start
Before you convert anything, gather three things:
- The cleanest PDF you can get. A text-based scope PDF (not a scan) converts far more reliably. If all you have is a scan, OCR handles it, but expect a few more line items to need a human eye.
- Your Xactimate install. The ESX file is the vehicle: Xactimate is the destination. You need Xactimate (or XactAnalysis) to open and reprice the file. ESXPress and similar tools convert the PDF; Xactimate imports the result.
- The current price list. Xactimate reprices every imported file against whatever price list is loaded in your copy at import time, not the list the file was originally priced on. More on that in a minute, because it's the #1 surprise in this workflow.
Step 1: Get the Scope PDF Ready
Carrier scopes come in every shape imaginable: 4-page summaries, 40-page line-by-line breakdowns, scanned faxes, and everything between. For the cleanest conversion:
- Use the final, signed version of the scope, not the draft.
- Make sure the pages are in order and none are rotated or upside down.
- If the PDF has multiple estimates inside one file (some carriers append the supplement to the original), note where the priced scope actually starts.
The good news: modern conversion tools handle multi-page scopes, mixed formats, and OCR. ESXPress, for example, processes the whole PDF and resolves every line item against the SEL code dictionary, with automated checks that flag anything it can't resolve.
Review required: AI-generated output requires professional review, verify every line item, price, and total before submission.
Step 2: Convert: Manually or With a Tool
You have three options here, and they're not equal:
| Method | Time per scope | Risk |
|---|---|---|
| Hand-build in Xactimate | Several hours | Typo'd codes, missed line items, your whole afternoon |
| Legacy converter / spreadsheet export | 1-3 hours + cleanup | Stale code maps, missing line items, no verification |
| Automated AI conversion (ESXPress) | About 2 minutes | Every line resolves to a real SEL code or keeps the PDF's own price, nothing is invented |
Whichever route you take, the output is the same thing: an .esx file, the Xactimate project file that carries your line items, quantities, and prices in the format Xactimate expects. (If you want the deep technical breakdown, read Inside the ESX File Format: What's Actually Inside a .esx File.)
Step 3: Review the Line Items Before You Import
This is the step everyone skips, and it's the step that separates a clean import from a mess. Before you import, check:
- Line count matches the PDF. If the scope has 47 priced line items, your conversion should have 47, not 41, not 52. A conversion that drops lines is worse than no conversion.
- Quantities and units carried over. SQ vs SF vs LF vs EA matters. A shingle line in SQ priced as SF is off by a factor of 100.
- Activity codes make sense. Xactimate prices install (+), removal (-), and add (&) differently. A tear-off priced as an install will come back wildly high.
- Totals reconcile. The grand total in the file should match the PDF's RCV (or be provably different, depreciation, O&P, and tax handling vary by carrier).
ESXPress surfaces this automatically: Scope Intel reads the totals (RCV, O&P, tax, depreciation, ACV) straight from the conversion record, and the estimate comparison tools run a side-by-side line variance against the PDF. You don't have to eyeball 47 lines against a 15-page PDF.
Step 4: Import Into Xactimate
Import is the easy part: Xactimate's Import function reads the .esx file directly. But here's what happens next that most contractors don't expect:
How the reprice works: Imported lines are repriced against the price list currently loaded in your copy, the price-list stamp inside the file is not honored. If the PDF was priced on an older list, your imported total can jump up or down by tens of thousands of dollars. That's not a bug in your file; that's the reprice. Depending on the file and the codes, the total can move in either direction, see Why Does Xactimate Reprice My Estimate? for the full breakdown.
So after import, the checklist continues:
- Compare the imported grand total against the PDF total.
- If it moved, identify which lines moved and why (price-list edition, activity-code mismatch, or a line Xactimate flagged as not in the price list).
- Fix anything flagged "Not in Price List", those lines usually need a different SEL code or a manual price.
Step 5: Verify and Ship
Verification is where the money lives. A 30-SQ roof with a $10/SQ shingle error is a $300 mistake. With 40+ line items, small errors compound fast. My rule: the converted file's line items, quantities, and totals must trace back to the PDF line by line. If you can't trace it, don't ship it.
This is exactly why ESXPress exists: the whole point of converting with a verified tool is that the file you import is the file the carrier priced. every line carried through as a real Xactimate line, priced the way the carrier priced it.
Common Pitfalls (and How to Avoid Them)
| Pitfall | What happens | Fix |
|---|---|---|
| Line-item caps | Tool truncates scopes over a line count | Use a converter with flat per-conversion pricing, big claims shouldn't cost extra (1,000+ line items per scope) |
| Credit/export walls | Tool requires credits to actually export the ESX | Check the pricing model before you convert, per-export fees add up fast |
| Ephemeral downloads | File disappears after 60 minutes; you lose the record | Keep a permanent copy of every conversion, you own the claim file |
| Unchecked codes | Converter guesses SEL codes; import flags them or prices them wrong | Use a tool with automated verification that flags unresolved lines |
The Bottom Line
PDF to ESX is a solved problem, the workflow is: clean scope in, convert with accurate code resolution, review line items and totals, import into Xactimate, expect and understand the reprice, and verify before you ship. The tools that do this well collapse a 3-6 hour task into about two minutes, and they give you the verification layer that protects your margin.
Want to see it on your own scope? Start a free 14-day trial, card required, no charge until it ends. Or check the full feature breakdown and pricing first, or go straight to the PDF to ESX converter.
This guide covers the conversion workflow. For the technical details behind the file itself, the sections Xactimate checks on import, the CAT|SEL linkage, and the format rules, read the definitive format guide: Inside the ESX File Format: What's Actually Inside a .esx File.
Related: the PDF to ESX converter walkthrough, and the PDF to Xactimate converter.