HRMS migration
Field-level mapping, validation, and rollback between Recright and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.
Recright
Source
BambooHR
Destination
Compatibility
6 of 10
objects map 1:1 between Recright and BambooHR.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Recright to BambooHR is a platform-type migration: Recright is a purpose-built video interviewing tool, while BambooHR is an all-in-one HRIS with a built-in ATS module. There is no public API on Recright's side, so we coordinate a structured CSV export from the admin interface and map it into BambooHR's candidate, job opening, and custom field schema. Pre-recorded video interviews—the core data asset in Recright—cannot be downloaded via any documented API; we flag this upfront and coordinate a separate secure file transfer, noting that BambooHR's ATS does not natively support video attachments on candidate records. Interview guides and structured scoring rubrics flatten into custom question banks and numeric fields in BambooHR since BambooHR's ATS does not expose structured interview template objects. Workflows, hiring pipelines configured in Recright, and any automation sequences do not migrate; we deliver a written inventory for the customer's admin to rebuild in BambooHR's workflow builder. The migration scope covers candidate records, position/job opening data, interview question text, reviewer scores, and team member assignments.
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 Recright 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.
Recright
Candidate
BambooHR
Applicant (BambooHR ATS)
1:1Recright candidate records (name, email, application date, status, metadata) map directly to BambooHR Applicant records. The primary email address on the Recright candidate becomes the Applicant's email field. Custom candidate properties added in Recright map to BambooHR custom Applicant fields, which we create before migration. We note that BambooHR's ATS does not support video attachments on Applicant records—video files require separate coordination.
Recright
Position
BambooHR
Job Opening (BambooHR ATS)
1:1Recright Positions define the job opening with associated interview templates, candidate pools, and publication settings. These map to BambooHR Job Openings with Position Title, Department, Location, and Status fields. The Recright position's publication status (Draft, Active, Closed) maps to BambooHR's Job Opening status values. We preserve the original position ID in a custom field for audit traceability.
Recright
Pre-recorded Interview
BambooHR
Applicant Custom Fields + Note
lossyThe core Recright data—a Candidate's video response to a structured question—cannot be migrated as a native object in BambooHR. We export interview metadata (question text, response duration, completion timestamp, watch count) and store it as structured custom fields on the Applicant record plus a Note attachment with the full question list and response sequence. Video files themselves are flagged for manual secure transfer (SFTP or encrypted drive) with a documented file-naming convention linking each video to the corresponding Applicant record.
Recright
Interview Guide
BambooHR
Custom Object (Interview Questions)
lossyRecright's Prepare module interview guides (ranked questions, time limits, scoring rubrics) have no direct equivalent in BambooHR's ATS. We create a custom object in BambooHR called Interview Question Banks linked to the Job Opening, storing question text, intended order, and time limit as custom fields. Scoring rubric descriptions (e.g., 1-5 scale with behavioral anchors) are stored as long-text custom fields on the question bank. We document the original guide structure in the migration validation report so the customer's admin can manually recreate the guide workflow in BambooHR.
Recright
Assessment Score
BambooHR
Custom Numeric Fields on Applicant
lossyReviewer-assigned numerical or qualitative scores per question in Recright map to custom numeric fields on the BambooHR Applicant record (e.g., score_overall__c, score_communication__c, score_problem_solving__c). Multi-reviewer scores are stored as separate fields per reviewer or aggregated into an average score field depending on the customer's reporting needs. We create the fields during schema design and validate the numeric ranges match Recright's original scale.
Recright
Interview Question
BambooHR
Custom Fields on Interview Question Bank
1:1Individual questions from Recright (text prompts, time limits, recording settings) map directly to custom fields on the BambooHR Interview Question Bank custom object. Question text becomes a long-text field; time limit becomes an integer field in seconds; required/optional flag becomes a boolean. We preserve the original question sequence order via an integer sort_order__c field.
Recright
Recruitment Team Member
BambooHR
BambooHR User
1:1Recright team members (name, email, role per position) map to BambooHR Users by email lookup. Any Recright team member without a matching BambooHR User account goes into a reconciliation queue for the customer's admin to provision before final import. Role assignments from Recright (Interviewer, Hiring Manager, Recruiter) are stored in a custom text field on the User record to preserve the original permission context.
Recright
Custom Candidate Properties
BambooHR
Custom Applicant Fields
1:1Customer-added custom fields on Recright candidate records (beyond name, email, and standard metadata) are extracted and mapped to equivalent custom fields on the BambooHR Applicant object. We match data types: text fields to text, dates to dates, checkboxes to booleans, and dropdown values to picklist fields. We flag any Recright multi-select custom properties as separate single-select fields or store as delimited text depending on BambooHR's field type constraints.
Recright
Candidate Status
BambooHR
Application Status (custom field)
lossyRecright candidate status values (Applied, Screening, Interview Scheduled, Offer Extended, Hired, Rejected) map to a custom picklist field on the BambooHR Applicant record. We preserve the original status value in a text field during migration so the customer can verify the mapping and adjust status values post-migration to match BambooHR's workflow preferences.
Recright
Candidate Source
BambooHR
Source (custom field on Applicant)
1:1Recright tracks where candidates originated (direct apply, referral, job board, agency) if configured. This maps to a custom Source field on the BambooHR Applicant record. BambooHR's built-in Candidate Sources report uses this field for aggregate reporting; we note that BambooHR's EEOC reporting (Candidate by Disability and Gender) is aggregate-only per legal requirements and cannot be tied to individual Applicant records.
| Recright | BambooHR | Compatibility | |
|---|---|---|---|
| Candidate | Applicant (BambooHR ATS)1:1 | Fully supported | |
| Position | Job Opening (BambooHR ATS)1:1 | Fully supported | |
| Pre-recorded Interview | Applicant Custom Fields + Notelossy | Fully supported | |
| Interview Guide | Custom Object (Interview Questions)lossy | Fully supported | |
| Assessment Score | Custom Numeric Fields on Applicantlossy | Fully supported | |
| Interview Question | Custom Fields on Interview Question Bank1:1 | Fully supported | |
| Recruitment Team Member | BambooHR User1:1 | Fully supported | |
| Custom Candidate Properties | Custom Applicant Fields1:1 | Mapping required | |
| Candidate Status | Application Status (custom field)lossy | Fully supported | |
| Candidate Source | Source (custom field on Applicant)1: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.
Recright gotchas
No public API for data export
Video files not exportable via API
Candidate PII embedded in interview records requires GDPR-aware handling
Interview guides map imperfectly to standard ATS assessment templates
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
Export coordination and scoping discovery
We contact Recright support to request a full data export (candidates, positions, interview metadata, assessment scores, team members). We audit the export format during discovery, identify any custom candidate properties, interview guides, and scoring rubrics in use, and map them to BambooHR equivalents. We confirm whether video file transfer will be handled via SFTP, encrypted drive, or Recright-assisted download. The discovery output is a written migration scope with the candidate count, custom field inventory, and video file count for pricing confirmation.
Schema design and custom field provisioning
We design the destination schema in BambooHR's ATS and HRIS modules. This includes creating custom Applicant fields for assessment scores (per-reviewer numeric fields or aggregated score fields), custom fields for interview metadata (completion timestamp, watch count, response duration), and a custom Interview Question Bank object with question text, sort order, and time limit fields linked to Job Openings. We also create custom fields for team member roles, candidate source, and any Recright custom candidate properties. Schema is validated in a BambooHR test environment before production migration begins.
CSV parsing, transformation, and reconciliation
We parse the Recright admin export CSV into our migration ingestion format, mapping each candidate's fields to the corresponding BambooHR Applicant fields. We apply the candidate status mapping, score scale normalization, and team member email-to-User lookup during this phase. We run a reconciliation check comparing the parsed record count to the original export row count, flag any missing or malformed records, and resolve schema mismatches before production import.
Video file coordination and documentation
We coordinate the video file transfer with the customer and Recright support. We generate a file-naming convention (e.g., CandidateID_QuestionID.mp4) and a manifest CSV linking each video file to the corresponding BambooHR Applicant record. We store the manifest in BambooHR as a Note attachment on each Applicant. We document the file transfer completion in the migration validation report. The customer implements the post-migration video access strategy (BambooHR Files, external URL field, or integrated storage platform) as a separate configuration task.
Production migration in dependency order
We run production migration in record order: Job Openings (from Recright Positions) first, then Applicants (with custom fields and status mapping resolved), then Interview Question Banks (linked to Job Openings), then team member role mappings. Assessment scores are imported as custom fields on the Applicant record after the Applicant is created. Each phase emits a row-count reconciliation report before the next phase begins. We use BambooHR's API for the import with rate-limit handling and batch chunking for large datasets.
Cutover, validation, and workflow rebuild handoff
We freeze Recright write access during cutover and run a final delta import of any records modified during the migration window. We validate a random sample of 25-50 Applicant records against the original Recright data, confirm custom field values and scoring scales, and verify Job Opening links. We deliver the interview guide inventory document (with original question order, time limits, and rubric descriptions) for the customer's HR admin to rebuild in BambooHR's hiring workflow tools. We do not rebuild Recright hiring pipelines or automation sequences as BambooHR workflows; that is a separate configuration task documented in the handoff.
Platform deep dives
Recright
Source
Strengths
Weaknesses
BambooHR
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. All 7 core objects map 1:1 between Recright and BambooHR.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Recright and BambooHR.
Object compatibility
All 7 core objects map 1:1 between Recright and BambooHR.
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
Recright: Not publicly documented.
Data volume sensitivity
Recright 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 Recright to BambooHR migration scoping. Not seeing yours? Book a call.
Walk through your Recright 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 Recright
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.