Migrate from eBoss to Crelate

eBoss Candidate records map to Crelate Contact. The candidate's name, email, phone, address, resume, and employment history migrate to the Contact's standard fields and attached documents. eBoss custom applicant fields migrate as Crelate custom fields on Contact (created via Settings > Core Records > Contacts before migration). The candidate's applicant status (active, inactive, placed) maps to a Crelate custom picklist field since Crelate Contacts do not have a native applicant status flag.

eBoss client companies and employer organizations map directly to Crelate Company. Company name, address, industry, website, and contacts migrate. If eBoss tracks client versus employer in separate objects or via a type field, we map that to a Crelate custom field on Company to preserve segmentation. Company deduplication uses the domain name or Company Name as the key.

eBoss job orders and active postings map to Crelate's Jobs object. Job title, description, requirements, location, salary range, status (open, filled, closed), and assigned recruiter migrate. Crelate Jobs track pipeline stage and source; we map eBoss job status to Crelate Job status and preserve the original posting date as a custom field.

eBoss placements and hire records map to Crelate Placements. The placement links a Contact (candidate) to a Job and to a Company (client), preserving the start date, end date (for contract placements), fee/commission amount, and placement status. Crelate Placements support billable amount and markup tracking that eBoss may not natively expose, so we create those fields during schema setup if the customer's business model requires them.

eBoss notes attached to candidates, companies, or job orders migrate to Crelate Notes linked via ContentDocumentLink to the parent Contact, Company, or Job. Note body, author, and timestamp preserve. If eBoss notes are rich-text with embedded files, the files migrate as separate ContentDocument records attached to the same parent.

eBoss call logs attached to candidate or job records map to Crelate Task with TaskSubtype=Call. Call duration, disposition, outcome, and recording reference migrate to custom Task fields. Activity timestamp preserves to maintain the engagement timeline order. Call records without a parent Contact or Job are held in a reconciliation queue for the customer to classify before insert.

eBoss email engagement records migrate to Crelate Task entries representing the email activity. The email content body migrates to a custom text area field on Task if Crelate does not expose a native rich-text body on the Activity form. We flag whether the email was sent, received, or logged manually based on eBoss engagement metadata.

eBoss interview and meeting records map to Crelate Event. Start time, end time, location, interviewer name, and meeting outcome migrate. Attendee resolution links the Event to the relevant Contact (candidate) and User (interviewer) via EventRelation records at migration time.

eBoss custom fields on candidates (industry-specific tags, clearance levels, credential expiry dates, preferred locations) map to Crelate custom fields on Contact. We create each custom field via Crelate Settings before migration, assign the appropriate type (text, number, date, picklist, checkbox), and set a Logical Name for API access. The customer's admin reviews field names and types during scoping to ensure semantic alignment.

eBoss users (recruiters, HR staff, administrators) map to Crelate Users by email match. We extract every distinct owner and assignee referenced on Candidate, Job, and Placement records and match against the destination Crelate User list. Any eBoss user without a matching Crelate User goes to a reconciliation queue for the admin to provision before record import resumes.

If eBoss carries custom objects beyond standard Candidates, Companies, and Placements (such as Certifications, Background Checks, or Credential records), we assess whether they map to Crelate custom fields on Contact/Company, a related Contact or Company sub-record, or a standalone custom object. Crelate supports custom fields on Core Records from Business tier. Complex multi-record custom objects may require a separate schema design phase.

eBoss resumes and candidate documents migrate to Crelate as ContentDocument records attached via ContentDocumentLink to the parent Contact. Document type (resume, cover letter, portfolio) preserves as a ContentVersion Description or a custom field on the ContentDocument. We preserve the original filename and file extension.