Switching

The software is the easy part. The data is the switch.

Agencies do not stay on an ATS they dislike because it is good. They stay because a decade of candidates, clients and history lives inside it and moving that feels like a quarter of lost billing. Here is how the move actually runs.

Before you commit

The four questions, answered honestly.

Including the one most vendors dodge, because the honest answer is “we cannot know yet.”

Question

How long until we are live?

It depends entirely on the source, and anyone who quotes you a number before seeing your data is guessing. A clean export from a modern ATS is a different job from eleven years of spreadsheets. We look at what you have first, then scope it with you — and the scope is agreed in writing before any work starts.

Question

Who actually does the migration?

We do the extract, mapping and load. You do the part only you can do: deciding what is worth bringing, who owns which records, and which fields your team actually uses. That division is the whole reason migrations fail — firms get handed a CSV template and told to sort it out themselves.

Question

What happens to the records we do not move?

They stay where they are. Leaving a decade of dead candidates behind is usually the right call, and we would rather argue for a smaller migration that lands than a complete one that takes a quarter. Nothing is deleted from your current system by us.

Question

Can we run both systems for a while?

Yes, and most firms should. Keep the incumbent read-only while your recruiters work Poach, so nothing is riding on a single cutover weekend. We plan the overlap window with you rather than forcing a hard switch.

Division of labour

Migrations fail when the firm is handed a CSV template.

The work splits cleanly. We take everything that is mechanical; you keep the judgement calls only your desk can make.

We do5
Read your export and map it to the recruiting model
Load candidates, clients, companies, jobs and history
Run duplicate detection and company matching
Parse resumes into structured, searchable people
Reconcile the counts with you before you rely on it
You do5
Get us the export, or the credentials to pull one
Say what is worth bringing and what is dead weight
Confirm record ownership across the team
Name the fields your desk actually works from
Spot-check the records you know best
How the cutover runs

Nothing rides on a single weekend.

01

Load and reconcile

Your data goes in and the counts that matter — people, companies, jobs, placements — get checked against the source before anyone works from it.

02

Run in parallel

Your team works Poach while the incumbent stays available read-only. Nobody is stranded if something is missing on day three.

03

Close the old one

You cancel the incumbent when your recruiters have stopped opening it — not on a date we picked to make a case study.

The uncomfortable part

Sometimes we will tell you not to switch.

If your desk depends on something Poach does not do, or your data is in a shape where the honest migration estimate is larger than the problem you are trying to solve, we would rather say so on the first call than six weeks into an implementation.

Tell us what your team relies on today. If it is a bad fit, that is a five-minute conversation and you have lost nothing.

Worth telling us aboutOn the first call
Where your data livesIncumbent ATS, CRM, spreadsheets, a database
What your team lives in dailyDialer, mailbox, job boards, LinkedIn
Anything that must not breakThe one workflow the desk runs on
Who needs accessAnd at what level
No obligation

Show us the data before you decide anything.

What we can move