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 मिनिटांचे वाचन · जुलै २०२६ रोजी अपडेट केले · 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.

या पृष्ठावर

The three arrays that make it whole
Safe by construction
Step by step
What you gain on the other side
इंटरफेस ब्लूप्रिंट आणि परस्परसंवाद प्रवाह
वारंवार विचारले जाणारे प्रश्न

तुम्ही कोणत्या सिस्टमवरून स्थलांतरित होत आहात?

शोधण्यासाठी टाईप करा — विक्रेता निवडल्याने त्यासाठीचे समर्पित स्थलांतर मार्गदर्शक उघडते. प्रत्येक मार्ग त्याच आयातक मध्ये उतरतो, त्याच प्रामाणिक बॅच मर्यादा आणि डीडुप नियमांसह.

अवलंबित्व नकाशा — नक्की काय आयात होते

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

इंटरफेस ब्लूप्रिंट

पृष्ठभागाची संरचनात्मक योजना — पॅनेल, पदानुक्रम आणि परस्परसंवाद क्षमता. एक करार, स्क्रीनशॉट नाही.

तुमचा सध्याचा ATS

CSV / JSON / API निर्यात

सेटिंग्ज → डेटा निर्यात, किंवा सपोर्टला विचारा — डेटा कायदेशीररित्या तुमचा आहे.

→

नमुना JSON करार

jobs[]candidates[]applications[]

फील्डची नावे नमुन्याशी तंतोतंत जुळली पाहिजेत; अतिरिक्त काहीही दुर्लक्षित केले जाते. स्प्रेडशीट, लहान स्क्रिप्ट किंवा कोणत्याही बुद्धिमान सहाय्यकासह पुन्हा आकार द्या: “या फॉरमॅटमध्ये रूपांतरित करा”.

→

Expertini ATS च्या आत

नोकऱ्या → मसुदे उमेदवार → टॅलेंट पूल अर्ज → फनेल, टप्पे मॅप केलेले

ईमेलद्वारे डीडुप्लिकेट केलेले · तुमच्या क्लिकशिवाय काहीही प्रकाशित होत नाही.

आकृती १ — मायग्रेशन पाइपलाइन: तुमच्या सध्याच्या सिस्टममधून एक्सपोर्ट करा, नमुना JSON करारासाठी पुन्हा आकार द्या, आणि डीड्युप (dedupe) व स्वयंचलित स्टेज मॅपिंगसह इम्पोर्ट करा.

परस्परसंवाद प्रवाह — स्थिती, प्रमाणीकरण, अभिप्राय

खालील प्रत्येक स्थिती सर्व्हर-साइडवर लागू केली जाते; इंटरफेस ती रिपोर्ट करतो, तो निर्णय घेत नाही.

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

आकृती २ — परस्परसंवाद प्रवाह: नेव्ही = स्थिती, सोनेरी = सर्व्हर-लागू गेट्स, हिरवे = पुष्टी केलेले परिणाम; टॅग्स एज केसेस आणि त्यांचा अभिप्राय सूचीबद्ध करतात.

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.

वारंवार विचारले जाणारे प्रश्न

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.

एका दृष्टीक्षेपात

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

तुमच्या स्वतःच्या भरतीवर migrate from workable पहा.

३०-मिनिटांच्या डेमोसाठी वास्तविक नोकरीचे वर्णन आणा — विनामूल्य चाचणी समाविष्ट आहे.

डेमो बुक करा