Migrate from Avature to Zoho Recruit

Avature Person records (candidates and employees) map to Zoho Recruit Candidate records. All standard fields (name, email, phone, work history) transfer directly. Zoho Recruit enforces Last Name as a mandatory field; we populate records missing this field with a 'Not Provided' placeholder per Zoho's documented import requirement. Custom fields on Person records map to Zoho custom candidate fields (50 available on Standard, 300 on Enterprise). Resume attachments migrate as parsed resume content or as file attachments in the Document Library.

Avature Company entities map to Zoho Recruit Client records. The Company-Person linkage in Avature (person records linked to companies) preserves as the Client-to-Candidate relationship in Zoho. Company custom fields map to Client custom fields. Address, industry, and revenue fields transfer as text or picklist values depending on Zoho's field configuration in the target account.

Avature Job records map to Zoho Recruit Job Opening records. Job status (Open, On Hold, Closed), department, location, and description transfer directly. Job-to-Person candidate associations migrate as Candidate-Job Opening linkage records. We map Avature workflow stage values to Zoho Hiring Pipeline stages using a stage-equivalence table built during scoping.

Avature record tables attached to Person records (e.g., multiple employment history entries, education entries, certifications) represent one-to-many relationships that Zoho Recruit's flat candidate profile does not support natively. We flatten these into separate child records in a Zoho Custom Module linked via lookup to the Candidate, or append them as structured Notes with labeled sections. The customer selects the strategy during scoping.

Avature candidate tags map as flat label Tags in Zoho Recruit. Tag counts (Standard 250, Professional 500, Enterprise 1000 per plan) constrain the total tag vocabulary; we flag any migration that exceeds the target plan's tag limit. Talent pool membership may require conversion to static Candidate Lists in Zoho Recruit.

Interview feedback, ratings, and notes submitted through Avature's hiring manager portal are stored as activity records attached to the Person record. We extract these as Zoho Recruit Notes linked to the Candidate record with a timestamp and author attribution preserved. Ratings migrate as numeric or picklist fields in a custom Candidate section.

Avature pipeline stages are customizable statuses per Job Template with conditional automation triggers. Zoho Recruit uses a visual Hiring Pipeline with predefined stage names (Screening, Interview, Offer, Hired, Rejected) that can be customized. We map Avature stage names to Zoho stage names using a stage-equivalence table, and we document any stages with no Zoho equivalent for the customer to configure post-migration.

Avature Workflow definitions are entity-specific sequences for requisitions, onboarding, internal mobility, and events. These do not migrate as automation logic because Zoho Recruit uses a different Workflow Rules model (trigger-action rules per module). We deliver a written inventory of every active Avature Workflow with its trigger conditions, steps, and recommended Zoho Workflow Rule equivalent for the customer's admin to rebuild.

Avature Job Templates define reusable requisition blueprints including fields, workflow steps, and approval chains. Template logic does not map directly to Zoho Recruit's Job Opening structure. We document the template fields and approval chain requirements in a written handoff so the customer's admin can configure equivalent Job Opening configurations in Zoho Recruit.

Avature Datasets store bulk reference data used by workflows and forms (e.g., department lists, location codes, skills taxonomies). Dataset structures vary by implementation. We extract dataset records and map them to Zoho Recruit Custom Modules (for transactional reference data) or as picklist value sets for standardized fields. We flag any dataset with over 500 records for the customer to validate the target field type.

Avature user accounts representing recruiters, hiring managers, and admins map to Zoho Recruit Users. Role assignments and permissions do not transfer directly because Zoho's role-based access control model differs. We extract the user list and map it to a Zoho Recruit user provisioning list; the customer's admin creates Zoho User accounts before migration. Note: users with existing separate Zoho Recruit accounts cannot be imported and must close those accounts first per Zoho documentation.

Avature onboarding module tracks new hire setup tasks and document collection. Onboarding data models differ significantly between ATS platforms. We map task status and document references as Zoho Tasks and Notes attached to the Candidate record after hiring, with a custom onboarding status field. Full onboarding workflow logic does not migrate; we document the onboarding sequence for rebuild in Zoho Recruit Tasks and Workflow Rules.