Quick answerAn ESX won't import into Xactimate® because of one of six things: the file isn't recognized as valid, the sketch imports blank, the price list doesn't match, the company or claim profile doesn't match, the file was built in an incompatible version, or the download is corrupted. Each has a distinct, checkable cause, and Xactware's own documentation covers the import requirements. This applies to any ESX regardless of who produced it, so troubleshoot the file itself before assuming the source did something wrong.

Six symptoms, six fixes

The table below covers the common failure patterns when an ESX arrives from a roofer, a provider, or another adjuster and won't load cleanly into Xactimate®. None of these are unique to one source; any ESX, from any format-compliant tool, can hit them.

SymptomLikely causeFix
File not recognized / import error on openExtension changed in transit (renamed, re-zipped, or stripped by an email filter)Re-download the original attachment directly and import it unmodified; do not rename or compress it first
Sketch imports but the drawing area is blankSketch data was stripped when the file was resaved, exported, or converted through another program before it reached youAsk the sender to confirm the sketch renders on their end, then re-send the original file rather than a copy
Price list mismatch warningThe file was built against a price list or region different from the one on your estimateAccept the import and remap the price list inside Xactimate® per Xactware's documentation, or request the file re-exported to your price list
Profile mismatch on importSender's company profile, claim template, or code list differs from yoursImport as a new project instead of merging into an open one, then verify claim fields manually against the file of record
Older or newer version formatFile was exported from a build of Xactimate® that isn't compatible with the version you're runningCheck build compatibility in Xactware's help documentation; update your build or ask the sender to re-export in the current format
File is corrupted on downloadIncomplete download, an attachment stripped by a mail server, or a file altered by antivirus scanningRe-download directly from the source, confirm the file size matches what the sender reports, then retry the import

Troubleshoot before you assume the file is bad

Most of these symptoms can be diagnosed quickly without contacting anyone. Work the list in order; it isolates the cause instead of guessing at it.

  1. Check the extension

    Confirm the file actually ends in .esx and not .esx.txt, .zip, or a duplicate extension added by an email client. Rename only if the extension itself is wrong; do not touch the file contents.

  2. Check the file size

    A 0 KB or unusually small file for a residential roof almost always means a corrupted or partial download. Re-download it before doing anything else.

  3. Try the import into a blank project

    Import via the Sketch import option into a fresh, empty project rather than merging into an existing claim file. This isolates whether the problem is the file or a profile clash with your open estimate. Menus vary by version; verify the exact path in your build.

  4. Compare Xactimate® build versions

    Check Help/About in your copy of Xactimate® against the version the sender used to export. Xactware documents which builds read which export formats; a mismatch here explains most 'older version' failures.

  5. Read the actual import message

    Xactimate® reports a specific reason for a failed or partial import, not just a generic error. That message usually points straight to price list, profile, or version as the cause rather than a bad file.

  6. Re-request only after the above

    If none of the checks above resolve it, the fastest fix is a fresh copy of the file rather than more troubleshooting on a copy that may already be damaged.

When to stop troubleshooting and re-request the file

  • More than one symptom shows up at once

    A blank sketch plus a version warning usually means the file itself is compromised, not that two separate settings are wrong.

  • The sender confirms the file opened correctly on their end before sending

    That isolates the failure to transmission (email, download, or storage), which a re-download or re-send usually fixes outright.

  • A claim deadline is close

    Working through six possible causes on a copy that might be unusable costs more time than asking for a fresh export up front.

  • The file came from an unfamiliar source or an unverified attachment

    Confirm the sender and the file's origin before importing anything into an active claim file; when in doubt, ask for a re-send through a known channel.

This is a file-format issue, not a provider issue

Every one of these six failure modes is a property of the ESX file itself, its export settings, and the build of Xactimate® reading it, not a defect specific to any one roofer, provider, or platform. A standards-built ESX from any source, including one built for the sponsor's Sketch My Roof roof measurement reports, can still fail to import if it is downloaded incompletely, renamed, or opened in a mismatched build. Diagnose the file before assuming the source did something wrong.

If the original file is unusable and re-requesting isn't practical, the reset is to order a roof report by address directly and get a clean ESX built to your price list and profile from the start.

Frequently Asked Questions

Why won't an ESX file import into Xactimate®?
It's typically one of six things: the file isn't recognized as valid, the sketch imports blank, the price list doesn't match, the profile doesn't match, the file was exported from an incompatible version, or the download is corrupted. Isolate which one with the file's size, extension, and the specific import error message before contacting the sender.
Does this happen with files from any provider, or just certain ones?
Any ESX, regardless of who built it, can hit these six failure modes; they're properties of the export, the transfer, and the Xactimate® build reading it, not a defect tied to a specific source.
Should I re-request the file or keep troubleshooting?
Troubleshoot first if only one symptom is present and you have time: check the extension, file size, and the exact import error. Re-request immediately if multiple symptoms appear at once, if the sender confirms the file worked before sending, or if a claim deadline is close.
Does a price list mismatch mean the file is bad?
No. A price list mismatch means the file was built against a different price list or region than your open estimate. Xactware's documentation covers remapping the price list on import; the file itself is usually fine.
What if the ESX came from Sketch My Roof and won't import?
Check the same six causes first, since the fix is identical regardless of source. If the file is confirmed corrupted or incomplete, request a revision from the original delivery email rather than troubleshooting a damaged copy.

Sources