Skip to main content
Core. Migration and data import are a standard setup task, not AI. Because Exterview is an intelligence layer above your ATS, this is about bringing in the role and candidate data an evaluation needs, not replacing your system of record. A connected, ongoing ATS/HRMS feed is still coming, so today this data is brought in with your Customer Success team.
Migrate and import data

​
Before you start

You need admin access. A self-service bulk import and a connected ATS/HRMS feed are not available yet — see How to Connect Integrations for current connector status.

​
What Exterview needs

At a minimum, the roles you are hiring for and the candidates to evaluate against them. Everything else stays in your ATS or HRMS.

​
Steps

1

Map your roles

Bring your existing roles to your Customer Success facilitator, or map them to the structure defined in How to Define Your Org Structure.
Map roles
2

Provide your candidates

Share candidate resumes or a source list with your setup team during setup. Once you’re live, resumes can be added per job — individually or in bulk — or pulled from your internal candidate pool; see View and Manage Candidates.
Provide candidates
3

Confirm what is out of scope

Pipeline stages, offers, and record-keeping remain in your ATS. Exterview evaluates and reports; it does not take ownership of the applicant-tracking workflow.
Out of scope
4

Validate the import

Check that roles and candidates came in correctly before running evaluations.
Validate import

​
FAQs

No. Exterview is not an ATS. You bring in only the role and candidate data an evaluation needs; your ATS stays your system of record.
Not yet. A connected, ongoing sync is still coming — see How to Connect Integrations for current status. Until then, role and candidate data is brought in with your Customer Success team during setup.