Migrate from Vultus Recruit to Crelate

Vultus Openings map directly to Crelate Jobs. We extract title, description, status (open/closed/draft), department, location, and creation date from the Opening CSV export. Vultus pipeline stage names stored as custom Opening properties migrate to Crelate as custom Job fields since Crelate handles pipeline stages at the job level. Job board posting status from Vultus does not carry over; the customer re-posts openings through Crelate's native Indeed, Dice, CareerBuilder, and Monster integrations post-migration.

Vultus Candidate records map to Crelate Person records. Standard fields (name, email, phone, resume text as a text field, source channel, current status, owner assignment) migrate as structured fields. Vultus's candidate source field maps to Crelate's source tracking field. Candidate scoring or rating from Vultus migrates as a custom numeric field if the customer has that feature active.

Vultus Hotlists are grouped candidate collections that do not have a direct Crelate object equivalent. We export the hotlist name and the candidate IDs within it, then recreate the groupings in Crelate as Tag records applied to the corresponding Person records. A candidate that appears in multiple Vultus hotlists receives multiple Crelate Tags. We document the full hotlist-to-tag mapping during scoping so the customer can validate the transformation before production migration.

Vultus Accounts (representing client companies) map directly to Crelate Organization records. We extract company name, address, industry, and contact count from the Account export. Custom Account properties migrate via field mapping to equivalent Organization custom fields after the customer creates them in Crelate.

Vultus Contacts within Accounts store recruiter and client contact details. Name, email, phone, role, and the linked Account reference (mapped to the Crelate Organization) migrate as structured Person records. The role or title field maps from Vultus to Crelate's contact role field. If a Contact has no linked Account in Vultus, we create an Organization record for it during migration to satisfy the lookup relationship in Crelate.

Vultus supports custom fields on Openings that vary per customer configuration. We discover these field names during scoping, then require the customer to create matching custom fields in Crelate before we can map data into them. This is a manual pre-migration step. We provide a field-mapping spreadsheet listing each discovered Vultus custom Opening field, its data type, and the recommended Crelate Job custom field type for the customer's admin to create.

Vultus Candidate custom fields are discovered at scoping and mapped to Crelate Person custom fields after the customer manually creates them in Crelate. Candidate-specific custom fields (for example, skills certifications, clearance levels, or source details not captured in the standard source field) are the most common migration dependency. We flag any multi-select or checkbox custom fields as Crelate multi-select picklists during mapping design.

Vultus Account custom fields map to Crelate Organization custom fields. These typically include client-specific properties such as billing terms, staffing volume flags, or industry specializations. The customer must create these fields in Crelate before migration runs; we cannot insert data into non-existent custom fields.

Vultus Contact custom fields map to Crelate Person custom fields for client contacts. These cover recruiter-specific metadata such as preferred contact method, relationship notes, or billing rate types. As with all custom field objects, pre-creation in Crelate by the customer or their admin is required before data migration begins.

Vultus Users and Owners are assigned to Candidates and Openings. We extract user IDs and display names from record exports but cannot migrate user permissions, role configurations, or login credentials. The customer provisions matching Crelate User accounts before migration begins; we resolve Owner assignments by matching the Vultus owner name or email to the provisioned Crelate User record at migration time. Any Vultus Owner without a matching Crelate User goes to a reconciliation queue.

Vultus pipeline stage definitions are tied to the Opening object and vary per customer. We extract the current stage labels (for example, Screening, Interview, Offer, Placed) during scoping and document them in a stage-mapping reference sheet. The customer replicates these stages in Crelate's pipeline builder before migration. We then map the Vultus stage values from each Opening record to the matching Crelate pipeline stage during data import.

Candidate resume files attached to Vultus Candidate records are stored as file references and cannot be downloaded programmatically through any documented Vultus endpoint. We preserve resume text where the platform surfaces it in a structured Candidate field (for example, parsed resume content). We cannot guarantee binary file migration. Customers should expect to request resume re-uploads from candidates or to use a resume parsing service post-migration to rebuild file attachments in Crelate's Resume Toolbox.