Migrate from Beamery to BambooHR

Beamery Contacts (candidates) map to BambooHR Employee records. Standard fields (firstName, lastName, email, phone, location) migrate directly. Custom fields on the Contact object migrate as BambooHR Employee custom fields, which must be pre-created in BambooHR before import. Multi-value custom fields in Beamery use semicolon delimiters and are re-delimited for BambooHR's field type. We flag which Contacts are active candidates versus historical rejected candidates so the customer can decide whether to import all or only the active pipeline.

Beamery Talent Pools are named candidate collections with membership dates. BambooHR has no Talent Pool object. We map pool membership to BambooHR Tags on the Employee record (one tag per pool membership), with the join date preserved in a custom field pool_join_date__c. If the customer maintains more than ten pools, we recommend grouping into a hierarchical tag naming convention or using a custom dropdown field to avoid tag proliferation in BambooHR's flat tag model.

Beamery Vacancies map to BambooHR Jobs. Vacancy title becomes the Job title. Vacancy status (open, paused, closed) maps to BambooHR Job status. The vacancy stage pipeline in Beamery does not migrate to BambooHR because BambooHR Jobs have a single-stage application form with no configurable pipeline. We document the original stage sequence as a written appendix so the customer's recruiting team can reference the original hiring workflow.

Beamery Skills are taxonomy entries attached to Contacts. BambooHR has no skills taxonomy or skills library. We map skills to a BambooHR custom text field (Employee_skills__c) as a comma-separated list. Multi-select skills that the customer wants as structured data require a custom multi-select picklist field in BambooHR, which must be pre-created and whitelisted by BambooHR support. We recommend scoping this with the customer during discovery because picklist value limits (500 options per field) may require splitting into multiple fields.

Beamery Campaigns (outbound candidate engagement sequences) have no equivalent in BambooHR. Campaign membership, send dates, and engagement events do not migrate because BambooHR's ATS module does not store candidate outreach history. We export campaign membership data as a written CSV inventory with candidate email, campaign name, and last engagement date for the customer's recruiting team to reference when rebuilding sequences in a dedicated sales engagement tool.

Beamery Convert Flows are intake forms that create Contacts from candidate submissions. BambooHR has application forms but no equivalent intake form that creates candidate records for sourcing. The form field schema migrates as a written data dictionary; the form configuration and logic do not migrate.

Beamery engagement events (emails, calls, meetings, page views, notes) linked to Contacts have no home in BambooHR's Employee data model. BambooHR's ATS add-on supports notes on applicants but does not maintain a timeline of candidate outreach events. We export the engagement log as a separate CSV file linked by Contact email for the customer's records, but the data is not loaded into BambooHR as structured activity records.

Beamery Users (recruiters and sourcers) map to BambooHR Employee records with a role flag indicating they were a Beamery user. We map Beamery user roles (Admin, Recruiter, Sourcing Manager) to BambooHR Employee custom fields because BambooHR's permission model is not structured the same way. Beamery role permissions and ownership assignments are documented separately for the customer's IT team to configure in BambooHR's access control settings.

Beamery Tags on Contacts migrate directly to BambooHR Tags on the corresponding Employee record. One-to-one tag label mapping is preserved. Multi-value tags are handled as multiple separate tag inserts in BambooHR. Tags that represent pipeline stages in Beamery are flagged as non-semantic in BambooHR because BambooHR Tags are flat labels without taxonomy grouping.

Contact-level custom fields in Beamery migrate to Employee-level custom fields in BambooHR. We discover the custom field schema via Beamery's API before export, validate field types, and pre-create matching fields in BambooHR before import. Dropdown custom fields require BambooHR's option list to be pre-populated with the source values. Text fields migrate directly. Multi-select Beamery custom fields use the five-semicolon delimiter and are re-joined as comma-separated values for BambooHR's text fields or split into individual tag inserts for BambooHR's tag field.

Binary attachments linked to Contacts (resumes, portfolio files) are stored as file references in Beamery. We export the file URL and file metadata. Actual file retrieval depends on whether the Beamery storage bucket is accessible via API or requires a separate download step. Files are uploaded to the corresponding BambooHR Employee's document storage via BambooHR's file attachment API, with the original filename and upload date preserved. Resume files are tagged as Resume in BambooHR's file category.

Beamery Recipes are event-driven automation rules that reference Beamery object IDs and trigger logic. BambooHR has no automation recipe or workflow builder equivalent in its ATS module. We document all active Recipes during scoping — including trigger conditions, conditional assignments, and downstream actions — in a written Recipe Inventory for the customer's admin to evaluate for manual rebuild in BambooHR or an alternative ATS. This documentation is delivered as part of the migration handoff package.