1. LandOffer
  2. Blog
  3. All articles
  4. Export Huntr Application History: Choose Full Data, Not Just the Metrics Report

Job search

Export Huntr Application History: Choose Full Data, Not Just the Metrics Report

Current Huntr export documentation and two original worked archive and timeline audits, with a synthetic reconciliation test and explicit schema limits.

9 min readLandOffer team

To preserve your Huntr application history, start with the account-level data download. A report from Metrics can help answer a narrower question, but a list of jobs alone cannot reconstruct every contact, activity or document you need for an ongoing search. Choose the export according to the records you need to keep using.

This guide uses public Huntr documentation checked October 20, 2026, plus two completed fictional archive exercises. We did not sign in, download a private export or test an import into another service. Actual file names, headers and attachment coverage remain unverified. For new opportunities, browse recent LandOffer roles while keeping your existing history intact.

A candidate sorts a full archival box of folders beside a smaller reporting notebook in a sunlit study

Choose the download that fits your question

Huntr's export guide, dated November 12, 2025, distinguishes an account data download from Metrics exports. It describes the former as a ZIP containing multiple CSV files organized by data type, including jobs, activities, profile information and contacts. It describes the Metrics Jobs download as containing job title, company, creation date, tracker list and source.

That makes the account download the documented starting point for retaining a broader history. Metrics remains useful for a focused job list or analysis. It is inaccurate to say its export contains no individual jobs. Compare what each download contains with what your next task requires.

A coach reviewing where you found opportunities may need only selected job rows. If you are rebuilding follow-ups, you may also need activities and associations. Decide that before sharing an entire archive containing other people's contact details or personal notes. Keep an untouched original locally and analyze a separate working copy.

Find the account download without changing the account

The current account-settings guide, dated May 1, 2026, places personal settings under your name at the dashboard's bottom left. Within Personal Account Settings, the My Account section contains the data-download option. Follow the current interface's corresponding download control; this is a documentation-based route, not a walkthrough tested inside an account.

Do not confuse downloading with subscription cancellation or account deletion. The same guide says cancelling Pro retains stored data while limiting Pro features, whereas deleting the account permanently removes its information. Neither action is required simply to obtain a copy. An export should be inspected before you make a separate decision about retaining the source account.

Name your local archive so you can distinguish successive downloads. Record when you obtained it and which account and boards you expected it to cover. Those are your own audit notes, not claims that the ZIP necessarily contains a particular manifest or export timestamp. Avoid putting a private email address in a filename you might later share.

Full export is a starting claim to check

Huntr calls its account download a full export. The public guide does not establish every CSV header, relationship field, historical-board rule or document-binary inclusion. Treat those details as inspection questions. Seeing the ZIP arrive can be reassuring, especially when your search has months of history. Still, its arrival does not establish that every record needed for migration is readable or included.

Huntr's contacts and documents guide describes stored contact information and job-search documents. That confirms why these categories matter, but does not prove that every original uploaded PDF or generated document appears as a usable binary inside the data archive. A row referring to a document and the document itself are different things.

Likewise, the job-card guide describes posting URLs, descriptions, application notes and interview records. List the elements you rely on, then check the actual download. Do not infer their presence from the size of the ZIP or from seeing one familiar company name. Leave unresolved categories marked unknown rather than silently treating them as recovered.

Completed archive audit: what Maya has actually retained

Maya is a fictional candidate preserving her search before reorganizing her records. For this exercise only, stipulate that her working folder contains three job rows, four activity rows, one contact row and one profile row. A reference to a resume appears in her notes, but she has not found a corresponding PDF. These counts and categories describe invented inputs, not a Huntr export we obtained.

Her completed inventory records both what is present and what remains missing:

Category inspected Finding in the fictional working copy Audit decision
Job records Three rows; two share a company and title but have different example identifiers Retain all three pending a record-level comparison
Activity records Four rows; one references an identifier absent from the job records Preserve the unmatched row separately; do not force a link
Contact information One contact associated with Cedar; no job-specific relationship supplied Retain the contact without assigning it to a particular interview
Profile information One profile row is readable Confirm this category only; it says nothing about uploaded files
Resume binary A note mentions a resume, but no PDF is present in the stipulated folder Mark the original document unverified and locate a separate authorized copy
Board coverage No evidence about archived or shared boards is supplied Do not label the archive a complete board-by-board backup

Maya's result is a useful partial archive with specific gaps. She can work from the three job records and inspect the unmatched activity, but cannot claim a recoverable resume or complete historical-board coverage. Her original ZIP remains unchanged while she annotates the working copy. If she later finds the missing resume elsewhere, she will record its source and version separately; she will not rewrite this inventory to suggest it was present in the original archive.

