Migrate from JazzHR to Expertini ATS
INTEGRATIONS · EXPERTINI ATS

Migrate from JazzHR to Expertini ATS

Move your jobs, candidates, and live pipeline out of JazzHR and into Expertini ATS in an afternoon — drafts first, deduplicated, with your funnel stages mapped automatically and nothing published without your click.

読了目安 3 分 · 2026年7月更新 · Expertini Editorial

Leaving an ATS feels riskier than it is. Your data in JazzHR is legally yours, every mainstream system can export it, and Expertini's Third-Party ATS Import is built to receive exactly that export: jobs arrive as drafts so nothing goes live by accident, candidates land in the talent pool deduplicated by email, and your in-flight pipeline — who is at which stage on which job — is rebuilt rather than abandoned. The importer is the same one used for every migration source, so the path out of JazzHR is a well-trodden one, not a special case.

This page is the JazzHR-specific route through the general migration guide. Expertini ATS is an independent product; JazzHR is a trademark of its owner, and nothing here requires their cooperation — only the export they already provide to every customer.

このページ内

  1. Get your data out of JazzHR
  2. Reshape it to the sample JSON
  3. Upload in safe batches
  4. What lands where
  5. インターフェース設計図 & 操作フロー
  6. よくある質問

どのシステムから移行されますか？

入力して検索 — ベンダーを選択すると専用の移行ガイドが開きます。どのルートでも同じインポーターに接続され、明確な一括処理上限と重複排除ルールが適用されます。

依存関係マップ — インポートされる対象の詳細

Jobstitle, description, location, type, category, salary, experience & education levels — arrive as DRAFTS, nothing goes live by accident
Candidatesname, email, phone, title, location, skills, notes — into the talent pool, deduplicated by email
Applicationscandidate_email + job_external_id + stage + applied_at — rebuilds your funnel; foreign stage names ("phone screen", "offered", "onsite"…) map automatically, unrecognised ones land in Applied
Batch limits500 jobs and 2,000 candidates per upload — split bigger exports; duplicates are skipped, so overlapping batches are safe
CVsdon't travel through JSON — imported candidates carry their profile text; CVs can be added to records any time

インターフェース設計図

画面の構造的設計図 — パネル、階層構造、インタラクションのアフォーダンス。スクリーンショットではなく、仕様としての定義です。
現在のATS
CSV / JSON / APIエクスポート
設定 → データのエクスポート、またはサポートまでお問い合わせください。データは法的に貴社に帰属します。
→
サンプルJSONコントラクト
jobs[]candidates[]applications[]
フィールド名はサンプルと完全に一致している必要があります。余分な項目は無視されます。スプレッドシート、簡単なスクリプト、またはインテリジェントアシスタントを使用して「この形式に変換」と指示して整形してください。
→
Expertini ATS内
求人 → 下書き 候補者 → タレントプール 応募 → ファネル、ステージのマッピング
メールアドレスによる重複排除 · お客様がクリックするまで公開されません。
図1 — 移行パイプライン: 現在のシステムからエクスポートし、サンプルJSONスキーマに合わせて整形し、重複排除および自動ステージマッピング機能を用いてインポートします。

インタラクションフロー — 状態、検証、フィードバック

以下のすべての状態はサーバー側で適用されます。インターフェースはそれを報告するのみであり、決定するものではありません。
Export from JazzHRCSV/JSON/API export — usually Settings → Data export, or ask support; the data is legally yours
Reshape to the sample JSONspreadsheet save-as-JSON, a small script, or paste both files into an AI assistant: "convert to this format"
Upload & validatefield names must match the sample; anything extra is ignored, errors are named
Dedupe + stage mappingcandidates matched by email; foreign stage names map onto your pipeline automatically
Working pipelinejobs as drafts, talent pool populated, funnel rebuilt — review, then publish
Over the batch cap → split the file; overlapping batches are safe because duplicates skipUnknown stage name → lands in Applied, never lostField name mismatch → named validation error; nothing partial importsJobs import as drafts — nothing is published without your clickCVs can't ride in JSON — attach them to imported records afterwards
図2 — インタラクションフロー: 濃紺 = 状態、金 = サーバー強制ゲート、緑 = 確定した結果、タグはエッジケースとそのフィードバックを一覧表示。

