Migrate from RecruitBPM to Zoho Recruit

RecruitBPM Candidate records map directly to Zoho Recruit Candidates with the critical Last Name constraint handled upfront. Zoho Recruit requires Last Name as a mandatory field on every Candidate import; any RecruitBPM Candidate without a Last Name value receives a placeholder value of 'Not Provided' per Zoho's import documentation. We extract resume data, contact details, skills, source attribution, status, and candidate ID, then map RecruitBPM's custom status values to Zoho's candidate pipeline stages.

RecruitBPM Client records (the organizations a staffing agency places talent into) map to Zoho Recruit Clients. Client contact details, industry classification, location, and relationship notes carry over as structured fields. Client records must land in Zoho before any Candidate or Job Order that references them, because Client serves as the lookup parent for Job Openings.

RecruitBPM Job Orders map to Zoho Recruit Job Openings. Each Job Order's client association, requirements, compensation range, location, and job description migrate as typed fields. RecruitBPM's pipeline stages for the job order (screening, interviewing, offered, hired, etc.) map to Zoho's candidate pipeline status values, which we configure as a custom stage set before migration begins. We preserve the original stage names in a Zoho custom field for reporting continuity.

RecruitBPM Placements (confirmed hires with start date, compensation, placement fee, and links to Candidate and Client) migrate as a structured historical record. We create a Zoho custom module or structured custom fields on the Candidate record to capture placement fee, confirmed start date, and billing status, since Zoho Recruit does not have a native Placement object. The link to both the placed Candidate and the originating Job Opening is preserved via Zoho Lookup fields.

RecruitBPM Talent Pools (segregated candidate collections by skill, location, or certification) have no direct Zoho Recruit equivalent. We map pool membership to Zoho Tags on each Candidate record, using the pool name as the tag value. The customer's admin chooses during scoping whether to use Zoho's native tagging or a custom multi-select picklist for more structured filtering.

RecruitBPM Interview records (scheduled time, interviewer, format, outcome notes, and video interview data) map to Zoho Recruit Interview records. Interview scheduling fields migrate directly; video interview URLs migrate as text fields pointing to the original RecruitBPM-hosted recording. Interview feedback and interviewer scorecards migrate as Interview-related notes or custom fields depending on Zoho edition.

RecruitBPM custom assessment forms and evaluation results migrate as Zoho Recruit Assessments. Custom form schema (question types, answer options, scoring logic) is documented and handed off to the customer's Zoho admin to rebuild, because assessment form templates are not portable data records. Assessment scores and candidate responses migrate as structured data in Zoho's Assessment module.

RecruitBPM activity records (calls, emails, SMS, voicemails, notes tied to Candidates and Clients) map to Zoho Recruit's Tasks and Events. Call disposition, duration, and outcome migrate to custom Task fields. Email bodies and timestamps migrate as Activity records linked to the parent Candidate or Client. We apply Zoho's email sync configuration during migration setup so that historical emails attach to the correct Candidate record.

RecruitBPM's customizable pipeline stages (per job order reflecting an agency's hiring workflow) map to Zoho Recruit's candidate pipeline stage configuration. We extract the full stage name set during scoping, map each to a corresponding Zoho stage name, and configure the stage probability values in Zoho's pipeline setup. The original RecruitBPM stage names are preserved in a Zoho custom field for reporting.

RecruitBPM's tenant-specific custom fields across Candidates, Clients, and Job Orders map to Zoho Recruit custom fields, subject to Zoho's per-edition limits. Standard Edition allows 50 custom fields per module; Professional and Enterprise allow 300. We audit all RecruitBPM custom fields during scoping, flag any Zoho Standard Edition migration that would exceed the 50-field limit, and recommend Professional or Enterprise upgrade if necessary before migration begins.

RecruitBPM platform users who own records, assign tasks, and drive workflows map to Zoho Recruit Users. We match RecruitBPM users by email address to Zoho User accounts. Owner assignment on individual records (Candidates, Clients, Job Orders) migrates by resolving the email-based user reference to the corresponding Zoho User ID. Recruiter permissions and team hierarchy structures are documented and handed off for manual configuration in Zoho Recruit's user management.

Resume files, contracts, onboarding documents, and other attachments stored in RecruitBPM migrate as Zoho Recruit Attachments linked to the parent record (Candidate, Client, Job Opening). File format compatibility is verified during scoping; we flag any binary formats that Zoho Recruit does not render inline. Attachments are uploaded via Zoho Recruit's Attachment API after the parent record is committed.

RecruitBPM skill tags on Candidate records map to Zoho Recruit Skills. We extract the full skills taxonomy from RecruitBPM, create matching Skill records in Zoho Recruit, and link them to each Candidate via Zoho's Skills association. Skills used for candidate matching in RecruitBPM are documented for the customer to configure equivalent matching logic in Zoho Recruit's candidate sourcing workflow.