Import Burp / Caido / HAR projects

01What you can import

Crusader reads the project and capture formats you already have lying around from other tools. The format is auto-detected from the file you hand it — you don't pick a type.

• Burp project — the binary .burp project file. This is the saved-state file Burp writes, not an export.
• HAR — a .har archive from browser DevTools, Charles, or anything that emits HTTP Archive.
• Fiddler SAZ — a .saz session archive.
• Caido — a Caido project as .caido, .json, .zip, .sqlite, or .db (the SQLite database is opened read-only).
• Burp Target scope JSON — scope rules only, no traffic. Covered in §05.

02Import from the Project Picker

The Project Picker is the front door for imports — not drag-onto-startup. (Dragging files inside the app is a different feature: it imports URLs into the Site Map.)

1. Launch Crusader to reach the Project Picker.
2. Find the row labeled "Import Burp / HAR / SAZ / Caido", marked with an IMPORT chip, and click it.
3. In the "Import project traffic" file picker, choose your .burp, .har, .saz, or Caido file. Crusader detects the format on its own.

From there Crusader does the work: it auto-creates a new project named after the file (a file like acme.burp becomes the project "acme import"), reads the traffic in, and reports what it found — for example imported 1,234 exchanges, 56 request-only, 12 repeater tabs. It then opens the new project and jumps straight to Repeater if it seeded any tabs, or to History if it didn't.

03Import from the CLI

The same importers are available headless — handy for scripting a migration or pulling a teammate's capture into a project without opening the GUI. Every command prints JSON to stdout, so it pipes cleanly.

# format is the first argument; the file is the second
crusader import burp    ./acme.burp
crusader import har     ./session.har
crusader import saz     ./capture.saz
crusader import caido   ./project.caido
crusader import fiddler ./old.saz       # 'fiddler' is an alias for SAZ
crusader import scope   ./scope.json    # scope rules only — see below

Useful flags:

04What's preserved per format

Every format gives you the same core: your HTTP exchanges land in History with method, URL, host, path, query, scheme, TLS, protocol, status, headers, bodies, size, and content type — plus the raw bytes of each request and response. On top of that, Crusader smart-seeds up to 12 Repeater tabs from the most interesting requests it sees, and reconstructs your scope from the origins observed in the traffic (origin/*) and the hosts it discovered.

HAR, SAZ, and Caido carry only traffic to begin with — no findings or comments live in those formats — so history plus reconstructed scope is the whole picture. Burp projects carry more, which is where the limits below matter.

05Importing scope on its own

If you've already defined your engagement boundary in Burp, you don't have to retype it. Crusader reads Burp Target scope JSON directly and converts the include and exclude rules into its own glob patterns.

crusader import scope ./burp-scope.json

This opens Settings → Target scope and reports what it brought across — for example imported 8 scope / 2 exceptions. You can also paste the same Burp scope JSON straight into the scope boxes in Settings → Target scope if you'd rather not go through a file. Either way, your include and exclude lists are reconstructed without hand-editing.

06The honest limits

Crusader imports your traffic and your scope faithfully. It does not pretend to import things it can't read accurately. The limits are worth knowing before you delete the original file (you shouldn't — but you can).

• The original file is never modified. Every importer is read-only; the Caido SQLite database is opened read-only. Your source project stays byte-for-byte as it was, so you can re-import or fall back at any time.
• No Burp XML / items import. Only the binary .burp project file is supported — never the XML export.
• Burp Scanner issues are not imported. Crusader brings in HTTP traffic and reconstructed scope, not Burp's findings.
• Comments, highlights, and colors are not imported. Neither are Burp notes. Only the HTTP exchanges and scope cross over.
• Burp project size cap: 512 MB. Larger .burp files are out of range for the importer.

Want a guide that isn't here yet? Email hello@crusaderproxy.com.