Migrate your ApplicantStack data

Positions are the primary organizational unit in ApplicantStack. We export all job metadata including title, description, status, job board distribution settings, and opening count. These map directly into the destination ATS's Job/Position object.

Candidate records include name, contact info, application date, resume, status, source, and notes. We map these 1:1 into the destination ATS. We flag records that appear to be duplicates based on email matching, as ApplicantStack's duplicate detection has known limitations.

Questionnaires are ApplicantStack's equivalent of custom application forms. Responses are stored as field-value pairs tied to the candidate record. We extract all custom field responses and map them to corresponding custom properties in the destination ATS, creating the properties if they do not exist.

User roles (Administrator, Recruiter, Hiring Manager) control access to jobs and candidates. We export role assignments and map them to the nearest equivalent role model in the destination platform. Users who are only Hiring Managers may need to be re-created manually depending on destination role architecture.

When ApplicantStack Onboard is used, new hire onboarding packets include I-9 data, tax forms, and custom onboarding documents. We extract these as structured records and separate document blobs. The document attachments are migrated as files; structured field data maps into the destination HRIS or ATS onboarding module.

ApplicantStack supports configurable pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected). We export the full pipeline configuration and the per-candidate stage history, replaying the progression timeline in the destination system where supported.

Resume files, cover letters, and any uploaded documents are extracted from candidate records as binary blobs. We preserve file names and attach them to the corresponding candidate record in the destination platform. File format conversion is applied where the destination requires a different format.

ApplicantStack exports are generated via the Reports builder in CSV/Excel format. We use these exports as our primary data source for migration, parsing the flat-file structure and normalizing it into relational objects. Custom reports created by the customer are included in the export scope where accessible.

Job board distribution settings (Indeed, JobTarget, custom branded boards) are configuration data that do not carry forward to a new ATS. The job postings themselves migrate as content; the distribution connections must be re-established in the destination platform manually.

ApplicantStack stores email templates used in candidate communication sequences. We export template content and map variable placeholders. Automated trigger logic does not export; these sequences must be rebuilt in the destination ATS using the migrated template bodies.

Custom properties added to Candidates or Jobs beyond the standard schema are captured as key-value pairs. We map them to custom fields in the destination ATS, creating the destination properties during import and populating them with the migrated values.

Candidate tags and job labels are exported as flat tag arrays. We preserve all tags and apply them to the corresponding records in the destination system. Tag merge logic handles cases where identical tags use different naming conventions across systems.