Migrate from Recruitly to BambooHR

Recruitly Candidate records map to BambooHR Employee records. The candidate's name, email, phone, address, and employment history fields map to the corresponding BambooHR employee fields (firstName, lastName, workEmail, workPhone, dateOfBirth, hireDate). Recruitly's candidate source, skills, and experience fields migrate as custom Employee fields in BambooHR since the standard BambooHR schema covers employment basics but not recruitment-specific attributes. We extract the full column list from Recruitly's candidate module during discovery to identify every custom field that requires a corresponding BambooHR custom property.

For Recruitly Candidates who are in active pipeline stages and represent future hires, we create BambooHR Applicant records in addition to Employee records. The Applicant record captures the job applied to, application date, source, and stage status from Recruitly. BambooHR's Applicant Tracking module handles inbound applicants and job applications but does not support the full pipeline stage model that Recruitly uses, so stage information is stored as a custom field on the Applicant record. Active pipeline positions that are expected to result in hires get Applicant records; historical candidates who will not be re-hired get Employee records only.

Recruitly Contacts are client-side records managed in the Sales module (company contacts, client stakeholders). These do not have a native BambooHR equivalent because BambooHR is employee-centric. We map Recruitly Contacts who are also employees in the system to Employee records with a clientContact flag custom field. Recruitly Contacts who are not employees are exported as a standalone CSV inventory delivered alongside the migration for the customer to import into a CRM or contact management tool outside BambooHR.

Recruitly Company records map to BambooHR Organization entries in the Employee directory. The organization's name, address, phone, and industry map to BambooHR's org-level fields. Recruitly's custom Company columns (from Sales Analytics, Recruiting Analytics, Billing, or General field groups) require explicit extraction during discovery and are mapped to BambooHR custom fields on the Organization record. BambooHR does not have a standalone Company module separate from the employee directory, so multi-company organizations with no shared employees need a separate tracking mechanism documented for the customer.

Recruitly Job postings map to BambooHR Job records. The job title, description, location, department, employment status, and open date migrate directly. Recruitly job board distribution settings and job status (open, closed, draft) map to BambooHR job status and posting destination fields. Recruitly Jobs linked to specific Companies map to the corresponding BambooHR Organization. Recruitly's Jobs tier limits (5 Free, 25 Solo, unlimited Professional) are validated during scoping to confirm the target plan accommodates the migration volume.

Recruitly Placements track the full hire-to-onboarding lifecycle including offer details, start date, guarantee period, commission, and billing rate. BambooHR has no native placement object, so we decompose placement data into Employee custom fields: placement_start_date, guarantee_period_months, billing_rate, commission_rate, and client_name. Placement-to-invoice linkage from Recruitly cannot be preserved in BambooHR because BambooHR does not have invoicing or accounts receivable features; we export placement-invoice linkage as a CSV inventory for the customer's finance team.

Recruitly Pipeline stage names and candidate order within stages cannot map to a native BambooHR structure. BambooHR Applicant Tracking uses a simplified stage model (Applied, Screening, Interview, Offer, Hired, Rejected) that does not support the multi-stage pipeline configurations that Recruitly uses. We map the most recent Recruitly pipeline stage to a custom Applicant field (recruitly_pipeline_stage__c) and store the pipeline name as applicant metadata. Customers requiring the full pipeline history receive a written inventory of stage transitions for manual reconciliation.

Recruitly Activity logs (calls, emails, meetings, tasks) attached to Candidates map to BambooHR Employee Notes. The activity type, date, subject, and body content migrate as Note records linked to the corresponding Employee. Activity timestamps are preserved. Recruitly's engagement metrics (email opens, click counts, call duration) migrate as custom Note metadata fields since BambooHR Notes support rich text but not native engagement tracking. Large activity volumes (over 100,000 records) are chunked and loaded via BambooHR's API with rate-limit handling.

Recruitly custom fields across Candidates, Contacts, Companies, and Jobs migrate to BambooHR custom Employee fields or Applicant fields depending on the parent object. BambooHR supports custom fields on Employee, Applicant, and Job records. We extract the full custom field schema from Recruitly during discovery, validate the field types against BambooHR's supported types (text, number, date, dropdown, checkbox, multiple-select), and flag any Recruitly field types that require conversion or approximation at the destination. Custom fields on Company records that have no Employee parent are stored as Organization-level custom properties in BambooHR.

Recruitly attachments (CVs, cover letters, certifications, contracts) attached to Candidates and Jobs migrate as File Attachments on the corresponding BambooHR Employee or Applicant record. We export attachments via Recruitly's Export Data module (requires Export Data privilege) and upload them to BambooHR via the BambooHR API or file upload interface. PDF, DOC, DOCX, and image formats are supported. BambooHR file attachments are linked to the employee record and visible in the Documents tab. Resume files are associated with the Employee's application history. Document conversion is handled for non-standard formats.

Recruitly User records and Owner assignments on Candidates, Jobs, and Placements map to BambooHR User accounts. We resolve Recruitly Owner email addresses against BambooHR User accounts during migration. Any Recruitly Owner without a matching BambooHR User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive user status is preserved. BambooHR's permission model (Employee, Administrator, Manager) maps from Recruitly's role assignments.

Recruitly Outreach Campaigns with templates, recipient lists, send history, and engagement metrics have no direct BambooHR equivalent. BambooHR Applicant Tracking does not include sales engagement or email cadence features. We export outreach campaign metadata (campaign name, template subject, send date, recipient count, open rate, click rate) as a CSV inventory delivered alongside the migration. The customer's admin uses this inventory to rebuild cadence sequences in a dedicated sales engagement tool (Salesloft, Outreach, or a similar platform) or to document campaign history for reporting purposes.