Expertini Job Site Import
Bring your whole Expertini job site account into the ATS — company profile, live listings, applications, candidates and their CVs, reviews, candidate alerts and followed candidates. Listings are adopted, never duplicated.
If your company already posts on an Expertini country job site, you have a head start most teams switching to an applicant tracking system do not: your profile, your vacancies, the people who applied to them and the CVs they sent all exist already. The Expertini Job Site Import brings that account across into your ATS workspace, so day one in the new system starts with your real hiring history rather than an empty dashboard and a re-typing job.
The gap this closes is the classic migration dead zone: the week where jobs live in one place, applications land in another, and nobody is sure which listing is the source of truth. Because both systems are part of Expertini, live listings are adopted rather than copied — the job site listing and the ATS job become the same record, so applications flow straight into your hiring pipeline without a duplicate ever being created. It ships natively in every subscription: no connector to buy, no third-party sync tool, no per-seat add-on.
On this page
- What gets imported
- Your candidates' CVs come too — as files, not links
- Why adoption beats duplication
- How to run it
- After the import
- Connection architecture
- Write semantics and data flow
- Operational considerations
- Placement in the integration topology
- Interface blueprint & interaction flow
- Frequently asked questions
01What gets imported
You choose what to bring across, and everything is selected by default because a partial migration is usually an accident rather than a decision. The import covers your company profile as candidates see it — name, description, logo, contact details, social links, headquarters, founding year and company size — plus your job listings, the applications on them, the candidates behind those applications with their CV files, your employer reviews and any replies you wrote, your saved candidate alerts, and the candidates you had followed.
Live listings arrive published and adopted. Listings whose closing date has already passed arrive as closed history rather than being resurrected — you keep the record and the applications, without a dead vacancy going live again. Applications land in your pipeline at the stage that matches their old status, with their original application date preserved so your reporting and your data-retention clock both start from when the person actually applied, not from the day you migrated.
02Your candidates' CVs come too — as files, not links
Every CV attached to an imported application is copied into the ATS's own document storage and re-read so its text is searchable and scoreable straight away. It is deliberately a copy rather than a link back to the job site: that folder on the country site is served without authentication, and pointing at it would have imported that exposure into a system where every other document route is scoped to your organisation.
If a CV cannot be read — an old file saved with the wrong extension, or one no longer on disk — you are told which and why, in the import result. The application still comes across with the file attached; only search and scoring on its contents are affected. Re-running the import repairs any CV whose text failed to extract on an earlier pass, so you never have to delete records to fix one.
03Why adoption beats duplication
Most ATS migrations copy jobs into the new system and leave the originals running, which splits your applicant flow in two and quietly double-counts vacancies. Adoption means one record, one apply flow, one set of metrics. Candidates who bookmarked a job or found it through Google keep landing on a working page, your listings keep the search visibility they have already earned, and there is no cut-over date where applications fall between systems.
Every imported record also carries where it came from, so the import is re-runnable without ever creating a second copy — run it again and only what is genuinely new comes across. Large accounts import in passes rather than one enormous transaction, and the result tells you plainly how much is left to bring.
04How to run it
Sign in to the ATS and open the app, or come straight from the job site: signing in there offers you a one-click hand-off that recognises your account on arrival. Either way you confirm which job site account is yours, tick what to bring, and run it. Nothing is guessed silently — the result names what came across, what was skipped and why, and what is still waiting.
Your job site password is never involved. The hand-off is a short-lived, single-use invitation, not a credential copy, and you set an ATS password of your own afterwards if you want one.
05After the import
Imported alerts arrive paused, with an explanation — an alert saved years ago should not start emailing you on the day you migrate. Employer reviews and your replies come across as history you can read. Followed candidates keep working through Talent Search, including telling you honestly if someone has since chosen not to be listed.
From there it is an ordinary ATS: enrich each job with screening questions and pipeline stages, run CMS scoring on the applications that came across, or draft your next role with the job description builder and publish it to the careers site and the country network at once.
Platform architecture & operations
A1Connection architecture
The connection model for this integration is stated honestly on its card: where a public API exists it is used with your own account and consent, and where a vendor requires a partner agreement the page says so instead of showing a Connect button that cannot work.
Once available, credentials follow the platform standard: encrypted at rest, presence-flag display, immediate removal on disconnect.
A2Write semantics and data flow
Every data movement is an explicit action with a logged result. Writes happen on your click — or automatically only where you enabled a rule (auto-push on hire is off by default, per-provider). Reads — imports of people, accounts, or files — run when you press Import, deduplicate against what you already have (clients by name, people by email), skip rather than overwrite, and report created-versus-skipped honestly, which is why re-running any import is safe by design.
Each action writes a row to the app-activity journal (ats_app_activity): what ran, when, for which record, and the outcome — including the vendor's own error text verbatim when something fails. Usage reporting inside the ATS aggregates that same journal, so integration reporting and integration reality cannot diverge.
Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.
A3Operational considerations
Connections are organisation-level and gated to owner and admin roles; recruiters use the features a connection powers but cannot connect, disconnect, or reconfigure. Disconnecting removes stored credentials immediately and stops the dependent features visibly, not silently. Data already imported stays yours and editable.
Imported people arrive marked as imported with conservative privacy defaults — no consent is assumed for anyone who never filled in your application form, and retention defaults apply. Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.
A4Placement in the integration topology
This integration is live in the registry today. One connection per provider unlocks every feature it powers, and the topology grid below shows the neighbouring connectors in the same capability area — statuses come from the same registry that drives the in-app hub, so this page can never claim more than the product does. For anything the catalogue does not cover, Webhooks and Zapier are the generic, documented escape hatch.
Dependency map
Interface blueprint
Interaction flow — states, validations, feedback
Frequently asked questions
Will importing create duplicate job listings?⌄
Do my applications and candidates come across, or just the jobs?⌄
What happens to jobs that have already closed?⌄
Do I lose the search ranking my listings already have?⌄
Is my job site password moved to the ATS?⌄
What if a CV cannot be read?⌄
Is there an extra charge for the import?⌄
What if I post on more than one Expertini country site?⌄
At a glance
- Profile, logo, contact details and social links brought across
- Live listings adopted, never duplicated — closed ones kept as history
- Applications land in your pipeline at the right stage, with their original dates
- Candidate CVs copied into ATS storage and re-read for search and scoring
- Reviews and replies, candidate alerts and followed candidates included
- Re-runnable — only what is new comes across, and unreadable CVs self-repair
- Your job site password is never moved; the hand-off is a single-use token
- Included in every subscription, no migration fee
See expertini job site import on your own hiring.
Bring a real job description to a 30-minute demo — free trial included.
Book a demo