Migrate from eBoss to Recruit CRM & ATS

eBoss candidate profiles map directly to Recruit CRM candidate records. Core fields include full name, email, phone, location, current employer, and LinkedIn URL. eBoss custom properties (industry-specific attributes, GDPR consent flags, source attribution) migrate as custom fields in Recruit CRM. CV files migrate as attachments linked to the candidate record. Candidate status values (Active, Passive, Placed) map to Recruit CRM candidate availability states.

eBoss Application records (the explicit join between Candidate and Job) map to Recruit CRM job application pipeline entries. The application status from eBoss (Applied, Shortlisted, Interview, Offer, Placed, Rejected) maps to the corresponding Recruit CRM pipeline stage. We preserve the original application date and any internal rating or notes from the eBoss recruiter who managed the application.

eBoss job postings map to Recruit CRM job records. Job title, description, requirements, salary range, location, and employment type transfer directly. Job status (Draft, Published, On Hold, Closed, Filled) maps to Recruit CRM status equivalents. Active jobs migrate first; closed jobs migrate as historical records if the agency elects to preserve placement history.

eBoss client records map to Recruit CRM client entries. Client company name, industry, address, and primary contact details transfer. Multi-contact client hierarchies in eBoss (primary contact plus secondary contacts) map to Recruit CRM client records with primary contact marked and additional contacts stored as related contact entries under the same client.

eBoss contact records nested under clients map to Recruit CRM client contact entries. Name, title, email, phone, and LinkedIn profile URL transfer. Primary contact flag from eBoss maps to the Recruit CRM primary contact designation. Contact roles (Hiring Manager, HR, Finance Approver) migrate as custom contact attributes if the agency uses role-based authorization.

eBoss placement records (filled jobs with candidate-to-client attribution) map to Recruit CRM placement entries. Placement date, start date, offered salary, placed candidate, and client assignment transfer. Historical placement fees and bill rate migrate as custom fields if the agency tracks commercial data on placements.

eBoss notes attached to candidate or client records migrate as activity notes in Recruit CRM linked to the corresponding candidate or client. Note creation date, author, and content transfer. Rich text formatting in eBoss notes is preserved as plain text with paragraph breaks maintained.

eBoss email engagement logs attached to candidates migrate as Recruit CRM email activity entries. Subject line, body content, timestamp, and direction (sent/received) transfer. The linked candidate or client record is resolved by email address matching against the migrated contact database.

eBoss call engagement records migrate as Recruit CRM call activity entries with call date, duration, and disposition preserved where available. Call notes migrate as activity notes attached to the same call record. The linked candidate or client record is resolved using the candidate or contact identifier from the eBoss call log.

eBoss meeting records attached to candidates or clients migrate as Recruit CRM meeting activity entries. Meeting date, time, location (or video link), attendees, and meeting notes transfer. We link the meeting to the candidate or client record that was associated in eBoss.

eBoss skills, semantic search tags, and AI-matched skill attributes migrate to Recruit CRM candidate tags. We preserve the original skill taxonomy from eBoss so that search and filtering in Recruit CRM mirrors the agency's existing candidate categorization. The customer chooses during scoping whether to use Recruit CRM tags or custom skill fields for specialized industry vocabularies.