Migrate from Vultus Recruit to Recruit CRM & ATS

Vultus Recruit Openings map to Recruit CRM Jobs. We extract title, description, status (draft/open/closed), department, location, and creation date from the Opening export. Pipeline stage definitions within openings migrate as a custom text field on the Recruit CRM Job record. Recruit CRM's Job object supports multiple hiring pipelines (analogous to Vultus's pipeline configuration) configured as separate Jobs with a pipeline custom field. Job board posting integrations (Indeed, ZipRecruiter, Techfetch) are platform settings not migratable; we document the current posting configuration so the customer can re-post manually or via Recruit CRM's native job board distribution.

The primary candidate record is the most data-dense object in this migration. We extract name, email, phone, resume text, source channel, current status, owner assignment, and any custom field values surfaced in the CSV export. Vultus's candidate status values (Applied, Screening, Interview, Offer, Hired, Rejected) map directly to Recruit CRM's status options. We flag duplicate candidates detected during deduplication logic and resolve the primary record for the merged entry. Resume text transfers to Recruit CRM's candidate resume field; binary file attachments are noted as non-migratable (see Gotchas).

Vultus Recruit Accounts (client companies) map to Recruit CRM Clients. Standard fields including company name, address, industry, and contact count migrate cleanly. Custom Account properties discovered during scoping map to Recruit CRM custom fields on the Client object, requiring the customer to pre-create matching fields in Recruit CRM's field editor before migration. Account ownership resolves to the Recruit CRM User lookup via email match.

Recruiter and client contact details stored within Accounts map to Recruit CRM Contacts. Name, email, phone, role/title, and the linked Account/Client reference transfer via parent-lookup resolution. Custom Contact properties discovered during scoping follow the same pre-creation requirement as Account custom fields. Contact deduplication applies the same email-based logic used for Candidates.

Vultus Recruit Users and Owners referenced on Candidates and Openings map to Recruit CRM Users. We extract user IDs and names but resolve by email match to the Recruit CRM User table. Role assignments and permission sets are platform-configured and cannot migrate; the customer provisions User accounts in Recruit CRM before migration and we reconcile the OwnerId references against the provisioned User list.

Vultus Recruit Hotlists are grouped candidate collections without a direct Recruit CRM equivalent. We export the hotlist name and candidate IDs within each hotlist, then recreate the grouping in Recruit CRM as Tag records on the Candidate object. Tag assignment is a post-import step executed via Recruit CRM's bulk tag interface. If a customer has more than 20 hotlists, we batch-tag in groups of 50 candidates per operation to stay within Recruit CRM's bulk edit limits.

Vultus Recruit supports custom fields on Openings that vary per customer. We discover custom field names and data types during scoping and map them to Recruit CRM Job custom fields, requiring the customer to pre-create matching fields in Recruit CRM's Settings > Custom Fields before migration. The migration waits on the customer to confirm field creation before importing records containing custom field data.

Candidate custom fields in Vultus Recruit map to Recruit CRM Candidate custom fields. Field type mapping handles text, number, date, picklist, and checkbox types with appropriate Recruit CRM equivalents. Multi-select picklist values transfer as comma-separated strings and are split into Recruit CRM's multi-select format. The customer pre-creates all destination custom fields before the migration phase; we provide a field creation checklist during scoping.

Custom Account and Contact fields follow the same pre-creation requirement. We map each Vultus field name to a Recruit CRM field and flag any field type incompatibilities (e.g., Vultus freeform text that needs to become a structured picklist in Recruit CRM) for customer resolution during scoping.

Pipeline stage definitions tied to the Opening object vary per Vultus Recruit customer configuration. We extract current stage labels and order from the Opening export and document them as a stage map for the customer's Recruit CRM admin to configure as Stage options on the Job object. Stage transition rules and automation triggers cannot migrate and are included in the automation inventory document delivered post-scoping.

Resume files attached to candidate records are not accessible as downloadable binaries via Vultus Recruit's UI. We extract resume text displayed in structured candidate fields and import it as the Resume text block in Recruit CRM. Binary file migration is not possible with the current export mechanism. Customers should plan for candidate-side re-upload or a post-migration resume parsing pass using Recruit CRM's built-in AI parser on candidate records.

Mass mailing history and email campaign metadata are stored within Vultus Recruit but not exposed as a distinct exportable object. We extract candidate email addresses, names, and any segment tags (derived from hotlist membership or source channel) to populate Recruit CRM's candidate contact records. Email campaign history does not migrate; we document the existence of mass mailing campaigns for the customer's awareness.