Migrate from Voyse to Recruit CRM & ATS

Voyse candidate records map directly to Recruit CRM Candidate. The primary identifier is email address used as the dedupe key during import. We extract Voyse stage history properties and map the most recent stage value to Candidate status in Recruit CRM. Any Voyse custom properties on the candidate record migrate as Recruit CRM custom fields after schema discovery against the /v1/candidates endpoint reveals the available field types. If Voyse stores candidate records with an employee-type flag distinguishing active employees from job applicants, we preserve that distinction as a custom Candidate field rather than filtering them out.

Voyse organisation records map to Recruit CRM Company. The Voyse company name becomes Company name, and the registered address maps to the Company address fields. Recruit CRM Company supports industry classification, employee count, and revenue ranges; we map Voyse firmographic fields to these standard fields where present. Companies without a Voyse equivalent in the source are flagged during scoping for customer decision on whether to import or leave blank.

Voyse contact records (hiring managers, referees, internal HR contacts) map to Recruit CRM Contact. The Contact is linked to its parent Company record via the company_id lookup; we resolve this by importing Companies first and then Contacts with the CompanyId reference satisfied at migration time. Any Voyse contact custom properties migrate as Recruit CRM Contact custom fields discovered during schema scoping.

Voyse job or vacancy records map to Recruit CRM Job. The job title, description, location, and employment type map to their Recruit CRM equivalents. Voyse job status (open, filled, closed) maps to Recruit CRM Job status. If Voyse stores job requirements as structured skill tags, these migrate to Recruit CRM Job skills as a comma-delimited or multi-select field depending on the destination schema.

Voyse placement or deal records map to Recruit CRM Deal. The deal value, currency, and stage map to Deal amount, currency, and stage respectively. If Voyse tracks placement fees or commission rates as custom properties, these migrate to Recruit CRM Deal custom fields. We import the parent Company and Contact references before Deal import so that the lookup relationships are satisfied.

Voyse document attachments on candidate records (CVs, cover letters, onboarding forms) migrate to Recruit CRM Files linked to the corresponding Candidate. We extract file content and metadata from the Voyse export, then use the Recruit CRM Files API endpoint to create ContentDocument records attached to the parent CandidateId. File naming conventions and any folder structure in Voyse are preserved as file titles or description fields in Recruit CRM.

Voyse custom property groups (onboarding fields, HR-specific attributes) map to Recruit CRM nested custom fields. We query the Recruit CRM Schemas endpoint during discovery to identify the existing custom field structure and add any missing field definitions via the Custom Fields API before importing data. Voyse field types are mapped to Recruit CRM types: text to string, number to number, date to date, and multi-select to multi-select picklist.

Voyse user accounts map to Recruit CRM User records by email match. We extract all distinct Voyse users referenced as record owners or assigned recruiters and match them against the destination Recruit CRM User table. Any Voyse user without a matching Recruit CRM User is held in a reconciliation queue for the customer to provision before record import resumes. OwnerId references on Candidate, Contact, Company, Job, and Deal records are resolved against this User mapping.

Voyse stage or onboarding status values map to Recruit CRM Job pipeline stages. We configure a Job pipeline in Recruit CRM that mirrors the Voyse stage progression, mapping each Voyse stage name to a corresponding Recruit CRM stage. If Voyse uses a custom stage set per role type or department, we create multiple Recruit CRM pipelines (one per Voyse stage group) and assign them to the relevant Jobs during import.

Voyse tasks and activity records map to Recruit CRM Task. Task subject, description, due date, and status migrate directly. The assigned owner resolves against the User mapping by email. If Voyse stores call logs and meeting notes as distinct activity types, these map to Recruit CRM Call Logs and Meetings endpoints respectively with the relevant type metadata preserved.