Migrate from LogicMelon to BambooHR

LogicMelon Job records map to BambooHR Job Openings. The job title, description, location, employment type, and department migrate directly. The original job board targeting list (the set of boards LogicMelon posted to) is preserved as a comma-separated tag or custom field on the BambooHR Job Opening, since BambooHR does not support multi-board posting natively. Active job postings in LogicMelon are migrated as open Job Openings in BambooHR; closed or filled jobs are migrated as inactive records for historical reference.

Each LogicMelon Application record maps to a BambooHR Applicant record attached to the corresponding Job Opening. The application date, current stage in the pipeline, and any screening notes attached to the Application in LogicMelon migrate as custom fields or notes on the BambooHR Applicant. BambooHR's fixed pipeline statuses (Applied, Phone Screen, Interview, Offer, Rejected, Hired) may require re-labelling via BambooHR's status configuration if the customer's LogicMelon pipeline uses non-standard stage names.

LogicMelon Candidates with no associated Application in LogicMelon (sourced via CV search but not applied) are migrated as BambooHR Applicants. LogicMelon Candidates linked to an Application with status Hired or a completed offer are migrated as BambooHR Employees, with their hire date set from the Application's final status change timestamp. Candidates sourced via CV search without a corresponding job application are flagged in the migration report so the customer can decide whether to import them as Applicants or employees in BambooHR.

LogicMelon stores CV documents as binary file attachments (PDF or Word) linked to Candidate records. We extract the raw file from LogicMelon's file store and attach it to the corresponding BambooHR Applicant record or Employee record. The structured profile fields already captured in LogicMelon's Candidate object (name, email, phone, skills, work history) are migrated directly to the BambooHR record. The CV file serves as the backup source-of-truth where structured fields are incomplete. Any CV text extracted during pre-processing can be written to a custom long-text field on the BambooHR record.

LogicMelon stores the list of job boards targeted per job advert as a board-association object. BambooHR has no native equivalent for multi-board posting distribution. We preserve the board list as a tag or custom field on the Job Opening record (e.g., a multi-value text field listing 'Indeed, LinkedIn, Reed, Totaljobs') so teams can see the original posting distribution. This is stored as metadata only; BambooHR does not use this field to trigger any posting action.

LogicMelon's configurable pipeline stages (Applied, Screened, Interviewed, Offered, etc.) are customer-specific. BambooHR uses a fixed set of applicant statuses on its Job Opening. We map the customer's LogicMelon stage names to BambooHR status labels during scoping, flagging any LogicMelon stages that have no BambooHR equivalent. If the customer uses stages beyond BambooHR's six-status model (Applied, Phone Screen, Interview, Offer, Rejected, Hired), we note the overflow stages for manual re-labelling in BambooHR's settings post-migration.

Recruiter screening notes and scoring attached to LogicMelon Application records are migrated as Notes on the corresponding BambooHR Applicant. We preserve the original note author (where available from LogicMelon) and timestamp. BambooHR does not support a dedicated screening score field outside of custom fields, so we either map numeric scores to a custom field on the Applicant or append them as structured note text depending on the customer's preference.

LogicMelon custom fields on Jobs and Applications are identified during discovery. We map them to BambooHR custom fields on the corresponding object (Job Opening or Applicant), creating the destination field if it does not exist. BambooHR supports text, number, date, dropdown, checkbox, and employee-type custom fields. We flag any LogicMelon custom fields with data types (e.g., complex multi-select or relational fields) that cannot be represented in BambooHR's custom field schema.

File attachments beyond CVs — such as cover letters, assessment documents, or reference files attached to LogicMelon Jobs or Applications — are extracted and attached to the corresponding record in BambooHR. We preserve the original filename and attach it to the Applicant or Employee record using BambooHR's file attachment API endpoint.

LogicMelon's multi-tenant organisation hierarchy (agency-level vs. client-level structures) maps to BambooHR's Locations and Departments structure. We extract the organisation hierarchy during discovery and map it to the customer's BambooHR Locations (for office or client-level separation) and Departments (for functional team structure). The mapping is configuration-only; BambooHR does not support the same multi-tenant sub-account model as LogicMelon.