Migrate
Anyone looking at us already runs a desk on something else. So before the pricing and the trial: here is how your data gets in, how it gets back out, and which parts we have not solved. Including the ones we would rather you heard from us than found out in month two.
Getting in
A folder of CVs. The candidates screen has a Multiple CVs action. Drop the files in and each one becomes a candidate: the CV is read, the record is created, and you watch it happen per file rather than staring at a spinner. Queued, reading, creating, created. If one file fails it says so and the rest keep going, and the summary at the end counts what landed and what did not.
Companies, from a LinkedIn URL. Paste the company page when you add a client and the details are read out and enriched, instead of you retyping an address you already had.
What we do not have, and will not pretend to.
There is no CSV import, and no automated connector to Bullhorn, Vincere, Carerix or Otys. Nobody presses a button and watches the old system pour in. If your history lives in a database export, moving it is a conversation with us, not a feature you switch on. We would rather have that conversation before you sign up than after.
Getting out
We say cancel anytime on the pricing page. That is half a promise if your data stays behind, so the export is a button in the product, not a support ticket you file and hope for. Every list exports to CSV, by you, whenever you want.
| kandidaten-YYYY-MM-DD.csv | Candidates, with the columns you have on screen |
| clients-YYYY-MM-DD.csv | Clients, all of them or just the ones you select |
| hiring-managers-YYYY-MM-DD.csv | Hiring managers per client |
| open-jobs-YYYY-MM-DD.csv | Open jobs and their state |
| kpi-scorecard-[period].csv | Your scorecard: metric, actual, target, percentage |
| data-quality.csv | Who is missing what, and their completeness score |
Select rows and take just those, or take the lot. The candidate export writes whatever columns you have on screen, so you set the view and export exactly that:
The files come out UTF-8 with a byte-order mark and properly quoted, which is a boring sentence that means Excel opens them without turning the accent in a candidate's name into rubble. Small thing. It is also the thing that quietly ruins most exports.
The honest edge: the CSV carries fields, not documents. It records whether a candidate has a CV, not the CV itself. If you need the files out too, say so and we will sort it with you rather than let you find out at the worst possible moment.
The unknowns
How long it takes.
We do not know your data, so we are not going to print a number here. Ten thousand candidates from a clean export is a different afternoon than four years of free-text notes. Tell us what you are sitting on and we will tell you what we think, before you spend a euro.
Whether your notes and attachments come across.
We have not proven that end to end, so we are not claiming it. The CSV carries fields, not documents. What happens to your notes, files and CV documents depends on what your current system will hand over, and that is the first thing we would look at together.
Whether your export maps cleanly.
Every ATS names its fields differently and every agency has bent them into a shape that only makes sense in-house. Send us a sample export with the names scrubbed. We will map it against ours and tell you what fits and what falls on the floor.
None of this needs a call to find out. Mail support@polpohire.com with what you run today and roughly how many candidates are in it. You get a straight answer back, including the one where we tell you this is going to hurt and it might not be worth it.
Open the live demo, go to Candidates, hit Export. It is the real product on sample data, and the file lands in your downloads. No form, no call, nothing to verify first.