Migrate from Betterteam to Zoho Recruit

Betterteam Jobs map to Zoho Recruit Job Openings. The job title, description, requirements, location, and department fields map directly. Betterteam's job status (active, closed, draft) maps to Zoho Recruit's Opening Status field. We extract all active and closed job postings with their full text content. Betterteam's active-job cap (the billing unit) is compared against the destination Zoho Recruit plan's job opening limit during scoping to ensure the plan supports the customer's hiring volume.

Betterteam stores candidate data as flat records per application, meaning the same person applying to two different jobs appears as two separate records. We deduplicate candidate email addresses across all applications in the source account and reconstruct a unified candidate profile in Zoho Recruit. The unified profile preserves all application dates, statuses, and source board attributions from each Betterteam application. This merge is the primary schema transformation in this migration and requires email-based deduplication logic before any records are inserted into Zoho Recruit.

Each Betterteam Application record links a deduplicated candidate to a job opening and includes submission date, source job board, status, and custom notes. Betterteam application statuses (new, reviewed, liked, declined) map to Zoho Recruit's current application status values. If a single Zoho Recruit candidate has multiple applications (from the N:1 merge above), each appears as a separate Job Application record associated with the unified Candidate profile. Application order is preserved by submission timestamp.

Betterteam allows reviewers to like/dislike and apply 5-star ratings to candidates. We preserve these ratings as numeric scores on the candidate record in Zoho Recruit, mapping the 5-star scale consistently. Zoho Recruit's rating field accepts numeric values that align with the 1-5 star scale used in Betterteam. Like/dislike binary flags are mapped to a custom boolean field or to the candidate status workflow as the customer prefers during scoping.

Reviewers can attach free-text notes to candidate profiles in Betterteam. We import all notes with author attribution and timestamps, preserving the chronological note history per candidate. In Zoho Recruit, notes attach to the unified candidate profile. If the original Betterteam note references a specific application rather than the candidate overall, we include the job title in the note body for context.

Resume and cover letter files are attached to Betterteam applications. We download all binary attachment files from Betterteam (where accessible) and re-upload them to the corresponding Zoho Recruit candidate record as Resume attachments. File naming conventions differ between platforms; we preserve the original filename in the Zoho Recruit attachment record. Attachment migration is batched to stay within API rate limits and Zoho Recruit's file size constraints.

Betterteam generates hosted careers pages as rendered HTML rather than structured data objects. Job listings and branding content exist as visible page content in Betterteam, but the page structure is not accessible via exportable API fields. We export the page URL and visible job listing content for reference. The Zoho Recruit careers page or external careers site must be rebuilt separately; we provide the exported job content and department structure to support that rebuild as a configuration deliverable.

Betterteam's job board posting integrations (Indeed, ZipRecruiter, LinkedIn, and 100+ others) are third-party connections managed server-side within the Betterteam platform. The job-to-board mapping data is not exposed via any exportable API field. We cannot migrate these distribution settings. After migration, the customer reconfigures job board integrations in Zoho Recruit or through each board's native posting interface. We provide a written inventory of the job boards active per job from Betterteam (where visible in job records) as a reference guide.

Betterteam team members who have created or owned records are extracted by email address. We resolve Betterteam owner email addresses against the Zoho Recruit destination account's User table. If a Betterteam owner does not have a corresponding Zoho Recruit User account, the record is held in a reconciliation queue for the customer's admin to provision the User before migration resumes. Active vs inactive status is preserved in a custom field on the User record.

Betterteam records which job board generated an application (Indeed, LinkedIn, direct, etc.) but does not track granular UTM or campaign-level attribution. We preserve the board-level source in Zoho Recruit's Candidate Source field. Detailed source analytics (specific campaign, posting variant) will not carry over because Betterteam does not expose that data. We warn customers during scoping that source analytics will reset at migration.

Betterteam applications may contain custom free-text fields specific to the customer's configuration. We export all custom fields as generic text fields in Zoho Recruit if matching custom fields do not already exist. The customer's admin reviews these fields post-migration and renames or restructures them in Zoho Recruit's field configuration if needed. We flag any custom fields with empty values across all records as candidates for removal.

Betterteam tracks application status transitions (new, reviewed, liked, declined) but does not expose a full status history audit log. We preserve the most recent application status as the current status in Zoho Recruit. Status transition timestamps are not available in Betterteam exports; if the customer requires a full audit log, we document this as a gap in the migration findings report.