Migrate from Vultus Recruit to Zoho Recruit

Vultus Recruit Candidate records map directly to Zoho Recruit Candidate. Standard fields (First Name, Last Name, Email, Phone, Source, Status, Current Title, Current Company) migrate as typed fields. The mandatory Last Name constraint in Zoho Recruit requires that any Vultus Candidate with a blank last name receive a placeholder value ('Not Provided') during transform, or the record will be rejected during import per Zoho's mandatory field enforcement documented in their Data Migration guide.

Vultus Recruit Opening records map to Zoho Recruit Job. Fields including Title, Description, Status (Open/Closed), Department, Location, and Creation Date migrate as standard Job fields. Pipeline stage data within Openings (custom stage labels per customer) migrate as a custom Job field rather than a native pipeline stage, since Zoho Recruit's pipeline model differs structurally.

Vultus Recruit Account records (client companies) map to Zoho Recruit Client Account. Standard fields including Company Name, Address, Industry, Website, and Contact Count migrate cleanly. Custom Account properties discovered during scoping map to Zoho custom fields, requiring those fields to be pre-created before migration. The account record must be imported before any Contact records referencing it, since Zoho enforces the lookup relationship at insert time.

Vultus Recruit Contact records (recruiter and client contacts within Accounts) map to Zoho Recruit Contact. Fields include Name, Email, Phone, Job Title, and linked Client Account reference. The Account lookup is resolved at migration time by matching Vultus Account names to Zoho Client Account names. Any orphaned Contact without a matching Account is held in a reconciliation queue.

Vultus Recruit Hotlists are grouped candidate collections that have no direct Zoho Recruit equivalent. We export the Hotlist name and the candidate IDs contained in each Hotlist, then recreate the grouping in Zoho Recruit as colored Tags on the matching Candidate records. The customer chooses tag colors and naming conventions during scoping. Hotlist membership exceeding 100 candidates per list is chunked into multiple Tag assignments.

Vultus Recruit pipeline stage definitions are tied to the Opening object and vary per customer configuration. These are not exposed as a distinct exportable object. We extract the current stage labels and status values during scoping and apply them as a custom picklist field on the Zoho Recruit Job record. The customer recreates the stage progression in Zoho Recruit's pipeline builder post-migration.

Vultus supports custom fields on Openings that map to Zoho Recruit Job custom fields. We discover custom field names and data types during scoping. The destination custom fields must be created in Zoho Recruit before migration begins (Setup > Customization > Modules > Job > Layout Editor). Field types must match: text maps to Single Line, picklist maps to Picklist, checkbox maps to Checkbox. Custom fields are not available in Zoho Recruit's Free Edition; the customer must be on Standard or above.

Vultus Candidate custom fields map to Zoho Recruit Candidate custom fields. We map field types during discovery: multi-select from Vultus maps to Zoho Multi-Select Picklist; URL fields map to Link; numeric fields map to Number. Lookup fields in Vultus that reference related records require Zoho Lookup fields, which are only available in Professional and Enterprise editions of Zoho Recruit per the platform's custom field limits documentation.

Vultus Account custom fields map to Zoho Recruit Client Account custom fields. The same pre-creation requirement applies: destination custom fields must exist in Zoho before we can map data into them. We extract field names, data types, and sample values during scoping and provide a Zoho field creation checklist to the customer or their Zoho admin before migration.

Vultus Contact custom fields map to Zoho Recruit Contact custom fields. This follows the same pattern as Candidate and Account custom fields: discover at scoping, create in Zoho before migration, then map data during import. All custom field creation requires Zoho Recruit Standard edition or above; Free edition does not support custom fields per Zoho's field-level customization documentation.

Vultus Recruit Users (Owners) assigned to Candidates and Openings map to Zoho Recruit User records. We resolve by email match during migration. Any Vultus User without a matching Zoho User account is held in a reconciliation queue for the customer's admin to provision. Per Zoho's migration requirements, at least two Users must exist in the destination Zoho Recruit account before migration begins, and any pre-existing Zoho Recruit User accounts must be closed or merged before importing users via CSV.

Vultus Recruit mass mailing history and email campaign data are not exposed as a distinct exportable object. We extract candidate email addresses, phone numbers, and opt-in status as part of the Candidate record export and migrate these as structured Contact fields on the Zoho Recruit Candidate. Email campaign history, open rates, and response cadence do not migrate; the candidate contact information required to resume campaigns does.