Migrate from Teamtailor to Crelate

Teamtailor Candidates map directly to Crelate Contacts. Standard fields (name, email, phone, LinkedIn URL) migrate as typed Contact fields. Any custom fields discovered during schema discovery map to Crelate custom fields on the Contact object. Candidate creation date and last activity date migrate as Crelate CreatedDate and Last Activity. We resolve any duplicate candidates by email during import.

Teamtailor Jobs map to Crelate Job records with title, description, status (active/paused/closed), and public URL preserved. Job posting body content migrates as the Crelate job description. Department and location from Teamtailor map to Crelate's Department and Location fields on the Job record. Status mappings preserve Teamtailor's active/paused/closed semantics in Crelate's job status field.

Teamtailor Job Applications map to Crelate Activity records linked to the Contact (candidate) and Job. The application status (new, in-progress, rejected, hired) migrates as an Activity status or a custom field. Application source, rejection reason, and timeline timestamps preserve. The application record is the primary audit trail for candidate progression through the hiring process.

Teamtailor custom fields on candidate cards have no metadata API, so we run a discovery pass on a sample of 50-100 candidate records to enumerate field names, types, and value patterns. Each discovered custom field maps to a Crelate Contact custom field of equivalent type (text, number, select, multi-select, date). Text fields with long values migrate as long-text. Multi-select values migrate as Crelate multi-select or as comma-separated text depending on Crelate field configuration.

Teamtailor job posting custom fields are scoped to the job object and differ from candidate custom fields. We discover these during the same schema pass and map them to Crelate Job custom fields. Job-level custom fields are optional and their presence depends on the customer's job template configuration; we only map fields that are actively populated in the source data.

Teamtailor Departments are a lightweight taxonomy object that categorizes jobs and sometimes candidates. We export them as a flat list and map each to a Crelate Department record. Department assignments on Job and Candidate records migrate as lookup references to the resolved Department records.

Teamtailor Locations tag jobs and candidates with a geographic dimension. We export locations as a list and map each to a Crelate Location or Office record, preserving the location name and any associated address details. Location assignments on Job records migrate as resolved references.

Teamtailor Users (recruiters and hiring managers) export as a list with name, email, and role. We match by email against Crelate User accounts. Any User without a matching Crelate account goes to a reconciliation queue for the customer's admin to provision before record import continues, since OwnerId references must resolve on both sides.

Teamtailor Interview Kits group structured questions for candidate evaluation. The questions endpoint is queryable via API, and kit-to-job assignments are retrievable. We migrate kit names and question text as Crelate Activity Template records or as Notes attached to the Job or Contact. The structured scorecard mapping depends on Crelate's form builder support for the customer's tier.

Candidate resumes, cover letters, and files are stored as upload objects in Teamtailor with URLs returned via API. The file itself must be fetched separately from the upload URL. We download each file and attach it to the corresponding Crelate Contact record as a resume document. Files are ingested in batches to avoid overwhelming the Teamtailor file server under the rate limit.

Teamtailor automation rules and trigger-based email sequences (e.g., send email when candidate moves to stage 2) are configuration objects stored in Teamtailor and are not exposed via the public API in a structured way. We do not migrate them as code. We document every active automation visible in the Teamtailor UI during scoping, including trigger conditions, actions, and delays, and deliver a written inventory for the customer's admin to rebuild in Crelate's workflow engine.

Teamtailor Multi-Brand accounts host multiple employer brands with separate career sites and sometimes separate candidate pools. We scope the export to the primary brand or each sub-entity separately, flagging which candidates and jobs belong to which brand during extraction. Crelate's multi-organization settings handle brand separation at the account level. We coordinate with the customer to determine whether a single Crelate account with tagging or separate Crelate organizations per brand best fits their setup.