WizzHire

WizzHire ATSWorks with Claude through the WizzHire connector.

Move your candidates out of your old ATS. Your AI assistant does the typing. You approve every step.

1.Three steps, and nothing saves until you say go. The first prompt only reads and plans.

  1. Connect WizzHire to your assistant

    Add the WizzHire connector once and allow changes when it asks. It works with the access you already have.

  2. Attach your export and paste the first prompt

    A CSV or Excel export from your old ATS. Publish or pause the jobs in WizzHire first.

  3. Read the plan, answer, then say go

    Each later prompt does one part: the candidates, their ratings and notes, then a check against your file.

2.One row per candidate and job is enough. Messy is fine: old stage names, ratings out of 10, two date formats.

NameEmailJobJob statusStageAppliedRatingTagsNotes
2Lejla Hodžićlejla.hodzic@example.baSenior Java DeveloperOpenOffer02/09/20269/10java;spring;referralOffer sent 20 Oct, waiting on notice period
3Marko Petrovićmarko.petrovic@example.rsSenior Java DeveloperOpenFinal interview2026-09-048/10java;kafkaStrong system design, wants hybrid
4Emma Clarkeemma.clarke@example.comSenior Java DeveloperOpenFinal interview05/09/20268java;remote-okBased in Leeds, remote only
5Haris Mujićharis.mujic@example.baSenior Java DeveloperOpenTechnical interview2026-09-087/10java;springSalary expectation €3,800 net
6Ivana Kovačevićivana.kovacevic@example.hrSenior Java DeveloperOpenTechnical interview09/09/2026java;awsTest task sent 15 Oct
7Tomás Ruiztomas.ruiz@example.comSenior Java DeveloperOpenTechnical interview2026-09-116/10java;relocationAsked for relocation support
8Amar Begićamar.begic@example.baSenior Java DeveloperOpenPhone screen12/09/2026javaCall booked for next week
9Sara Novaksara.novak@example.hrSenior Java DeveloperOpenPhone screen2026-09-157java;spring;referralReferred by Daniel Price
10Nikola Jovanovićnikola.jovanovic@example.rsSenior Java DeveloperOpenPhone screen16/09/2026java;kotlin
11Dino Halilovićdino.halilovic@example.baSenior Java DeveloperOpenApplied2026-09-18java
12Ana Marićana.maric@example.hrSenior Java DeveloperOpenApplied19/09/2026java;remote-okAlso applied for QA Engineer
13Kenan Softićkenan.softic@example.baSenior Java DeveloperOpenApplied2026-09-22java;spring
14Oliver Hughesoliver.hughes@example.comSenior Java DeveloperOpenSourced23/09/2026java;contractContractor, available from January
15Mirza Delićmirza.delic@example.baSenior Java DeveloperOpenSourced2026-09-25java
16Jelena Ilićjelena.ilic@example.rsSenior Java DeveloperOpenHired01/08/20269/10java;referralStarted 1 Oct
17Adnan Hasićadnan.hasic@example.baSenior Java DeveloperOpenDisqualified2026-08-124/10javaNot enough Spring experience
18Luka Babićluka.babic@example.hrSenior Java DeveloperOpenDisqualified14/08/20265javaSalary too high
19Maja Pavlovićmaja.pavlovic@example.rsSenior Java DeveloperOpenDisqualified2026-08-20javaWithdrew
20Ana Marićana.maric@example.hrQA EngineerOpenTechnical interview2026-09-198/10qa;automationStrong Playwright
21Belma Ahmetovićbelma.ahmetovic@example.baQA EngineerOpenFinal interview03/09/20268/10qa;automationMeets Daniel Price on Friday
22James Porterjames.porter@example.comQA EngineerOpenTechnical interview2026-09-067qa;manualTest task done, good bug reports
23Selma Karićselma.karic@example.baQA EngineerOpenTechnical interview10/09/20267/10qa;referral
24Petra Horvatpetra.horvat@example.hrQA EngineerOpenPhone screen2026-09-13qa;automation
25Edin Mehićedin.mehic@example.baQA EngineerOpenPhone screen17/09/20266/10qaPart time until December
26Stefan Nikolićstefan.nikolic@example.rsQA EngineerOpenApplied2026-09-20qa;manual
27Lana Šarićlana.saric@example.hrQA EngineerOpenApplied24/09/2026qa;remote-ok
28Lana ŠarićLana.Saric@Example.hrQA EngineerOpenApplied2026-09-26qaApplied again through the career page
29Aida Kurtovićaida.kurtovic@example.baQA EngineerOpenApplied27/09/2026qa
30Ben Walshben.walsh@example.comQA EngineerOpenSourced2026-09-29qa;automationContacted on LinkedIn, interested
31Ivan Radićivan.radic@example.hrQA EngineerOpenDisqualified10/08/20263/10qaNo automation experience
32Nermina Imamovićnermina.imamovic@example.baQA EngineerOpenDisqualified2026-08-185/10qaTook another offer
33Milica Stankovićmilica.stankovic@example.rsQA EngineerOpenDisqualified22/08/2026qaNo reply after phone screen
34Robert Lanerobert.lane@example.comProject ManagerClosedHired2026-06-029/10pm;referralStarted 1 Aug
35Emina Zukićemina.zukic@example.baProject ManagerClosedDisqualified05/06/20267/10pmSecond choice, keep in touch
36Goran Lukićgoran.lukic@example.rsProject ManagerClosedDisqualified2026-06-076pm
37Tea Jurićtea.juric@example.hrProject ManagerClosedDisqualified09/06/2026pm;agile
38Faruk Osmanovićfaruk.osmanovic@example.baProject ManagerClosedFinal interview2026-06-117/10pmRole closed before final round
39Hannah Pricehannah.price@example.comProject ManagerClosedPhone screen14/06/2026pm
40Vedran Kosvedran.kos@example.hrProject ManagerClosedApplied2026-06-16pm
41Dženana Smajićdzenana.smajic@example.baProject ManagerClosedApplied18/06/2026pm;agile
Cells the assistant has to read carefully40 rows, 11 columns

