Migrate your Ashby data

Candidates is the core object in Ashby. We export all candidate records including contact info, status, source, and activity history via the candidates endpoint. Custom fields on candidates are mapped individually.

Applications link candidates to specific jobs and openings. We preserve the application record, including submission date, current stage, and all stage transitions. Applications are the primary unit for pipeline reporting.

Jobs are the top-level job postings. We export job records including title, department, team, location, status, and job board distributions. Job structure including opening counts maps cleanly to destination job objects.

Openings represent individual headcount slots within a job. We export all openings and map them to the destination job's opening structure. Multi-opening positions require individual record mapping.

Offer records including compensation details, start dates, and e-signature status export via the offers API. We preserve offer history and status transitions for compliance and audit purposes.

Ashby users including recruiters, hiring managers, and admins export via user.list. Role assignments map to destination permission structures. Note that elevated seats use a separate pricing model that may affect how many users we include in migration scope.

Interview plans export with their stage structures and activity definitions. Automated activity triggers (like sending booking links) are tier-gated and may not be importable. We preserve the plan structure and manually document automation triggers for manual recreation.

Email sequences export with templates and stage definitions. Automation rules tied to sequences are preserved where available. Live-running sequences require scoping to determine whether to migrate as active or archived based on destination platform capabilities.

Assessments from integrations like HackerRank and CoderPad link to Ashby but live in third-party systems. We export assessment results attached to applications and map the association. The assessment itself remains in the external tool.

Custom fields on candidates, applications, and jobs are enumerated via customField.list. We export all custom field values and map them to destination custom fields. Customers often have dozens of custom fields requiring individual mapping decisions.

Activity records including emails, notes, calls, and scorecards export per candidate and application. Automated activities tied to interview plan triggers require tier verification. We export all activity history for records in migration scope.

Candidate surveys and questionnaire responses export via the activities API. Survey templates are preserved but may require configuration in the destination system. We map response data to the corresponding survey structure.

Department records export and map to the destination HR structure. Department hierarchy and department-level permissions are preserved in the export.

Team records within departments export and map to destination team structures. Team assignments on jobs and users are preserved in the migration.

Report definitions export as CSV via the report endpoint. Dashboard layouts do not export via API. We export all report data as CSV including funnel analytics, pipeline metrics, and time-to-hire data. Dashboard reconstruction requires manual rebuilding in the destination.