Migrate from Sesame HR to Bullhorn ATS & CRM

Sesame HR Employee records split into Bullhorn Candidate (the recruiting/ATS record) and optionally Bullhorn Contact (the client relationship record) depending on whether the customer uses Bullhorn CRM alongside ATS. We map first name, last name, email, phone, department, job title, hire date, and employment status directly. Employment type (full-time, part-time, contractor) becomes a custom Candidate field or maps to the Bullhorn custom object if the customer licenses one for employment classification. We flag any Employee without a valid email address for manual handling before import because Bullhorn requires an email for Candidate deduplication.

Sesame HR Contract records (employment type, salary band, start/end dates, probation period) do not have a native Bullhorn equivalent. We map them to Bullhorn custom fields on Candidate (employmentType__c, salaryBand__c, contractStartDate__c, contractEndDate__c, probationEndDate__c) or to a Bullhorn custom object (EmploymentContract__c) if the customer requires a separate record type. Bullhorn's Front Office Growth/Enterprise edition supports up to 10 custom objects with 55 fields each; we verify capacity against the customer's existing custom object count during scoping.

Sesame HR Candidates attached to Vacancies map directly to Bullhorn Candidate records with the JobOrder serving as the Bullhorn equivalent of the vacancy. We preserve the Sesame HR application stage (new, screening, interview, offer, hired, rejected) as a custom Candidate field or map it to Bullhorn's candidateStatus if the customer's pipeline uses standard Bullhorn stages. Custom pipeline stages from Sesame HR migrate to Bullhorn custom Candidate fields or to the Bullhorn Opportunity pipeline if the customer uses Bullhorn CRM for temp-to-perm tracking. We flag any vacancy records above the Starter tier's 5-position cap for extraction completeness.

Sesame HR Vacancy records map to Bullhorn JobOrder with job title, department, location, employment type, salary range, and opening count preserved. The Sesame HR vacancy status (open, paused, closed) maps to the Bullhorn JobOrder status field. Bullhorn JobOrder supports multiple placements per order; we preserve the total headcount from Sesame HR as the jobOrderHeadcount field. Custom vacancy fields migrate to JobOrder custom fields or to the Bullhorn Opportunity object if the customer uses Bullhorn CRM for job-order tracking.

Sesame HR time entries (clock-in/clock-out, overtime flags, break deductions) have no native Bullhorn ATS/CRM equivalent. Bullhorn Time & Expense is a separate product (formerly PeopleNet Time) that handles WFM-style time tracking for staffing firms with placed contractors. We assess whether the customer uses Bullhorn Time & Expense during scoping. If yes, we map Sesame HR time entries to the Bullhorn Time & Expense API. If no, we store time-entry summaries as custom fields on the Employee's corresponding Bullhorn Candidate record (hoursWorkedThisPeriod__c, overtimeHours__c) or deliver a structured export for downstream payroll ingestion.

Sesame HR leave balances and request history do not have a native Bullhorn ATS equivalent. We migrate current PTO balance snapshots as custom fields on the Candidate record (ptoBalance__c, sickBalance__c, lastLeaveRequestDate__c, leaveType__c) and store leave request history as a structured export. For customers using Bullhorn Onboarding (workforce management module), we map leave accrual to the Onboarding module's accrual tracking. Bullhorn does not natively process leave workflows; the customer's HR team configures leave approvals outside Bullhorn or via Bullhorn Automation (Herefish) if licensed.

Sesame HR shift assignments (start/end times, assigned employee, role) have no native Bullhorn ATS/CRM equivalent. Bullhorn Onboarding (formerly Able) handles workforce scheduling for staffing firms with placed contractors. We assess Bullhorn Onboarding licensing during scoping. If licensed, we map shifts to the Onboarding module's schedule records. If not licensed, we store shift summary data as custom fields on the Candidate record (shiftStart__c, shiftEnd__c, shiftRole__c) and deliver a written handoff of the full shift schedule for the customer's workforce management team to rebuild in Bullhorn Onboarding or a third-party scheduling tool.

Sesame HR organizational units and company-level records map to Bullhorn ClientCorporation. We extract the org chart as a flat list of manager-subordinate relationships and map the reporting structure to Bullhorn ClientCorporation name and address fields. Bullhorn does not have a native hierarchical org chart; we flag circular references (employee reported to their own subordinate) during extraction and resolve them to the next highest valid manager before import. For staffing firms, ClientCorporation represents the hiring client company rather than the staffing firm's internal structure.

Sesame HR employee documents (contracts, ID copies, certificates) migrate as Bullhorn ContentDocument records attached via ContentDocumentLink to the corresponding Candidate record. We preserve the original filename and MIME type, and map the Sesame HR document category (contract, identification, certification) to a custom ContentDocument field or to the document's title prefix. Binary files are base64-encoded for API upload. Bullhorn's file size limits and document type restrictions are verified during scoping.

Sesame HR custom fields on Employees and other objects are available via API. We read the full custom field schema during discovery and apply value mapping for picklist and multi-select fields. Bullhorn Front Office Growth/Enterprise editions support up to 10 custom objects with 55 fields each; Bullhorn ATS supports 2 custom objects; ATS Growth supports none. We map Sesame HR custom properties to Bullhorn custom fields on the equivalent standard object first, and escalate to Bullhorn custom objects only if field capacity is exhausted. Any Sesame HR custom object that exceeds Bullhorn's custom object field limits is delivered as a structured export with a rebuild recommendation.

Sesame HR payroll preparation data (hours worked, overtime, deductions, accruals) has no native Bullhorn equivalent. Bullhorn does not process payroll. We package the Sesame HR payroll preparation dataset as a structured CSV export with schema documentation for the customer's external payroll system. If the customer licenses Bullhorn Payroll (a separate product), we assess whether a Bullhorn Payroll API integration is in scope; otherwise, the payroll export is delivered as a reference artifact alongside the migration package.

Sesame HR employee tags map to Bullhorn's native tagging feature on Candidate and Contact records where available, or to a custom multi-select picklist field (employeeTags__c) if the customer's Bullhorn edition supports it. We extract all distinct tag values during discovery and apply them to the mapped Candidate records. Tags used for classification (department tags, employment type tags) are separated from functional tags that represent workflow states.