Example. Names and figures are made up.

Name, Email, Phone
Candidate
Job
Published or paused job
Stage
Applied, Screening or Interview
Applied
Applied date
Source
Source, marked as imported
Rating, out of 10
Team note
Tags, Notes
Team note
Closed jobs, Hired, Disqualified
Stays in your file

Try it with our example first.

Download the example file

Or as CSV: Candidates

3.The four prompts. Paste them in order. Change the words to fit your file.

  1. Plan the move

    Reads the export, matches your jobs and stages, and checks every row without saving.

    You get backA plan in short tables and the questions it needs you to answer.

    I've attached a candidate export from our old ATS. Plan how to move it into WizzHire, but don't save anything yet.
    
    1. Tell me what each column is.
    2. Match each job to a published or paused job in WizzHire. List any job with no match, and any job the file marks as closed.
    3. Match the old stages to the stages of that job in WizzHire. List any stage with no match.
    4. Leave out people who were hired or rejected, and tell me how many.
    5. Check the rest with a dry run and show me duplicates and rows with problems.
    
    Then wait for my go.
  2. Bring the candidates over

    Adds each candidate to their job, in the matched stage, with the date they applied.

    You get backWhat was added per job and stage, and every row it skipped with the reason.

    Go ahead with the plan.
    
    - Add each candidate to their job, in the matched stage, with the date they applied and where they came from.
    - Someone who applied for two jobs goes into both.
    - The same email on the same job is one person, whatever the capitals. Skip the second row.
    - Don't email anyone.
    
    Finish with what you added per job and stage, and anything you skipped and why.
  3. Keep the ratings and notes

    Puts the old rating, tags and notes on each candidate as a note your team can read.

    You get backHow many notes landed per job.

    Now the Rating, Tags and Notes columns. On each candidate you added, leave one team note that starts with "From our old ATS" and holds the rating out of 10, the tags and the note.
    
    Don't rate anyone. Our team rates again in WizzHire.
    
    Tell me how many notes you added per job.
  4. Check it matches

    Compares WizzHire with your file, so you can switch the old ATS off with confidence.

    You get backCounts side by side and a list of anything that differs.

    Compare the file with WizzHire now: candidates per job and per stage, leaving out the closed job and the people who were hired or rejected.
    
    List anything that doesn't match.

What your assistant will not do. It works inside the same rules as you.

Save before you say go
The first prompt reads and checks. Nothing lands until you answer the plan.
Email your candidates
Nobody gets an email because you moved. No form, document request or interview invite goes out.
Screen the people you bring over
No AI screening or stage automation runs on them. They arrive as your team left them.
Rate in your team's name
Old ratings stay as notes. Ratings in WizzHire are your team's own.
Overwrite what you have
Someone already on the job is skipped and named, never changed.
Reach past your access
It can only do what your own account can do in WizzHire.

Questions

Do I need to set up the jobs first?

Yes. Publish or pause each job in WizzHire, with its stages, before the first prompt. The plan matches your old jobs to them and names any it cannot find.

What happens to people we hired or rejected?

They stay in your file. The plan counts them, so you know exactly what was left out. The same goes for every row of a job that is already closed.

What about the CVs?

The prompts bring over what is in the spreadsheet. Edit a candidate in WizzHire to add their CV.

Will candidates notice that we moved?

No. Nobody is emailed, and no form, document request or interview invite goes out because of the move.

What if someone applied twice?

The same email on the same job is one person, even written with different capitals. The second row is skipped and named. Someone who applied for two different jobs goes into both.

How big can the export be?

Big exports go in batches. Ask your assistant to split the file, and run the same prompt again for the next part. Someone already brought over is skipped the second time.

Questions about your own file? Ask in a demo, or start a free trial and try the prompts on the example.

Start a free trial