Migrate from Vultus Recruit to BambooHR

Vultus Openings map to BambooHR Jobs. We extract title, description, status (open/closed/draft), department, location, and creation date. Vultus pipeline stage labels (Applied, Screening, Interview, Offer, etc.) are captured as a custom text field on the BambooHR Job record because BambooHR's hiring module uses a simplified funnel rather than named pipeline stages. The customer recreates their pipeline stage configuration in BambooHR Hiring Settings using our documented stage list as a reference.

Vultus Candidates with a hired status and a corresponding BambooHR employee record map to the Employee object. Candidates with no employee relationship (active sourcing, not yet hired) map to BambooHR Applicants linked to the relevant Job. We extract name, email, phone, resume text, source channel, current status, and owner assignment. Resume text migrates as a text field on the Applicant record; actual file migration is limited to text extracted from the UI.

Vultus Hotlists are grouped candidate collections with no direct BambooHR equivalent. We export the hotlist name and all candidate IDs within it, then recreate groupings in BambooHR using Tags applied to Applicant records. If the customer requires category-level groupings rather than individual tags, we recommend static BambooHR Applicant Groups as an alternative. The hotlist membership transformation is documented in the mapping sheet before migration runs.

Vultus Accounts represent client companies and store company name, address, industry, and contact count. In BambooHR's ATS module, Accounts have no native equivalent object. We map Account name and address to a custom text field on the related Applicant record, or we create a Company custom field on the Applicant object if the customer requires a structured company lookup. Standard fields like industry map to a custom picklist field created in BambooHR before migration.

Vultus Contacts within Accounts store recruiter and client contact details. If the contact is an internal employee, we map to a BambooHR Employee record with name, email, phone, job title, and department. If the contact is an external recruiter or client, we map to a BambooHR Directory Contact (if the directory feature is enabled) or to a Note attached to the related Applicant. The customer decides during scoping whether external contacts should live as employees or directory entries.

Vultus supports custom fields on Openings with non-standard structure. We discover custom field names and types during scoping, then create matching custom fields on the BambooHR Job object using BambooHR's Customize Layout feature. All custom fields must be created in BambooHR before migration runs; we provide a field creation checklist as part of the pre-migration handoff.

Vultus custom fields on Candidate records (beyond name, email, phone, status) require manual recreation in BambooHR on the Applicant object before migration. We map data type where possible (text to text, number to number, date to date) but flag any custom fields that use data types BambooHR does not support (such as multi-select without a defined picklist). These require customer admin action before field mapping can complete.

Vultus Users and Owners are assigned to Candidates and Openings. We extract user ID, name, and email and use these as a proxy Owner reference in BambooHR Applicant records. Since BambooHR associates Applicants with Jobs rather than individual Users, owner assignment migrates as a text field on the Applicant record pointing to the original Vultus owner name. Active Vultus users who will use BambooHR must have Employee records provisioned in BambooHR before migration runs.

Pipeline stage definitions in Vultus are tied to the Opening object and vary per customer configuration. We extract all active stage labels, their order, and any stage-specific automation triggers during scoping. BambooHR's hiring module uses a simple funnel with default stages (Applied, Phone Screen, Interview, Offer, Hired, Rejected). We document the customer's current stages so they can configure BambooHR Hiring Settings to match before cutover.

Vultus mass mailing history and email campaign data are not exposed as a distinct exportable object. We extract candidate contact information (name, email, phone) for re-use in BambooHR but do not migrate campaign history, open rates, or reply data. If the customer requires email campaign continuity, we recommend a separate email marketing tool or BambooHR's email integration. We preserve the fact that mass mailing was used as a source tag on the Candidate record.