Migrate from Workable
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 na pagbasa · Na-update noong Hulyo 2026 · Editoryal ng Expertini

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.

Aling sistema ang iyong nililipatan?

Mag-type upang maghanap — ang pagpili ng vendor ay magbubukas ng nakatuong gabay sa paglipat para rito. Ang bawat landas ay dumarating sa parehong importer, na may parehong tapat na mga limitasyon sa batch at mga panuntunan sa dedupe.

Mapa ng pagdedepende ng — kung ano ang eksaktong nai-import

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

Blueprint ng interface ng

Istraktura ng ibabaw — mga panel, hirarkiya, at mga kakayahan sa pakikipag-ugnayan. Isang kontrata, hindi isang screenshot.
Ang iyong kasalukuyang ATS
Pag-export ng CSV / JSON / API
Mga Setting → Pag-export ng data, o humingi ng suporta — ang data ay legal na sa iyo.
Ang sample na kontrata ng JSON
mga trabaho[]mga kandidato[]mga aplikasyon[]
Ang mga pangalan ng patlang ay dapat na eksaktong tumugma sa halimbawa; ang anuman sa labas nito ay binabalewala. Baguhin ang hugis gamit ang isang spreadsheet, isang maliit na script, o anumang intelligent assistant: “i-convert sa format na ito”.
Sa loob ng Expertini ATS
mga trabaho → mga draft mga kandidato → pool ng talento mga aplikasyon → funnel, nakamapang mga yugto
Na-deduplicate sa pamamagitan ng email · walang naga-publish nang walang pag-click mo.
Lar. 1 — ang pipeline ng migrasyon: i-export mula sa iyong kasalukuyang sistema, baguhin sa sample na kasunduan sa JSON, i-import na may dedupe at awtomatikong pagmamapa ng yugto.

Daloy ng interaksyon — mga estado, pag-verify, feedback

Ang bawat estado sa ibaba ay ipinapatupad sa gilid ng server; iniulat ito ng interface, hindi ito nagpapasya nito.
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 — daloy ng pakikipag-ugnayan: navy = mga estado, ginto = mga gate na ipinapatupad ng server, berdeng = kumpirmadong mga kinalabasan; nililista ng mga tag ang mga edge case at ang kanilang 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.

Mga madalas itanong

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.

Sa isang sulyap

  • 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

Tingnan ang migrate from workable sa iyong sariling pag-hire.

Magdala ng totoong paglalarawan ng trabaho sa 30-minutong demo — kasama ang libreng pagsubok.

Mag-book ng demo
Expertini Intelligent
Online ngayon
Kumusta! Ako ang Intelligent Product Expert ng Expertini. Magtanong sa akin ng anuman tungkol sa aming mga solusyon, kumuha ng patnubay sa anuman sa aming mga Tool sa Pag-hire, o sabihin lamang sa akin kung ano ang sinusubukan mong gawin — ituturo ko sa iyo ang tamang direksyon. Para sa mga isyu na partikular sa account, mag-email sa support@expertini.com.