01Get your data out of JazzHR

Export jobs and candidates from JazzHR — every mainstream ATS offers CSV, JSON, or API export, usually under a Settings → Data export area, and their support team will produce a full export on request if the interface doesn't cover something. You have a legal right to your own data, and data-protection law in most jurisdictions obliges the vendor to hand it over in a usable format. Ask for jobs, candidates, and applications (the links between the two) — three files or one, either works.

02Reshape it to the sample JSON

The importer accepts a simple, documented JSON shape with three arrays: jobs, candidates, and applications. A spreadsheet with a save-as-JSON step works; a small script works; and the fastest path for most teams is pasting their export and our sample file into any AI assistant with the instruction "convert to this format". Field names must match the sample exactly — anything extra is simply ignored, so over-complete exports are fine as-is.

03Upload in safe batches

Upload on the in-app import page. Limits per upload: 500 jobs and 2,000 candidates — split bigger exports into batches. Duplicates are skipped, not duplicated, so overlapping batches are safe and re-running an upload after a fix costs nothing. Validation errors name the exact field rather than failing silently.

04What lands where

Jobs import as drafts with title, description, location, type, category, salary, and experience and education levels — you review and publish on your own schedule. Candidates arrive in the talent pool with name, email, phone, title, location, skills, and notes, deduplicated by email. Applications rebuild your funnel: JazzHR's stage names — "phone screen", "offered", "onsite", and dozens more — map automatically onto your pipeline stages, and anything unrecognised lands safely in Applied. CVs can't travel through JSON: imported candidates carry their profile text, and CV files can be added to any record afterwards.

よくある質問

Do I need JazzHR's permission or help to migrate?⌄
No. You export your own data with the export function every customer has, reshape it to the sample format, and upload. No API keys, no vendor cooperation, no overlap period required.
Will anything go live during the import?⌄
No. Jobs arrive as drafts and are published only when you choose. Candidates and applications are internal records — nothing is emailed to anyone during an import.
What happens to my pipeline stages?⌄
Stage names from other systems map automatically onto your pipeline — "phone screen", "offered", "onsite" and many more are recognised. Unrecognised names land in Applied rather than being lost.
What about CVs?⌄
CV files can't ride inside JSON. Imported candidates carry their profile text (searchable immediately), and you can attach CV files to any record afterwards — individually or via the bulk CV drop.
Is Expertini affiliated with JazzHR?⌄
No. JazzHR is a trademark of its owner. This page describes Expertini's own import tool receiving a standard data export that belongs to you.

概要

  • Jobs, candidates, and the live funnel — all three migrate
  • Jobs arrive as drafts; nothing publishes without your click
  • Candidates deduplicated by email — re-runs are safe
  • Foreign stage names map automatically; unknowns land in Applied
  • 500 jobs / 2,000 candidates per upload — batch bigger exports
  • No vendor cooperation, API keys, or overlap period needed

関連記事

Third-Party ATS ImportMove from Zoho Recruit, Greenhouse, Workable, Lever, iCIMS, JazzHR, Breezy, Manatal, Ceipal, or any other system — jobs, candidates, AND your live funnel, in one structured JSON upload. 🌱Migrate from GreenhouseMoving off Greenhouse? Bring your jobs, your candidates, and your live pipeline — including which stage every application was at — across in one structured upload. Migrate from WorkableLeaving Workable? Move jobs, candidates, and your live hiring funnel into Expertini in one upload — stages mapped, duplicates impossible, nothing published without review.

貴社の採用でmigrate from jazzhr to expertini atsをご確認ください。

実際の職務記述書をご用意のうえ、30分間のデモにご参加ください。無料トライアルが含まれています。

デモを予約
Expertini インテリジェント
現在オンライン
こんにちは！Expertiniのインテリジェント・プロダクトエキスパートです。ソリューションに関するご質問、採用ツールのガイダンス、進め方のご相談など、何でもお尋ねください。適切にご案内いたします。アカウント固有のお問い合わせは、support@expertini.comまでメールでご連絡ください。
メールをご希望ですか？お問い合わせはこちら →