Migrate from Loxo to BambooHR

Loxo Candidates map to BambooHR Employees with name, email, phone, address, work history, education, and skills preserved as standard or custom fields. Loxo candidate status (active, placed, rejected) migrates to a BambooHR custom field loxo_candidate_status__c. Communication history (emails, calls, notes) migrates to BambooHR Employee Notes if the volume is modest; large histories may be scoped to the most recent 12 months to avoid import performance issues. Candidates who have no existing employee relationship in BambooHR are loaded as Applicants first, then promoted to Employees during onboarding if applicable.

Loxo Contacts tagged or categorized as candidate-facing map to BambooHR Employees using the same field mapping as Candidates. The distinction between candidate and employee contact in Loxo is preserved via a loxo_contact_type__c custom field. All contact properties (phone, email, company association) transfer to the corresponding BambooHR Employee fields.

Loxo Contacts tagged as client-facing have no native home in BambooHR's HRIS model. We map these to a BambooHR Employee record only if the contact is also an employee. If the client contact is external (not employed by the company), we store them as a custom Employee field loxo_client_contact__c with the contact name and a reference to the associated Loxo Job or Deal. The customer decides during scoping whether to migrate external client contacts or exclude them and manage them in a separate CRM.

Loxo Jobs have no standard BambooHR equivalent unless BambooHR's optional ATS add-on is active. If the ATS add-on is not in scope, we store Loxo Job name, status, and requirements as a custom field on the associated Employee record (the hired candidate) and document the full job list separately for the customer's admin to recreate in their ATS of choice. If BambooHR ATS is active, Loxo Jobs map to BambooHR Job Openings with stage, description, and assigned hiring manager migrated.

Loxo Deals tracking client assignments and revenue have no direct BambooHR equivalent. BambooHR is an HRIS, not a CRM. We do not migrate Deals as structured records. If a Deal references a placed candidate, we link the associated Employee record to the Loxo Deal name via a custom field loxo_associated_deal__c for reference. The customer receives a written Deal inventory listing every Loxo Deal with its stage, value, owner, and associated contacts for manual re-creation in their CRM or pipeline management tool.

Loxo Placements recording placed candidates against a Job and Deal map to BambooHR Employee fields: hire date, start date, job title, and compensation details migrate as standard or custom Employee fields. The association to a specific Loxo Job and Deal is preserved in loxo_original_job__c and loxo_associated_deal__c custom fields for audit trail. BambooHR does not have a dedicated Placement object, so the full placement history (multiple placements per candidate) requires custom fields or a separate reference document.

Loxo Client Companies map to BambooHR's Company field on the Employee record if the parent organization is the employer. If Loxo Client Companies represent external organizations (not the employer), they are stored as a custom field loxo_client_company__c on the associated Employee. Company billing information from Loxo does not map to BambooHR and is documented separately for the customer's finance or operations team.

Loxo Pipeline stages are a recruiting/CRM concept with no BambooHR equivalent. We extract the full stage list from Loxo during discovery and document it as a reference table for the customer's admin. If BambooHR ATS is active, stages may map to Job Opening statuses. Otherwise, stage history is stored as a custom field on the Employee record if needed for placement audit.

Loxo custom fields on Candidates, Contacts, Jobs, and Deals map to BambooHR custom Employee fields. We extract the full custom field schema (name, type, options) from Loxo during discovery and map each to the equivalent BambooHR field type: text, dropdown, date, number, or checkbox. Custom fields on Jobs and Deals without a BambooHR equivalent are stored as Employee custom fields or documented separately. Field naming conventions differ between platforms; we apply a customer-confirmed naming prefix to avoid collisions with BambooHR system fields.

Loxo communication history (emails, calls, SMS) logged against Candidates and Contacts migrates to BambooHR Employee Notes. Each activity type is prefixed in the note body for identification. We scope activity history to the most recent 12-24 months to reduce import volume; older histories are exported as a separate CSV reference file. BambooHR's note model does not support threaded conversations, so the original threading context is flattened into a chronological list per employee.

Loxo tags on Candidates, Contacts, and Jobs migrate to BambooHR Tags. We export all tag associations, resolve duplicates, and apply tags to the corresponding Employee records in BambooHR. Tags that do not exist in BambooHR are created during import. Tag-based candidate segmentation from Loxo is preserved as a tag list on each Employee for filtering and reporting.

Binary attachments (resumes, cover letters, client agreements) are downloaded from Loxo via API and uploaded to BambooHR Employee Files attached to the corresponding Employee record. Resume files attach to the Employee's application or document storage section. Large file counts may extend the migration timeline; we confirm file volume during discovery.