Migrate from Teamtailor to Zoho Recruit

Teamtailor Candidates map to Zoho Recruit Candidates. The mapping includes first name, last name, email, phone, LinkedIn URL, source, and all custom fields discovered during the scoping discovery pass. Email serves as the primary dedupe key. Custom fields on the candidate card (discovered by inspecting a sample of records since Teamtailor exposes no unified schema endpoint) map to Zoho Recruit custom fields on the Candidates module, using type mapping: text to single-line, multi-checkbox to multi-select picklist, date to date field, and numeric values to number or currency fields based on content.

Teamtailor Jobs map to Zoho Recruit Job Openings. Job title, status (active/paused/closed), department, location, and job body content migrate. The job status maps to Zoho Recruit's Opening Status field (Open, On Hold, Closed). Teamtailor's job-specific custom fields (discovered during scoping) map to custom fields on the Job Openings module. The public job URL is preserved in a custom text field for reference.

Teamtailor Job Applications (the join between Candidate and Job with status, source, and timestamps) map to Zoho Recruit Job Submissions. This is a critical mapping: Zoho Recruit requires the Job Submission record to be explicitly created and linked to both the Candidate and the Job Opening. Application status from Teamtailor (applied, screening, interview, offer, hired, rejected) maps to Zoho Recruit's Submission Status values. Rejection reasons and stage-at-rejection migrate to custom fields on the Job Submission.

Teamtailor Departments export as a flat list and map directly to Zoho Recruit Departments. In Zoho Recruit, Departments are used to organize Job Openings and sometimes to assign hiring managers. We import the department taxonomy before Job Openings so that the department lookup is satisfied at import time.

Teamtailor Locations export as a flat list and map to Zoho Recruit Locations. Geographic information from Teamtailor's location fields migrates as location text; Zoho Recruit's Location module supports city, state, and country fields which we populate where available from the source data.

Teamtailor custom fields on candidate cards are user-defined key-value pairs with no standardized API schema. We run a discovery pass on a sample of 50-100 candidate records to enumerate field names, types, and picklist values. Each discovered field maps to a corresponding Zoho Recruit custom field on the Candidates module, created before migration. Lookup fields from Teamtailor (if referencing other Teamtailor objects) are converted to text fields or to Zoho Recruit Lookup fields pointing at the migrated related record, depending on the target module's availability in Zoho Recruit.

Teamtailor custom fields on job postings differ from candidate custom fields and are scoped to the job object. These fields are optional and depend on the customer's job template configuration. We discover them during the same scoping pass and create equivalent custom fields on the Job Openings module in Zoho Recruit. Field types map as for candidate custom fields.

Teamtailor Users (recruiters and hiring managers) map to Zoho Recruit Staff records. We resolve by email match. Any Teamtailor user referenced on a Candidate, Job, or Job Application without a matching Zoho Recruit Staff record enters a reconciliation queue for the customer to provision before record import proceeds. Roles (Admin, Recruiter, Hiring Manager) map to Zoho Recruit profile permissions.

Teamtailor Interview Kits group structured questions for candidate evaluation and are tied to jobs via the API. Zoho Recruit does not have an equivalent Interview Kit object at the API level; interview scheduling uses scorecards and rating templates within the Interview module. We export the full list of Interview Kit names, question text, question type, and the jobs they are attached to. This inventory is delivered as a written handoff document for the customer's admin to recreate interview templates in Zoho Recruit's Interview framework.

Teamtailor resumes, cover letters, and other candidate files are stored as upload objects with a URL returned by the API; the file itself must be fetched separately. We download each file, map it to the corresponding Zoho Recruit Candidate record, and upload it as an attachment using Zoho Recruit's file attachment API. File type and original filename are preserved. Files that cannot be retrieved (expired URLs or access-restricted uploads) are flagged in the reconciliation report.

Teamtailor's Multi-Brand feature allows a single account to host multiple employer brands with separate career sites and sometimes separate candidate pools. Zoho Recruit does not have a native multi-brand equivalent. We scope the export to each brand separately during discovery and deliver brand-tagged datasets. The customer decides whether to create separate Zoho Recruit accounts per brand (preferred for full data isolation) or to use a Brand tag on Candidate and Job Opening records for filtering within a single account.

Teamtailor's /v1/answers and /v1/actions endpoints return candidate activity data including questionnaire responses and candidate interactions. These endpoints return HTTP 500 on unbounded queries for large datasets. We paginate by date range (monthly slices) and migrate key activity indicators (application received, stage changed, offer extended) as custom fields on the Job Submission or as Tasks on the Candidate. Full answer-by-answer migration is scoped based on the customer's requirements and the dataset size.