Migrate from Beamery to Recruit CRM & ATS

Beamery Contacts map to Recruit CRM Candidates as the primary record. All standard fields (name, email, phone, current title, location) migrate directly. Custom fields are discovered via Beamery API before export and mapped to Recruit CRM Candidate custom fields, applying the same type logic (single-select to picklist, multi-select to Recruit CRM's equivalent multi-value field). Multi-value fields in Beamery use semicolon delimiters in CSV exports; we re-format these to Recruit CRM's accepted format before import. The migration user must have access to all Contact records including those with restricted field visibility.

Beamery Talent Pools have no native equivalent in Recruit CRM. We decompose each pool into a tag applied to the relevant Candidates (pool name becomes the tag label) and record the membership date as a custom date field on the Candidate record. If the customer prefers list-based grouping, we create a Candidate List in Recruit CRM for each pool and add members during migration. The decomposition strategy is selected during scoping based on how the customer plans to use talent pool data in Recruit CRM.

Beamery Vacancies map to Recruit CRM Jobs. Vacancy metadata including title, description, department, location, and status migrates directly. The stage pipeline structure migrates as a Recruit CRM Job pipeline with stages configured to match the Beamery stage names. Vacancy-to-candidate linkages (which candidates are associated with which vacancy) migrate as Applications in Recruit CRM, linking the Candidate record to the Job record.

Beamery Campaigns (outbound engagement sequences) cannot migrate as functional sequences because Recruit CRM's automation model differs. We export campaign membership, send dates, and engagement events as historical records attached to the relevant Candidate. The campaign name is preserved as a tag on each participating Candidate so the customer's team can reference past outreach history. The rebuild strategy for active sequences is documented separately.

Beamery Skills are taxonomy entries attached to Contacts via a customer-defined taxonomy. We export all assigned skills as flat text values and map them to Recruit CRM's Skills field if available, or apply them as tags on the Candidate record. The mapping strategy is confirmed during scoping based on which Recruit CRM fields are available in the customer's tier. Any skill taxonomy hierarchy in Beamery (parent-child skill groupings) is flattened to a flat tag list in Recruit CRM.

Beamery Users (recruiters and sourcers) map to Recruit CRM Users. We extract user IDs, names, roles, and email addresses and create matching users in Recruit CRM. Role names and permission levels differ between platforms and are mapped on a per-customer basis during scoping. If a Beamery Owner is referenced on a Contact or Vacancy but the User record does not exist in Recruit CRM, we hold the assignment in a reconciliation queue for the customer's admin to provision the user before record import resumes.

Beamery custom fields on Contacts and other objects are discovered via the Beamery API schema endpoint before export. We map each custom field to an equivalent Recruit CRM custom field, preserving the field type (single-select, multi-select, short text, date). Multi-select fields use semicolon delimiters in Beamery exports and are re-formatted to match Recruit CRM's multi-value input convention before import. Custom field folders in Beamery are documented but do not have a structural equivalent in Recruit CRM.

Beamery engagement events (emails sent, page views, notes) are timestamped activities linked to Contacts. We export them as a separate activity log and import them as Notes or Tasks in Recruit CRM depending on the engagement type, linked back to the corresponding Candidate record. Send dates and engagement timestamps are preserved. The event type (email, call, meeting) is recorded in a custom field on each Note or Task so the customer's team can filter by engagement type.

Beamery Tags (flat label fields applied to Contacts) migrate one-to-one as Tags applied to the corresponding Recruit CRM Candidate. Tag labels are preserved verbatim. If a tag in Beamery corresponds to a pool membership already being decomposed (see Talent Pool mapping), we avoid double-applying the same label and consolidate to a single tag per Candidate per original pool.

Binary attachments (resumes, portfolio files) stored in Beamery are exported as file references with URL and metadata. We import the file URL as a link field on the Candidate record in Recruit CRM. Actual file retrieval depends on whether the storage endpoint is accessible via API or requires the customer's credentials to Beamery's file storage. If files are not accessible via API, we document the attachment inventory for manual re-upload post-migration.

Convert Flows are forms that create Contacts in Beamery. We preserve the submitted field data and conversion timestamps as part of the Candidate record migration. The Convert Flow configuration itself (form layout, conditional logic, trigger conditions) is not portable and must be rebuilt in Recruit CRM. We document the active Convert Flow configurations during scoping as a separate rebuild guide.