Migrate from Eploy to BambooHR

Eploy Jobs (title, department, location, salary band, workflow assignment) map directly to BambooHR Jobs. Custom job fields migrate as BambooHR custom fields on the Job object. Eploy's job-to-workflow linkage does not have a native BambooHR equivalent; we document the stage sequence as a written workflow map and recommend configuring BambooHR's ATS pipeline stages to match the original sequence.

Eploy Candidate records (contact details, application history, skills, notes, status) map to BambooHR Employee records. We preserve the candidate's application context by linking the BambooHR Employee to the migrated BambooHR Job via the Employee History field. Duplicate detection uses email as the dedupe key. Custom candidate properties migrate as BambooHR custom fields on the Employee file; any properties without a matching field type are flagged for scoping review.

Eploy workflow stages are customisable per organisation with no canonical list in the API. We discover stage names by querying active jobs during scoping, aggregate the distinct values, and map each to a custom picklist field on the BambooHR Job object (e.g., eploy_stage__c). The stage-to-stage transition timestamps migrate as structured note entries on the BambooHR Employee or Job record for audit. Customer confirms the mapping table before production migration.

Eploy hiring manager assignments tie specific users to jobs and workflow stages. These do not map to a native BambooHR object. We export the assignments as a written role matrix (which Eploy user has access to which job and stage) and recommend that BambooHR permissions are configured manually as Employee visibility and Job posting permissions in BambooHR's ATS settings after migration.

Eploy Offers (salary, start date, role details, e-signature status) map to BambooHR Job Offers. E-signature audit trails migrate as a file attachment on the BambooHR Job Offer record. Active offers migrate at migration time; withdrawn or expired offers are excluded from the primary migration but can be included as historical records if the customer requires a full audit trail.

Eploy's onboarding module (reference collection, contracts, compliance documents) lives in a separate schema not fully accessible via the standard API. We migrate what is available through the onboarding API endpoints as structured fields on the BambooHR Employee record, and flag any objects that return partial schemas. For records that cannot be extracted automatically, we document the gap and recommend a manual CSV export of the onboarding module as a complement to the automated migration.

Eploy referral records (employee who referred, candidate referred, reward status) map to a BambooHR custom field pair: referral_source__c (naming the referring employee) and referral_reward_status__c. We preserve the referral attribution at migration time and link the referred candidate to the referring employee's BambooHR Employee record where applicable.

Eploy Talent Pools are saved candidate collections for future roles. BambooHR has no native Talent Pool object. We migrate pool memberships as BambooHR employee file tags (one tag per pool name) and add a structured note field talent_pool_memberships__c listing all pools the employee belongs to. The customer selects this strategy during scoping.

Eploy organisations add custom fields to jobs. We detect custom job property schemas during discovery, create corresponding custom fields in BambooHR's ATS Job object via the API during the schema design phase, then populate them during the job migration pass.

Eploy candidate custom properties map to BambooHR employee custom fields. We detect the full custom property schema during scoping, pre-create the destination fields in BambooHR, and migrate values during the candidate-to-employee migration. Fields that do not have a compatible BambooHR field type (e.g., complex multi-value structures) are flagged for review and may be stored as long-text notes.

Eploy resume and document attachments are served as download URLs, not inline blobs. We enumerate all attachment URLs, download each file to temporary storage, then upload each to the BambooHR Employee file attachment endpoint. Large attachment volumes (hundreds per candidate in compliance-heavy sectors) extend migration time significantly and require sufficient storage headroom. We run the download pass before the record migration pass so that attachments can be linked at insert time.

Eploy email and SMS threads tied to candidates migrate as structured notes on the BambooHR Employee record. Thread content and timestamps are preserved; thread formatting may flatten in transit. We cannot migrate real-time email send/receive functionality as that requires API integration beyond data migration scope.