She also chooses a limited sharing packet: selected job rows for a coach, with unrelated contacts and profile information excluded. That is her completed handling decision, not an upload we performed. The archive stays private until she determines what information the recipient actually needs.

Separate saved dates, activities and employer receipts

Huntr's Metrics documentation describes a saved-job date range and an applications measure tied to associated application activity. A job's creation date and the date of applying therefore answer different questions. A CSV that includes the former should not be relabeled as an application-date history without supporting records.

The Activities guide adds another distinction: activities can include completed actions, future tasks and general search work. It also says moving jobs through certain stages automatically logs activities based on those moves. A tracker entry can reflect what was recorded or assumed from a stage change; it is not an employer's confirmation of receipt.

For a reliable timeline, identify the record type, associated opportunity and date's meaning before counting. Preserve original date text and any supplied time-zone information. If a field does not supply a time zone, leave it unspecified rather than inventing one. Compare a disputed submission with a genuine employer confirmation or portal record when available; do not manufacture that evidence from tracker status.

Completed timeline reconstruction with synthetic CSV records

The following exercise uses a tiny invented CSV fixture. We executed a local reconciliation of those fictional records to check the result. Its identifiers, columns and relationship rules are demonstration inputs, not Huntr's verified schema or a supported import format.

The fixture has three jobs. J1 and J2 both say Acme, Backend Engineer, but their created dates are October 1 and October 8, 2026. J1's stipulated list is Applied; J2's is Saved. J3 says Cedar, “Data Engineer, Platforms,” created October 2, with list Interview.

Four activity rows are supplied: A1 links J1 to an application on October 3; A2 links J3 to an application on October 4; A3 links J3 to an interview on October 10; A4 references missing job J9 on October 12. All four are stipulated completed records; future tasks are outside this fixture.

Using only those declared links produces this completed reconstruction:

Job identifier Recorded creation date Supported timeline from the fixture Completed handling decision
J1 October 1 Application activity A1 on October 3 Keep creation and application dates in separate fields
J2 October 8 No associated application activity supplied Retain as a separate Saved record; do not copy J1's application date
J3 October 2 Application A2 on October 4; interview A3 on October 10 Retain both events rather than replacing application history with the latest stage
J9, absent from jobs Unknown Unmatched activity A4 on October 12 Quarantine the relationship for review; do not invent a fourth job's details

The executed fixture check yields three job records, three matched activities and one unmatched activity. There are two matched application activities, not four applications. Two matching company-and-title strings do not justify merging J1 and J2. An activity whose linked job is missing remains unresolved even if its date looks plausible.

This is a consistency test of the example, not a test of Huntr's export completeness, employer submissions or round-trip restoration. A real archive may use different fields or omit stable identifiers. Inspect its actual structure before adapting the approach, and retain ambiguity where it cannot support a link.

Hands compare distinct job cards and event slips, keeping one unmatched slip aside for further review

Preserve meaning when you inspect CSVs

Work with a copy so spreadsheet edits do not overwrite the downloaded original. Check whether your tool interprets dates, long identifiers or leading zeros differently from the raw text. Preserve the original values beside any normalized analysis fields. A convenient display format is not evidence that the underlying record changed.

CSV values can contain punctuation, quoted text and line breaks. Use a CSV-aware reader rather than splitting every line at commas; our local fixture used Python’s documented CSV reader. In our synthetic test, a quoted comma in one fictional job title remains part of the title. This narrow check confirms the fixture was parsed as intended; it does not validate an unknown export's encoding or every possible spreadsheet behavior.

Keep a short exception list: missing associations, unreadable files, unspecified dates and required documents not located. Counts are useful for detecting a mismatch, but equal counts alone cannot prove that the right records or document versions survived. For example, three readable job rows could still contain an unintended duplicate while a needed opportunity is missing. Compare recognizable records and their associations as well as totals, and keep the reason for each unresolved discrepancy.

Finish with a usable archive, not a migration promise

Before treating your history as preserved, confirm that the needed categories are readable, important relationships are understood and unresolved items are recorded. Retain necessary documents separately where their presence in the archive has not been established. An export may support your own review without being directly importable into a different tracker. We did not test restoration into Huntr or another product, and no import-ready file is supplied here.

For active applications, preserve original employer confirmations alongside your own notes. Keep future tasks separate from completed events so a reminder does not become a claimed submission. Then use the archive to choose your next action, such as reviewing an unresolved follow-up, while finding separate opportunities on LandOffer. Exporting records does not itself apply, contact an employer or change an application's status.

Sources and Further Reading

Public documentation checked October 20, 2026. Maya and all CSV records are fictional. No private account, export, application, document upload, account change or message was accessed or performed.