INTEGRATIONS · EXPERTINI ATS

Migrate from Workable

Leaving Workable? Move jobs, candidates, and your live hiring funnel into Expertini in one upload — stages mapped, duplicates impossible, nothing published without review.

2 min read · Updated July 2026 · Expertini Editorial

Teams outgrow Workable in both directions — some need more depth than its simplicity offers, some need a price that isn't per-job. Either way, the thing that makes switching feel risky is the same: the candidates and pipelines accumulated inside it. Expertini's Third-Party ATS Import is built so that history survives the move: jobs land as drafts for review, candidates join the talent pool deduplicated by email, and the applications array rebuilds your funnel — every candidate re-attached to their job at the stage they were at when you exported.

Workable provides export paths for your own data, and reshaping that export to our documented JSON sample is deliberately unexciting work — a spreadsheet with a save-as step, or any script, or pasting both files into an AI assistant with "convert to this format". Workable is a trademark of its owner; moving your own data out of your own account is your right, and this page is the how-to.

▶ Watch the 30-second overview — no sign-up needed

Which system are you moving from?

Type to search — picking a vendor opens the dedicated migration guide for it. Every path lands in the same importer, with the same honest batch limits and dedupe rules.

Dependency map — what imports, exactly

Jobstitle, description, location, type, category, salary, experience & education levels — arrive as DRAFTS, nothing goes live by accident

Candidatesname, email, phone, title, location, skills, notes — into the talent pool, deduplicated by email

Applicationscandidate_email + job_external_id + stage + applied_at — rebuilds your funnel; foreign stage names ("phone screen", "offered", "onsite"…) map automatically, unrecognised ones land in Applied

Batch limits500 jobs and 2,000 candidates per upload — split bigger exports; duplicates are skipped, so overlapping batches are safe

CVsdon't travel through JSON — imported candidates carry their profile text; CVs can be added to records any time

Interface blueprint

Structural schematic of the surface — panels, hierarchy, and interaction affordances. A contract, not a screenshot.

Your current ATS

CSV / JSON / API export

Settings → Data export, or ask support — the data is legally yours.

→

The sample JSON contract

jobs[]candidates[]applications[]

Field names must match the sample exactly; anything extra is ignored. Reshape with a spreadsheet, a small script, or any AI assistant: “convert to this format”.

→

Inside Expertini ATS

jobs → drafts candidates → talent pool applications → funnel, stages mapped

Deduplicated by email · nothing publishes without your click.

Fig. 1 — the migration pipeline: export from your current system, reshape to the sample JSON contract, import with dedupe and automatic stage mapping.

Interaction flow — states, validations, feedback

Every state below is enforced server-side; the interface reports it, it doesn't decide it.

Export from WorkableCSV/JSON/API export — usually Settings → Data export, or ask support; the data is legally yours

Reshape to the sample JSONspreadsheet save-as-JSON, a small script, or paste both files into an AI assistant: "convert to this format"

Upload & validatefield names must match the sample; anything extra is ignored, errors are named

Dedupe + stage mappingcandidates matched by email; foreign stage names map onto your pipeline automatically

Working pipelinejobs as drafts, talent pool populated, funnel rebuilt — review, then publish

Over the batch cap → split the file; overlapping batches are safe because duplicates skipUnknown stage name → lands in Applied, never lostField name mismatch → named validation error; nothing partial importsJobs import as drafts — nothing is published without your clickCVs can't ride in JSON — attach them to imported records afterwards

Fig. 2 — interaction flow: navy = states, gold = server-enforced gates, green = confirmed outcomes; tags list the edge cases and their feedback.

01The three arrays that make it whole

Most "migrations" move jobs and stop. Ours moves three linked sets: jobs (title, description, location, type, salary, experience and education levels), candidates (name, email, phone, title, location, skills, notes), and applications (candidate email + old job id + stage + applied date). That third array is the difference between starting over and continuing — your open roles arrive with their applicants already sorted into stages.

02Safe by construction

Imported jobs are drafts until you publish them, so there is no accidental double-listing during cut-over. Candidates are deduplicated by email against everything already in your database. Re-uploading a corrected file is completely safe — duplicates are skipped and reported, never created. Stage names Workable uses map automatically onto Expertini's pipeline; anything unrecognised lands in Applied.

03Step by step

Export jobs and candidates from Workable. Download the sample JSON from the import page — it shows every field for all three arrays. Reshape, upload, read the per-row report (imported / already present / invalid, with reasons). Review your drafts, publish on your schedule, and your funnel is live in Expertini. Attach CV files any time afterwards — individually, or in bulk from a Dropbox/OneDrive folder with the cloud CV import.

04What you gain on the other side

Beyond price: an own candidate database with CV parsing and resume scoring built in, network job distribution with no per-posting fees, assessments and video interviews in the same subscription, and a data export that keeps the exit door as open as the entrance — the courtesy we're extending to Workable here is one we extend to ourselves.

Frequently asked questions

How do I get my data out of Workable?⌄

Workable offers export tooling and, where needed, a support request for your full data — it's your data by right. The export then reshapes to our documented JSON sample.

Do application stages survive the move?⌄

Yes. The applications array carries a stage per application, and common stage vocabularies map automatically onto Expertini's pipeline stages. Unmapped names default safely to Applied.

Is there a size limit?⌄

Per upload: 500 jobs, 2,000 candidates, 2,000 applications — and batching is safe because duplicates are skipped, so larger migrations just run as several uploads.

What does it cost?⌄

Included in every plan — no per-record fees, no paid migration service. See pricing.

At a glance

Jobs, candidates, and applications with stages — the full funnel moves
Workable stage names auto-mapped; unknowns land safely in Applied
Drafts-first publishing — no accidental double listings
Email dedupe makes re-uploads and batching risk-free
CVs attachable afterwards, including bulk cloud import
Included in every plan; most moves finish in an afternoon

See migrate from workable on your own hiring.

Bring a real job description to a 30-minute demo — free trial included.

Book a demo