HRMS migration
Field-level mapping, validation, and rollback between Recooty and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.
Recooty
Source
BambooHR
Destination
Compatibility
8 of 10
objects map 1:1 between Recooty and BambooHR.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Recooty to BambooHR is a category shift, not a like-for-like ATS swap. Recooty is an applicant tracking system where Jobs and Candidates are the primary objects. BambooHR is an HRIS where Employee records are the central entity and hiring is a secondary module bundled in the Advantage tier. We handle this structural difference by mapping Recooty Candidates to BambooHR Applicants (for open positions) and flagging which records should become Employee records (for hired candidates). Pipeline stages migrate as BambooHR stage definitions, interview schedules migrate as structured interview data, and GDPR consent records and audit trails carry over with explicit re-creation at the destination. Recooty custom fields (Business and Enterprise only) are documented as a written inventory for the BambooHR admin to rebuild post-migration. Workflows, job board publishing history, AI Bot Interviewer records, and branded career pages do not migrate.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Recooty object lands in BambooHR, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Recooty
Job
BambooHR
Job (BambooHR ATS module)
1:1Recooty Job records (title, description, location, department, employment type, publishing status) map to BambooHR Job records created within the BambooHR ATS module. BambooHR requires the Advantage tier to access the ATS module with job posting capability. We preserve the Recooty job_id as a reference field and migrate job status (Draft, Published, Closed) to BambooHR's job visibility settings. Publishing history to external boards does not migrate because BambooHR's board distribution is handled post-migration through BambooHR's own job board integrations.
Recooty
Candidate / Applicant
BambooHR
Applicant (BambooHR ATS)
1:1Recooty Candidate records map to BambooHR Applicant records attached to the corresponding Job. Each applicant's contact information, application date, pipeline stage, and source tracking migrate directly. We resolve the parent Job reference during import so the applicant is attached to the correct BambooHR position on insert. Candidates who were hired in Recooty are flagged for the customer to create as BambooHR Employees post-migration, since BambooHR separates Applicants (hiring) from Employees (post-onboarding).
Recooty
Pipeline (Hiring Pipeline)
BambooHR
Job Stage (BambooHR ATS)
lossyRecooty's visual pipeline stages (Applied, Screening, Interview, Offer, Hired, and any custom stages) map to BambooHR Job stage definitions. We extract every distinct stage name and order from the source pipelines and configure matching stages in BambooHR before applicant records are imported, ensuring stage transitions carry over without manual re-entry. Stages unique to specific jobs (rather than global defaults) are preserved as job-specific stage orders in BambooHR.
Recooty
Interview Schedule
BambooHR
Interview data (BambooHR ATS)
1:1Recooty interview records containing date, time, interview type, interviewer assignment, and candidate reference migrate as structured interview records linked to the BambooHR Applicant. Business and Enterprise Recooty accounts with calendar sync and self-scheduling links do not transfer because BambooHR's interview scheduling uses BambooHR's own calendar integration. We preserve the interviewer name and interview type as free-text fields in BambooHR's interview notes area.
Recooty
Custom Fields (Business/Enterprise only)
BambooHR
Custom Fields (BambooHR all paid tiers)
1:1Recooty custom fields on Candidate and Job objects (available only on Business and Enterprise plans) are documented as a written inventory with field name, data type, and picklist values. We do not migrate custom field data into BambooHR during the standard migration scope because BambooHR's custom field schema must first be configured by the admin to accept the incoming data. The inventory includes recommended field types in BambooHR (dropdown, text, date, checkbox) and is handed off for admin configuration before a supplemental data load. Starter and Growth Recooty accounts have no custom fields to migrate.
Recooty
Candidate Notes
BambooHR
Note (BambooHR Employee record)
1:1Recooty notes attached to Candidate records migrate as BambooHR Notes linked to the corresponding Applicant. Long-format evaluation notes, recruiter comments, and interview debriefs preserve their content and timestamp. Notes do not carry formatting metadata; plain text migrates as-is.
Recooty
GDPR / Privacy Data
BambooHR
Employee Files / Compliance Records (BambooHR)
lossyRecooty GDPR consent records, retention policy configurations, and audit trail logs require explicit re-creation in BambooHR. We extract the consent status, retention policy name, and last-access timestamp per candidate from Recooty's structured GDPR data, then flag these for manual re-entry or supplemental file upload in BambooHR's Employee Files module. Any candidates with lapsed consent during the migration window are flagged with a compliance alert for the customer's HR team to resolve before the new system goes live.
Recooty
Job Board Posting History
BambooHR
Not migratable
1:1Recooty's 100+ job board publishing integrations (LinkedIn, Glassdoor, Indeed, and 97 others) store posting history as OAuth token and job-board-side metadata that is not accessible via Recooty's export APIs. We preserve the job content (title, description, location) but treat board-level publishing history as non-migratable. Jobs are re-published post-migration through BambooHR's own board integrations or manually at each destination board.
Recooty
Branded Career Page
BambooHR
Not migratable
1:1Recooty Growth and Business plans include drag-and-drop branded career page builders with hosted microsites. The page builder state (layout, styling, content blocks, microsite URL) is not exportable as structured data and cannot be replicated in BambooHR, which does not include a native career page builder. We document the current career page URLs and content structure as a reference for the customer to rebuild using BambooHR's employee portal, a third-party career site tool (e.g., Breezy, Talenteria), or a hand-coded page that links to BambooHR job postings.
Recooty
AI Bot Interviewer / AI Salary Estimator Data
BambooHR
Not migratable
1:1Recooty's AI Bot Interviewer recordings, transcriptions, and scoring data live in the Recooty AI Dashboard, which uses separate credentials and a separate interface from the main Recooty ATS Dashboard. These records are not accessible via the same export path as standard candidate data. We flag the existence of AI interview data during discovery and recommend the customer downloads AI interview records directly from the Recooty AI Dashboard before account closure. Salary estimator outputs are reference-only in Recooty and do not require migration.
| Recooty | BambooHR | Compatibility | |
|---|---|---|---|
| Job | Job (BambooHR ATS module)1:1 | Fully supported | |
| Candidate / Applicant | Applicant (BambooHR ATS)1:1 | Fully supported | |
| Pipeline (Hiring Pipeline) | Job Stage (BambooHR ATS)lossy | Fully supported | |
| Interview Schedule | Interview data (BambooHR ATS)1:1 | Fully supported | |
| Custom Fields (Business/Enterprise only) | Custom Fields (BambooHR all paid tiers)1:1 | Fully supported | |
| Candidate Notes | Note (BambooHR Employee record)1:1 | Fully supported | |
| GDPR / Privacy Data | Employee Files / Compliance Records (BambooHR)lossy | Mapping required | |
| Job Board Posting History | Not migratable1:1 | Fully supported | |
| Branded Career Page | Not migratable1:1 | Fully supported | |
| AI Bot Interviewer / AI Salary Estimator Data | Not migratable1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Recooty gotchas
Tier-gated bulk import blocks high-volume migrations
GDPR audit trails require explicit cross-platform mapping
Job board posting history does not transfer between platforms
BambooHR gotchas
Undocumented API rate limits can trigger 503 errors
Per-employee pricing model requires active record count verification
API credentials must be sent on every request to avoid extra round trips
Custom field schema varies per account and requires manual inventory
Document and attachment exports are not covered by standard report exports
Pair-specific challenges
Migration approach
Discovery and tier verification
We audit the source Recooty account for plan tier (Starter/Growth/Business/Enterprise), active job count, total candidate records, pipeline stage definitions (global and per-job), custom field definitions and their associated objects, GDPR compliance data (consent records, retention policies, audit logs), and interview schedule volume. We pair this with a BambooHR tier assessment to confirm Advantage-tier access (required for ATS), map the customer's BambooHR employee subdomain, and identify any existing BambooHR employee records that would create duplicates with migrating candidate data. The discovery output is a written migration scope that explicitly notes Starter-plan accounts with no bulk import capability and Business/Enterprise accounts with custom fields requiring inventory documentation.
ATS-to-HRIS boundary definition
We define the record-type boundary before any data moves. Candidates in Recooty with pipeline stage Hired are designated for BambooHR Employee record creation (post-migration, separate from the ATS migration scope). Active candidates (Applied through Offer stages) map to BambooHR Applicants attached to BambooHR Jobs. We document this boundary in the mapping spec and confirm it with the customer's HR lead before migration begins. This step prevents the common issue of a BambooHR instance filling with applicant records that have no corresponding job openings.
Schema preparation and custom field inventory
We extract all Recooty custom field definitions (name, type, picklist values, associated object) from Business and Enterprise accounts and produce a Custom Field Inventory document. The customer's BambooHR admin uses this document to configure matching custom fields in BambooHR's field builder before the data migration pass. We configure BambooHR Job stages to match Recooty pipeline stage names and order during this phase. Starter and Growth Recooty accounts skip the custom field step entirely since those tiers do not support custom fields.
GDPR compliance extraction and handoff preparation
We extract Recooty's GDPR data including candidate consent records, retention policy assignments, and access audit logs as structured CSV exports. Candidates with lapsed consent are flagged with a compliance alert. We package the GDPR data as a compliance handoff document listing each candidate ID, consent status, applicable policy, and last audit timestamp. The customer reviews and manually re-creates these records in BambooHR Employee Files or as compliance notes. This step must complete before the BambooHR instance handles any EU-applicant data.
Test migration and reconciliation
We run a test migration into a BambooHR sandbox or a designated test environment using a representative sample of data (50-100 candidate records, 5-10 jobs, all pipeline stages represented). The customer reconciles the imported records against the Recooty source, confirms stage mappings, verifies custom field mapping (where applicable), and approves the mapping spec before production migration begins. Any field type mismatches, stage naming discrepancies, or lookup resolution failures are corrected here.
Production migration in dependency order
We run production migration in this order: BambooHR Jobs (from Recooty Job records), BambooHR Job stages (configured before applicant import), Recooty Candidates mapped to BambooHR Applicants (with parent Job resolved on insert), Candidate Notes (linked to Applicant records), Interview data (linked to Applicant records). GDPR compliance handoff document is delivered alongside the migration for manual re-entry. Each phase emits a row-count reconciliation report. Job board publishing history, branded career pages, and AI Bot Interviewer records are documented as non-migratable with recommendations for manual post-migration steps.
Cutover, validation, and admin handoff
We freeze Recooty write access during cutover, run a final delta migration of any records modified during the migration window, and hand off a Custom Field Inventory document (for BambooHR admin to configure) and a GDPR Compliance Handoff document (for HR admin to re-enter). We do not rebuild Recooty workflows, job board integrations, or branded career pages inside the migration scope. We support a three-day hypercare window for reconciliation issues raised by the recruiting team. Post-migration admin tasks (BambooHR workflow configuration, job board re-publishing, career page rebuild) are documented separately as rebuild tasks.
Platform deep dives
Recooty
Source
Strengths
Weaknesses
BambooHR
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Recooty and BambooHR.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Recooty: Not publicly documented.
Data volume sensitivity
Recooty doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Recooty to BambooHR migration scoping. Not seeing yours? Book a call.
Walk through your Recooty to BambooHR migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Recooty
Other ways to arrive at BambooHR
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.