Migrate from Alpha Hire to Zoho Recruit

Alpha Hire job orders sourced from VMS feeds, manual entry, and other recruiting channels map to Zoho Recruit Job Opening records. VMS-sourced job orders may omit metadata fields that exist on manually entered orders; we validate every imported job order against Zoho's required fields (Job Title, Department, Country, Job Type, Experience, and Status) and flag records with missing values for customer review before final load. Source attribution (VMS vs manual) is preserved in a custom field vms_source__c if the source field is available in the Alpha Hire export.

Alpha Hire candidate profiles including screening data, vetting records, AI-generated screening scores, and application history map directly to Zoho Recruit Candidates. Alpha Hire Last Name is required in Zoho; if a candidate record has a blank last name in the source export, we substitute 'Not Provided' per Zoho's migration documentation. Resume files migrate as attachments linked to the Candidate record. Candidate source (referral, job board, VMS) maps to the Candidate Origin or Source field in Zoho.

Alpha Hire talent partner entities map to Zoho Recruit Client records (representing the external recruiting firm or individual partner) and Contact records linked to the Client. Assignment histories between talent partners and job orders map to the Zoho Client-Candidate association model. Staffing firms using the Zoho Recruit for Staffing Agencies SKU get the Client Portal add-on ($6/license/month) for partner-facing access; we document whether the customer's talent partner workflow requires this during scoping.

Alpha Hire's rule engine for auto-assignment of job orders does not expose rule definitions in any documented export format. During scoping, we collect the customer's active rule configurations and produce a written rule inventory documenting each rule's trigger conditions, assignment criteria, and target recruiter or talent partner. The customer's admin rebuilds these as Zoho Recruit Assignment Rules in Setup > Automation & Tasks > Assignment Rules on the Professional or Enterprise tier. Rules that cannot be reproduced due to feature gaps are flagged for manual reconfiguration.

Alpha Hire structures hiring as a multi-step process with configurable stage definitions that may vary by client configuration. Zoho Recruit uses a Hiring Pipeline with configurable stages per Job Opening. We map active Alpha Hire stage definitions to Zoho pipeline stages, preserving stage names, ordering, and any probability weightings. Stage customization happens in Setup > Talent Management > Hiring Pipeline in Zoho before migration records are loaded.

Alpha Hire subscription metadata including plan tier and billing model (fixed vs percentage) is preserved as read-only notes in a custom object. We do not replicate billing relationships; these are re-established directly with Zoho Recruit post-migration. We document the customer's Alpha Hire plan tier and feature set during scoping so the customer can select the equivalent Zoho Recruit tier (Standard, Professional, or Enterprise) before the migration cutover.

Alpha Hire integrates with Microsoft Outlook, ADP, and QuickBooks. During scoping, we document each active integration and map to Zoho equivalents: Microsoft Outlook email sync maps to Zoho's POP3/IMAP email integration; ADP payroll data maps to Zoho People if the customer also uses Zoho's HR suite; QuickBooks accounting maps to Zoho Books. Integrations without a direct Zoho equivalent (or that require a different connector) are flagged for the customer's admin to reconfigure post-migration.

Candidate attachments, offer letters, and onboarding documents stored within Alpha Hire migrate as files attached to the corresponding Zoho Candidate record or stored in Zoho Recruit's Document Library. Export availability depends on the customer's data export capability from Alpha Hire. We include all accessible documents in the migration package; documents that cannot be exported from Alpha Hire are logged in the gaps report with a note for the customer to retrieve manually before cutover.

Alpha Hire recruiter and talent partner owners map to Zoho Recruit User records. We resolve owners by email match against the Zoho Recruit destination account's User table. Before migration, the customer must ensure at least two users exist in Zoho Recruit (Zoho requires a minimum of two users for data migration per its documentation). Any Alpha Hire owner without a matching Zoho User is held in a reconciliation queue for the admin to provision before record import resumes.

Scheduled interviews from Alpha Hire map to Zoho Recruit Interview records linked to the Candidate and Job Opening. Interview feedback forms from Alpha Hire map to Zoho's Interview Feedback Form where equivalent fields exist; custom feedback fields are documented for rebuild in Zoho's form builder on Professional and Enterprise tiers.

Alpha Hire AI-generated screening scores and vetting records attach to the Zoho Candidate record as custom fields (e.g., screening_score__c, vetting_status__c) created during schema setup. If Alpha Hire stores screening as a separate entity with a lookup to the candidate, we flatten it into candidate-level custom fields or create a linked custom module in Zoho.

Alpha Hire notes attached to candidates, job orders, and talent partners migrate to Zoho Recruit Notes linked to the corresponding record. Rich text formatting is preserved where the source export supports it; plain-text-only exports are loaded as-is with a note in the migration log indicating the format limitation.