Migrate from Teamdoor to Zoho Recruit

TeamDoor Job Openings map directly to Zoho Recruit Job Openings (same module name). Title, employment type, location, posting date, and owner move directly. Zoho Recruit Job Openings link to a Client; we derive Client from client mentions on the TeamDoor Job Opening. Job status maps from TeamDoor's active/closed boolean to Zoho Recruit Job Status. The original TeamDoor job_id is preserved on a Zoho Recruit custom field. Closed Job Openings import as Closed status with original close date.

TeamDoor has no Client object. Client identity lives as free-text on Job Opening title or description. During scoping we extract distinct client mentions, present a canonical list to the customer's operations lead, and create one Zoho Recruit Client per approved client. Jobs without identifiable client text link to a placeholder Client called 'Internal' for post-cutover reclassification. Client address, industry, and ownership are not in TeamDoor; the customer enriches via Zoho Recruit's manual entry, Zia AI enrichment, or an integrated data source.

TeamDoor hiring-manager email per Job Opening maps to a Zoho Recruit Contact (client-side person) linked to the parent Client via the standard lookup. We resolve duplicates on email. firstName and lastName parse from the email's local part when no name is recorded; Last Name resolves to 'not provided' per Zoho's documented guidance if the local part isn't reasonable. Multiple Job Openings link to the same Contact when the same hiring manager appears across roles.

TeamDoor Candidates map to Zoho Recruit Candidates. Email is the dedupe key. firstName, lastName, email, phone, currentTitle, and city move directly. Zoho Recruit enforces Last Name as mandatory; we resolve missing Last Name to 'not provided' per Zoho's own data migration documentation, with a flag in a custom field so the customer's recruiters can clean these up post-cutover. The original TeamDoor candidate_id is preserved on a Zoho Recruit custom field for audit.

TeamDoor Talent Pool entries map to Zoho Recruit Candidates with Candidate Status = Inactive and a custom field 'Source Type' set to 'Talent Pool'. Dedup runs on email and phone fingerprint against active Candidate records. lastContactedDate from the Talent Pool entry maps to a Zoho Recruit custom date field. The customer's recruiters can re-activate Talent Pool Candidates by changing status when they re-engage.

TeamDoor allows per-job custom stage sequences. Zoho Recruit uses Hiring Stages configured via Blueprint at the Candidate module level. We build a stage-normalization matrix during scoping that maps every distinct TeamDoor stage across every job onto a single Zoho Recruit Blueprint. The customer's admin signs off the Blueprint before bulk import. Original TeamDoor stage name is preserved on each Candidate-Job association in a custom field.

Each TeamDoor Candidate-in-Job stage transition becomes a Zoho Recruit Hiring Stage update for that Candidate against the linked Job Opening. We replay status transitions in chronological order via the API. Each transition posts with the original TeamDoor timestamp where Zoho Recruit's API permits backdating; otherwise the timestamp lives in a Note on the Candidate. Blueprint stage-transition rules (required fields, validation) fire on insert and we configure the Blueprint to permit migration-context inserts to avoid validation failures.

TeamDoor tags on candidates map to Zoho Recruit Candidate Tags. Tag names transfer verbatim with whitespace trimmed and case normalized. Skill-flavored tags also flow to the Skill Set field where Zia AI can use them for candidate matching. Zoho Recruit tags are module-wide; we flag any tag names that collide with different meaning across jobs for the customer to rename during scoping.

TeamDoor interview notes migrate to Zoho Recruit Notes attached to the Candidate. Original author email is preserved in the Note body because Zoho Recruit sets the API user as Note creator. dateAdded preserves the original TeamDoor timestamp. Long-form notes over Zoho Recruit's Note body cap split across multiple Notes with a continuation marker so nothing truncates.

TeamDoor email templates migrate to Zoho Recruit Email Templates. Merge-field syntax rewrites from TeamDoor's {{candidate.name}} to Zoho Recruit's {{candidate.firstName}} {{candidate.lastName}}. Stage-trigger automation behavior does not migrate as code; Zoho Recruit's automation lives in Workflows and Blueprint actions, which the customer's admin configures after migration. We deliver a written automation inventory for that rebuild.

TeamDoor resumes (URL references) are fetched within the first 48 hours of the migration window, validated, and re-uploaded via Zoho Recruit's attachment endpoint linked to the matching Candidate. Resume parsing runs on upload via Zoho's built-in parser and populates Experience, Education, and Skill Set fields where possible. Files exceeding per-file caps or returning 403/404 from TeamDoor land in the pre-flight report. Third-party LinkedIn or Facebook URLs are often unreachable.

TeamDoor's multi-channel array per Job Opening maps to the per-Candidate Source field in Zoho Recruit. The full channel array per Job is preserved as a custom note on the Job Opening for audit. Zoho Recruit's Source picklist is configured at the module level by the admin; we align TeamDoor channel names to the destination picklist during scoping and add any missing source values via the Setup interface before candidate insert.

TeamDoor users map to Zoho Recruit Users with a Profile (Standard, Administrator, Recruiter) and Role assigned by the customer's admin. Resolution is by email. Per Zoho's documented migration guidance, the workspace needs at least two users provisioned before migration begins (Setup > Users & Control > Users). Users with separate Zoho Recruit accounts on different orgs must close those accounts before they can join the customer's workspace, per Zoho's KB.

Any custom fields the customer added in TeamDoor map to Zoho Recruit custom fields per module, subject to per-tier field-type limits (Standard has fewer field types; Professional and Enterprise add Lookup and Formula). The Zoho Data Migration UI prompts to create new fields for unmapped source columns, which we use to materialize the destination schema. Text Area Large fields cannot be used as criteria for filters, per Zoho documentation.