How to Convert a PDF to ESX for Xactimate

Xactimate cannot open a PDF. To get a PDF estimate into Xactimate, you have two options: re-enter the estimate by hand, or run the PDF through a PDF-to-ESX converter and import the resulting file. Manual re-entry takes two to five hours on a large file. A converter takes minutes. Either way, the result needs to be verified before you build on it.

This guide covers what an ESX file is, how each conversion method works, and a checklist for confirming the converted estimate matches the original.

What is an ESX file?

An ESX file is Xactimate's native project format. It holds everything Xactimate knows about an estimate:

• Line items with category and selector codes, quantities, units, and pricing

• The project tree — the hierarchy of levels, rooms, and groups that organizes the estimate

• Trade and activity codes on every line item

• F9 notes — the line-item notes an estimator attaches to explain scope or pricing

• Dimensions for each room and area

• Claim information, including insured, carrier, and claim number

• Attachments, such as photos and supporting documents

• Sketch – the Sketch diagram of the loss.

A PDF estimate is a printout of that project. It keeps the descriptions and the numbers. It drops the structure. The codes, the tree, the notes, and the dimensions are gone, and the estimate becomes a document you can read but not work in.

That is why converting a PDF to ESX is more than data entry. You are rebuilding the structure the PDF removed.

When do you need to convert a PDF to ESX?

Estimates move between parties as PDFs because PDFs are easy to send and hard to alter. The moment someone needs to edit, review, or build from that estimate, the PDF has to become an ESX again. A few common situations:

• A contractor receives an adjuster's estimate as a PDF and needs to supplement it.

• A mitigation review team receives a contractor's invoice as a PDF and needs it in Xactimate to review against IICRC standards.

• A building consultant receives a contractor or independent adjuster's estimate and needs to analyze it in Xactimate.

• A restorer needs the approved scope as an ESX so it can sync to job management software like DASH, PSA, or Encircle.

Every handoff in the claims cycle creates one of these conversion steps. On a claim with three rounds of negotiation, the same estimate may be converted three times by three different people.

Method 1: Re-enter the estimate manually in Xactimate

Manual re-entry means opening a new project in Xactimate and rebuilding the PDF line by line.

1. Create a new project and enter the claim information.

2. Rebuild the project tree: levels, rooms, and groups as they appear in the PDF.

3. Enter dimensions for each room.

4. Search for each line item, add it to the correct room, and match the quantity and unit.

5. Adjust pricing where the PDF shows a non-standard price.

6. Re-create any notes that appear in the PDF.

7. Compare your total to the PDF's total and reconcile the difference.

On a small mitigation invoice, this might take twenty minutes. On a 500-line-item fire loss, it takes two to five hours, and most of that time goes to line item search rather than judgment.

Where manual re-entry breaks down

• RCV drift. Replacement Cost Value is the estimate's total before depreciation. A wrong code, a rounded quantity, or a missed price adjustment moves the total. On a large estimate, several small misses add up to a total that no longer matches the PDF.

• Lost notes. F9 notes explain why a line item is priced or scoped a certain way. They are the first thing skipped when someone is re-typing under time pressure.

• Custom items. Line items with modified descriptions or pricing look like standard items on a PDF. Without the original code, there is no way to tell them apart.

• Fatigue. Error rates rise after the first few hundred line items.

Manual re-entry still makes sense for very small files, or when you intend to rewrite most of the scope anyway.

Method 2: Use a PDF to ESX converter

A PDF-to-ESX converter reads the PDF and rebuilds the Xactimate project from it: line items, project tree, codes, notes, and dimensions. The steps below describe the general workflow. This is also how ClaimsFlow works.

1. Upload the PDF estimate. Any Xactimate-generated PDF, including large-loss files with 1,000 or more line items.

2. Wait for processing. Conversion takes minutes rather than hours, regardless of file size.

3. Review the converted project before you download it. Check the line item count, the RCV total against the PDF, and any items flagged as custom or non-standard.

4. Download the ESX file.

5. Import the ESX into Xactimate. Import the ESX file into your Xactimate profile.

