Migrate from StaffingSoft to Zoho Recruit

StaffingSoft Candidate records map directly to Zoho Recruit Candidates. The candidate's primary fields (name, email, phone, address, skills, employment history) map to the corresponding Zoho Candidate fields. We preserve all standard fields and custom candidate properties during migration. Any custom candidate fields from StaffingSoft are mapped to Zoho custom fields on the Candidates module, subject to the Zoho Recruit edition field limits (50 per module on Standard, 300 per module on Enterprise). Custom fields must be pre-created in Zoho before the migration import phase.

StaffingSoft Job Orders map to Zoho Recruit Job Openings. Each job order's requirements, qualifications, opening dates, and status transfer to the corresponding Zoho Job Opening fields. Pipeline stages on the StaffingSoft job order map to the Job Opening status field or a custom picklist field. The hiring team assignments (recruiter, hiring manager) from StaffingSoft transfer to the Owner and Assigned To fields in Zoho Recruit.

The StaffingSoft Assignment is the central entity in staffing-mode deployments, linking a Candidate to a Job Order with bill rate, pay rate, start date, end date, and status. We map assignment data to Zoho Recruit in one of two ways depending on the customer's Zoho Recruit edition: (1) For customers using the staffing-agency module, we map assignment fields as structured custom fields on the Candidate record linked to the Job Opening. (2) For customers on Standard or Professional tiers without the staffing module, we create a lightweight custom Assignment module with the same field structure. Bill rate and pay rate migrate as currency fields; start and end dates migrate as date fields.

StaffingSoft Client records map to Zoho Recruit Clients. Each client record carries company name, primary contact, address, and billing preferences. In Zoho Recruit's staffing-agency mode, the Client module links to Job Openings and Candidates, replicating the client-to-order relationship from StaffingSoft. We preserve the client ID from StaffingSoft as an external reference field for audit purposes. Any multi-company or multi-state client structure from StaffingSoft maps to Zoho's Client record hierarchy.

StaffingSoft resume files stored in the document management module are exported as file binaries and re-attached to the corresponding Zoho Recruit Candidate record. We map the original StaffingSoft file name to Zoho's attachment structure. Resume parsing in Zoho Recruit (250 per day on Standard, 500 on Professional, unlimited on Enterprise) can re-process imported resumes post-migration to populate structured candidate fields automatically. If StaffingSoft stores additional document types (contracts, agreements, credentials) against candidates or job orders, these migrate as Zoho attachments on the corresponding record.

StaffingSoft pipeline stages are configurable per job order or globally. Stage names and order transfer to Zoho Recruit as either the native Job Opening status field values or as a custom picklist field on the Job Opening module, depending on whether the customer uses the staffing-agency module. Any custom stage-specific automation in StaffingSoft does not migrate — we document the stage-specific workflow triggers as part of the automation inventory delivered post-migration for the customer to rebuild in Zoho Workflow Rules.

StaffingSoft User accounts including recruiter assignments, team structures, and permission roles map to Zoho Recruit Users. We match by email address. Any StaffingSoft Owner referenced on a record that does not have a corresponding Zoho User goes to a reconciliation queue for the customer's admin to provision before the record import phase continues. Zoho Recruit edition limits on active recruiters (Standard allows unlimited users but with module feature restrictions) must be confirmed before migration to ensure the destination tier matches the user count.

StaffingSoft custom fields on candidates, job orders, and assignments require field-level mapping. We preserve field types (text, dropdown, date, currency) during migration. Any StaffingSoft lookup fields that reference other StaffingSoft records by internal ID require lookup resolution: we replace the StaffingSoft ID reference with the corresponding Zoho Recruit record ID at migration time. Lookup fields are not available in the Zoho Recruit Standard edition, so any lookups in the source must be flattened into a text or reference field for Standard-tier destinations.

StaffingSoft interview feedback, scorecards, and scheduling notes stored as activities against the candidate record migrate to Zoho Recruit Notes attached to the Candidate record, or to the Interview module if the customer's Zoho Recruit edition includes interview scheduling. Interview ratings migrate as a numeric custom field or as a picklist on the candidate. Any interview-specific notes stored as rich text in StaffingSoft are preserved as Zoho Notes with the original timestamp preserved for activity timeline ordering.

StaffingSoft onboarding task checklists and document collection status transfer as candidate properties in Zoho Recruit — either as custom fields on the Candidate record or as linked Tasks. E-signature or I-9 integration configurations from StaffingSoft do not migrate; these must be reconfigured in the destination HRIS or document management system post-migration. We document the full onboarding checklist structure in the migration deliverable so the customer's admin can re-implement it in Zoho Recruit's task and workflow system.

StaffingSoft custom report definitions and saved filters are not exportable as portable artifacts. We recommend exporting report data as CSV before migration and rebuilding reports in Zoho Recruit's standard or custom reporting tools (available from Standard tier for standard reports, Enterprise for custom reports and Zoho Analytics integration). We deliver a written report inventory listing every StaffingSoft report with its filters and columns so the customer's admin has a rebuild specification.

StaffingSoft cross-posting configuration to external job boards (stored as site associations on the job order) includes posting URLs and dates. We export the posting metadata and store it in Zoho Recruit as custom fields on the Job Opening record or as a linked notes section. The active posting credentials (LinkedIn, Indeed, Glassdoor API keys) must be re-entered in Zoho Recruit's job board integration settings post-migration. Source boosters and automated posting schedules do not migrate and require manual reconfiguration in Zoho Recruit.