Migrate from Teamtailor to Recruit CRM & ATS

Teamtailor Candidate records map directly to Recruit CRM Candidate. The mapping preserves all standard fields (name, email, phone, location) plus any custom fields discovered during the scoping pass. Candidate status in Teamtailor (active, rejected, hired) maps to Recruit CRM's Candidate Status field. Owner assignment migrates by resolving Teamtailor user email to Recruit CRM user ID.

Teamtailor Job records map to Recruit CRM Job Order. The mapping preserves job title, description, location, employment type, and salary fields where present. Job status (active, paused, closed) maps to Recruit CRM Job Order status. The Teamtailor job public URL is stored as a custom field for reference. Department assignment on the Teamtailor job maps to the Recruit CRM Organization or a tagged client if the Teamtailor multi-brand scope maps to a Recruit CRM client account.

Teamtailor Job Application records (linking a Candidate to a Job) map to Recruit CRM Job Application with the same relationship. Application status (applied, screening, interview, offer, hired, rejected) maps to Recruit CRM application stage. Rejection reason and source attribution migrate as custom fields. The application creation timestamp and last-activity timestamp migrate for reporting continuity.

Teamtailor candidate custom fields vary per-customer and have no metadata API, so we run a discovery pass on a sample of candidate records to enumerate field names and types before full export. Each discovered custom field is mapped to a typed Recruit CRM custom field on the Candidate module. Multi-select and checkbox fields map to Recruit CRM multi-select picklists; text fields map to text or textarea depending on content length.

Teamtailor job posting custom fields are scoped to the job object and differ from candidate custom fields. We discover these during the same scoping pass and map them to Recruit CRM Job Order custom fields. Job-level fields may include things like hiring manager, internal recruiter, or requisition approval status.

Teamtailor Departments function as a taxonomy tagging both jobs and candidates. In Recruit CRM, organizational tagging depends on whether the customer is using Organizations or Client accounts. For agency customers, Teamtailor Departments map to Recruit CRM Client records if the agency tracks placement clients; for in-house teams, they map to Recruit CRM Organizations for internal division tracking.

Teamtailor Location records tag jobs and candidates with geographic data. These migrate as a flat list to Recruit CRM Location or as address fields on Job Order and Candidate. If the Teamtailor instance uses location to filter candidate searches, we ensure the location values are consistent strings in Recruit CRM for search functionality to work immediately.

Teamtailor Users (recruiters and hiring managers) map to Recruit CRM Users by email match. We export the full user list and resolve each by email during import. Any Teamtailor user without a matching Recruit CRM account goes to a reconciliation queue for the customer admin to provision before candidate and job imports proceed, since owner assignments are required on most record types.

Teamtailor Interview Kits group structured questions tied to jobs for candidate evaluation. The API exposes questions per kit. We export kit names and question text and import them as Candidate Notes with a structured prefix (e.g., 'Interview Kit: [Kit Name]') or as Recruit CRM evaluation form entries if the destination tenant has evaluation forms configured. The kit-to-job linkage is documented for rebuilding as Recruit CRM evaluation forms post-migration.

Teamtailor stores candidate resumes, cover letters, and other files as upload objects with a URL reference. We fetch the actual file content via the upload URL and attach it to the corresponding Candidate record in Recruit CRM via the candidate attachment API. File type and original filename are preserved. If the Teamtailor upload URL has expired or requires re-authentication, we flag the record for manual re-upload during the customer review phase.

Teamtailor Multi-Brand setups host separate employer brands with distinct career sites and sometimes separate candidate pools within one account. We scope the export per brand and map each brand's candidates and jobs to a distinct Recruit CRM Organization or Client account. This requires the customer to define the target Recruit CRM structure before migration begins; we provide a mapping worksheet during scoping.