The review step is where the value is. A converted file you still have to check line by line has not saved much time. A converted file that shows you the RCV match and flags the items worth a second look lets you move straight to the work you actually needed the ESX for.

Manual re-entry vs. PDF-to-ESX converter

How to verify a converted ESX before you use it

Whichever method you used, check the converted estimate against the source PDF before you supplement, review, or budget from it. Five minutes here prevents a dispute later.

• RCV total matches the PDF. To the dollar. If it does not, find the line items responsible before doing anything else.

• Line item count matches. A missing or duplicated line is the most common cause of a total that is off.

• Project tree matches. Rooms and groups appear in the same structure as the PDF.

• Custom and non-standard items are identified. Any line item with a modified description or price should be visible as such, not silently mapped to the nearest standard item.

• Notes and dimensions are present where the PDF had them.

• Spot-check the highest-value line items. Pick five to ten. Confirm quantity, unit, and unit price.

A mismatched RCV does not announce itself. It surfaces weeks later, when a supplement total does not reconcile or a reviewer's change report does not tie back to the invoice.

Common PDF to ESX conversion problems

Scanned or image-only PDFs. A PDF that was printed and scanned has no text layer. Converters that rely on text extraction will struggle. Where possible, request the original digital PDF.

Non-Xactimate PDFs. Contractor invoices, estimates from other platforms, and spreadsheet printouts do not follow the Xactimate report layout. They can still be converted, but line items have to be mapped to Xactimate codes rather than matched, which requires more review.

Custom line items. Items with modified descriptions or pricing are the hardest to convert and the most important to catch. This is where a review step matters most.

Multiple reports in one file. A PDF that combines several Xactimate report types, or several estimates, can confuse the structure. Split it before converting if you can.

Very large files. A 1,000-plus line item estimate is where manual re-entry becomes impractical and where converter accuracy matters most, because a small error rate applied to a large file produces a large gap.

Frequently asked questions

Can Xactimate import a PDF directly? No. Xactimate opens ESX files and its own project formats. It has no PDF import. To get a PDF estimate into Xactimate, you either rebuild it manually or convert it to ESX with a third-party tool and import the ESX.

What is the difference between a PDF estimate and an ESX file? An ESX file is the working Xactimate project, with line item codes, the project tree, notes, dimensions, and claim information. A PDF is a printed view of that project. It keeps descriptions and totals but drops the underlying structure, so it can be read but not edited in Xactimate.

How long does it take to convert a PDF to ESX? Manual re-entry takes roughly twenty minutes for a small mitigation invoice and two to five hours for a large-loss estimate. A PDF-to-ESX converter processes files of any size in minutes.

How accurate is PDF-to-ESX conversion? It depends on the tool and the file. The measure that matters is whether the converted RCV matches the PDF and whether custom items are flagged rather than silently mapped. Review the converted estimate before you download it, and spot-check high-value line items after import.

Can you convert a non-Xactimate estimate to ESX? Yes, but it requires mapping rather than matching. A contractor invoice or an estimate from another platform has no Xactimate codes, so each line item has to be assigned one. Expect more items flagged for review than on a Xactimate-generated PDF.

Does a converted ESX include dimensions and sketch? Dimensions transfer with the ESX, so room measurements and calculated quantities are available in Xactimate. [Confirm what ClaimsFlow transfers for Sketch geometry before publishing.]

How much does PDF-to-ESX conversion cost? Manual re-entry costs whatever the estimator or reviewer's time is worth, typically hours per file. Converters are priced per line item or by subscription. ClaimsFlow includes 250 line items free, then bills per line item, with a monthly plan for higher volume.

Convert your first PDF to ESX

Conversion is a small step, but it sits in front of every downstream task: supplementing, reviewing, analyzing, budgeting. Removing it moves all of them.

Upload a PDF estimate, review the conversion, and download the ESX. Your first 250 line items are free at claimsflow.io.

Related articles:

• Why Restoration Contractors Need to Convert PDF Estimates to Xactimate

• Mitigation Bill Review Has a PDF to ESX Conversion Problem

• Green Items: The Hidden Cost of Custom Line Items in PDF Estimates

• Why the Insurance Claims Process Has a Flow Problem