Manage
Your CRM stays
the system of record
For agencies that want Jenny’s matching and sourcing without leaving the CRM or ATS they already use. Today you bring candidates, companies, applications and notes in by CSV, with column mapping, a preview and duplicate checks. A native connector for your system is built on request, as far as its API and the access you grant allow.
The problem
Two systems that disagree are worse than one
Your CRM or ATS holds years of candidates, notes and placements, and your team’s habits are built around it. Replacing it to get better matching means a migration, retraining and months of two systems running side by side.
Adding a tool next to it carries its own risk: two copies of the same person that drift apart, duplicates from repeated imports, and nobody sure which phone number is current. It only works when every import is reviewed and it is clear which system owns which data.
What changes
- Candidates you already know become searchable and matchable in Jenny without changing the system your team records in.
- Column mapping is suggested from the import template and common English, Dutch and French column names, and every match can be changed.
- Possible duplicates — the same e-mail, phone or LinkedIn URL, or for companies the same website domain — are never merged automatically.
- Earlier applications, notes and evaluations arrive as dated, attributed history, so past work counts as evidence when you match a job.
- Nothing is written back to your CRM or ATS, so Jenny cannot change the records your team relies on.
Who owns what · after a CSV import
Illustrative — fictional data- Your CRM
Contact details and consent
Kept up to date in your CRM
Copied in by import
- Your CRM
Stages and placements
Recorded by your team
Not written back by Jenny
- Imported
Notes and earlier applications
Imported as dated history
Used as evidence in matching
- Jenny
Match evidence and shortlists
Produced in Jenny
Summarise in your CRM when you put someone forward
- Jenny
CV versions and e-mail drafts
Generated and approved in Jenny
Download to share or file
How it works
01
Export from your CRM
Export candidates and, if you have them, companies, applications and notes as CSV. Comma, semicolon and tab-separated files are recognised.
02
Map the columns
Accept the suggested mapping or change it. Unmapped columns are not uploaded, and age or birth-date columns can never be imported.
03
Check and review
Every row is checked for errors, repeats and possible duplicates. Filter by issue, accept clean rows in one step and decide the rest one by one.
04
Promote in batches
Accepted rows become records, up to 200 per request. Promoting the same rows again changes nothing.
05
Work, then record
Match and source in Jenny, then record outcomes such as stages, placements and consent changes in your own CRM, which stays the system of record.
Worked example: Bringing a recruitment CRM export into Jenny
Illustrative — fictional data01 · Export three files
You export candidates, applications and notes from your CRM as CSV: about 2,400 candidates, each with its CRM id.
02 · Map the columns
Jenny suggests “GSM” as phone and “Talen” as languages. You change one mapping and leave a birth-date column unmapped, since it cannot be imported.
03 · Review duplicates
Candidate A and Candidate B share an e-mail address with existing records. You link Candidate A to the existing person and keep Candidate B separate, with a reason.
04 · Promote in batches
You accept the clean rows and promote them 200 at a time. Applications and notes appear as dated history on each candidate.
05 · Match a job
A Senior Financial Controller job for a logistics company in Antwerp comes in; matching quotes a 2023 interview note from the import as dated evidence.
06 · Update your CRM
You put Candidate A forward and record the stage in your CRM, which stays the system of record. The next export updates only what changed.
You provide
- CSV exports from your CRM or ATS: candidates, plus optional companies, applications and notes
- The name of the source system, so each record keeps its source id
- Your column mapping and your decisions on duplicates and errors
- CV files, uploaded separately where you need them
- For LinkedIn Recruiter: the CSV export and the job it belongs to
Jenny produces
- Candidate and company records that keep their source ids and original dates
- Earlier applications, notes, evaluations and interview feedback as dated history on each candidate
- Candidates from a LinkedIn Recruiter export added to the chosen job
- A summary per file: rows, errors, decisions and promoted records
Sources and their status
| CSV export from any CRM or ATS | Available | Candidates, companies, applications and notes, with mapping suggestions, a preview, duplicate checks and staged review. |
|---|---|---|
| LinkedIn Recruiter CSV export | Available | Imported into one job, with duplicate checks and a decision on every row. |
| Native connector for your system | On request | Built on request where your system offers API access and you grant it. None exists yet; what it could read or write depends on that API. |
What it depends on
- A CRM or ATS that can export CSV, and someone who can run the export
- CV files uploaded separately where you need them in Jenny
- A database that fits within 3,000 candidates per workspace
- For a native connector, on request: API access on your system’s plan and the permissions you grant for what it may read or write
Approval and privacy controls
- Possible duplicates are never merged automatically, and keeping a row as a separate person requires a reason.
- Imported candidates arrive marked do-not-contact, with consent unconfirmed, until you confirm their contact preferences; a do-not-contact flag from the source is always kept.
- A later import updates changed fields, but values a recruiter has verified are kept and every change is written to the candidate’s history.
- Age and birth-date columns cannot be mapped or imported.
- Staged rows are deleted when you cancel the import or when it expires (after 14 days by default); records already promoted stay.
Current limitations
- The import is one way: nothing is written back to your CRM or ATS, so outcomes are recorded there by hand.
- An import is a snapshot of the export; changes made later in your CRM arrive only with the next import.
- A workspace holds up to 3,000 candidates, and up to 200 rows are promoted per request.
- CV files and other attachments are not part of the CSV import; add CVs separately.
- No native connector exists for any CRM or ATS, and none is plug-and-play: compatibility depends on each system’s API and the access permissions granted.
- Applications from your old system become history on the candidate, not live pipeline records, and Excel workbooks need saving as CSV first.
Questions about crm/ats integrations
Which CRM or ATS does Jenny work with?
Any system that can export CSV. Jenny is designed to connect with existing systems, but no native connector exists yet, and how far one could go depends on each system’s API and the access you grant. Tell us which system you use on the integrations page (/integrations).
Which system owns which data?
Your CRM or ATS stays the system of record for contact details, consent, stages and placements. Jenny keeps what it produces — match evidence, shortlists, CV versions and e-mail drafts — and you record outcomes in your own system. Our guide to using AI alongside your existing ATS explains how to agree this before the first import.
What happens to duplicates?
Rows that share an e-mail address, phone number or LinkedIn URL with another row or an existing candidate are flagged, never merged automatically. You link the row to the existing person, or keep it separate with a short reason. Companies are matched on their source id and then on their website domain.
Can I run the import again later?
Yes. Records keep their source ids, so a later export updates only what changed in the source and skips rows that are unchanged or older than the earlier import. Values your team has verified are not overwritten.
What would a native connector do?
It would read the records you authorise through your system’s API instead of a manual export. Anything written back would depend on what that API supports and what you allow. Connectors are built on request; none exists yet, and we promise no dates.
Related features
- Candidate database reactivation
Turn your existing candidate database into new placement opportunities.
Early access - Job-to-candidate matching
From a job description to an explained shortlist — evidence, gaps and unknowns included.
Available - CV and job-description intake
Upload, paste or link a CV or job description; AI prefills it and you review it first.
Available - Recruitment pipeline
One pipeline per job, with a history of every stage move and who made it.
Available
See it on your own vacancies and candidates
A short call with the founder: we look at how you work today and show the workflows that fit.