Migrate from Team Engine to Zoho Recruit

Team Engine Job records map directly to Zoho Recruit Job Openings. Job title, description, location, requirements, and posting status transfer as-is. Post-date and closing date migrate to the Zoho Recruit Opening Date and Target Date fields. We map Job status (active/paused/closed) to Zoho Recruit's Opening Status values. If Team Engine jobs have multiple locations or shift details encoded in the description field, we flag these for segmentation into separate Job Openings or custom fields during scoping.

Team Engine Applicant records map to Zoho Recruit Candidates. Fields transfer 1:1: First Name, Last Name, email, phone, application date, source, and status. Team Engine application status values (applied, screening, hired, rejected) map to Zoho Recruit Hiring Pipeline stage names that we configure before migration. Rejection reason migrates to a custom Candidate field. We flag any Applicant record missing a Last Name because Zoho Recruit requires Last Name as a mandatory field on Candidate.

Team Engine Applicant records with status = 'hired' map to Zoho Recruit Candidates with Employee Conversion populated (Zoho Recruit's standard employee conversion field). Applicants still in pipeline (applied, screening, interview) map to Candidates without conversion. We apply this split during the data transform phase so that the customer's hiring team can immediately see which records represent active pipeline versus converted employees.

Team Engine Employee records map to Zoho Recruit Candidates with employee-converted status. Name, contact details, hire date, and group membership transfer. Hire date migrates to the Zoho Recruit conversion date or a custom field te_hire_date__c for audit. We map Employee Group memberships to Tags in Zoho Recruit so that filtering by crew, shift, or trade works immediately post-migration without requiring custom field setup.

Team Engine Employee Groups use custom naming conventions per organization (role, shift, location, trade). We export group names and membership, then map them to Zoho Recruit Tags (preferred for flexibility) or a custom picklist field te_employee_group__c (if the customer prefers structured filtering). We flag any group name conflicts with existing Zoho Recruit picklist values during scoping. Group names with special characters are sanitized to Zoho Recruit's alphanumeric tag format.

Team Engine message threads are organized by contact phone number, not by employee record. Each thread maps to one or more Zoho Recruit Task records (subtype = Call for SMS/WhatsApp logs) attached to the corresponding Candidate record. We resolve the contact phone number to a Candidate by matching against the Candidate's phone and mobile fields. Unlinked contacts—applicants who were not hired or crew members without a full Candidate record—go to a reconciliation queue where the customer decides whether to create stub Candidate records or exclude message history.

Team Engine Referral records track which Employee referred an Applicant and the referral status. Zoho Recruit has a native Employee Referrals module in Standard tier and above. We map the referring Employee (by email match to a converted Candidate) and the referred Applicant to the Zoho Recruit Referrer and Candidate lookup fields. If Zoho Recruit's Employee Referrals module is not active on the destination account, we map referral data to a custom field te_referral_source__c on the Candidate record.

Team Engine automated survey responses (onboarding and exit) store question-answer pairs per Employee. We extract response data and map it to custom fields on the Zoho Recruit Candidate record using a te_onboarding_response__c and te_exit_response__c naming convention, with individual questions stored as multi-line text or separate subfields depending on survey structure. Survey question definitions do not migrate; we document them in the configuration inventory for the customer to recreate as Zoho Recruit assessment forms or custom fields.

Team Engine job records may include requirements fields (certifications, physical requirements, language requirements) specific to blue-collar workforces. Zoho Recruit Job Openings support custom fields at the Professional tier and above. We create te_required_certifications__c, te_physical_requirements__c, and te_language_requirements__c custom fields on Job Opening before migration and populate them from Team Engine's job record.

Team Engine Applicant records include a source field (Indeed, Indeed Apply, referral, walk-in, etc.). This maps directly to Zoho Recruit's Candidate Source picklist. We validate source values against Zoho Recruit's standard picklist during scoping and flag any custom source values for mapping to an existing picklist value or a new custom source field.

Team Engine users who post jobs, screen applicants, and manage employees map to Zoho Recruit User accounts. We resolve users by email match. Any Team Engine user without a matching Zoho Recruit User account goes to a reconciliation queue for the customer's admin to provision before migration. Zoho Recruit roles (Standard, Professional, Enterprise) are assigned based on the customer's desired recruiter license tier.

Team Engine Applicant records may include resumes or supporting documents attached. Zoho Recruit Candidates support file attachments via the Attachments section. We migrate attachments as ContentDocument records linked to the Candidate. File type and name are preserved. Attachments are migrated after Candidate records are created so that the parent lookup is satisfied.

Team Engine may store internal notes on Applicant records. These map to Zoho Recruit Notes attached to the Candidate. Note body, author, and creation date migrate. If the Team Engine note author email does not match a Zoho Recruit User, we flag the note for manual author reassignment.

If Team Engine stores interview scheduling data (interview date, interviewer, outcome), these map to Zoho Recruit Interview records linked to the Candidate. We resolve interviewer by email match to a Zoho Recruit User. Interview date and status transfer. If Team Engine interview notes are stored as separate engagement records, they migrate as Notes attached to the Interview or Candidate.