HRMS migration

Migrate from Recright to BambooHR

Field-level mapping, validation, and rollback between Recright and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.

Recright logo

Recright

Source

BambooHR

Destination

BambooHR logo

Compatibility

60%

6 of 10

objects map 1:1 between Recright and BambooHR.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Recright logo

Recright

What's pushing teams away

  • Feature gaps in core recording — at least one Capterra reviewer noted the absence of a pause button during recorded video responses as a limitation they actively missed.
  • Customer service responsiveness — a small team (14 employees per LinkedIn data) may struggle to match enterprise-level support SLAs for large organizations.
  • Transition to broader platform needs — Recright's core strength is video interviewing, so teams seeking a full ATS with advanced CRM, onboarding, or complex workflow automation may outgrow it.
  • Limited third-party integrations in migration context — no publicly documented public API means teams moving to platforms with native integrations (Workday, Greenhouse, Lever) lose a native sync path.

Choosing

BambooHR logo

BambooHR

What's pulling them in

  • Lowest friction entry point for SMBs moving off spreadsheets — intuitive interface means most teams are functional within days, not weeks.
  • Consolidation value: BambooHR merges ATS, onboarding, HR records, time-off, and payroll into a single pane of glass that employees never need to leave.
  • Volume discounts applied automatically by headcount, so pricing scales predictably as the company grows without renewal negotiations.
  • BambooHR reports most customers go live in four to six weeks, making it a realistic commitment for under-resourced HR teams.
  • Award-winning Support Heroes cited frequently in reviews — responsive human support after implementation is a differentiator.

Object mapping

How Recright objects map to BambooHR

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

maps to

BambooHR

Applicant (BambooHR ATS)

1:1
Fully supported

Recright 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

maps to

BambooHR

Job Opening (BambooHR ATS)

1:1
Fully supported

Recright 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

maps to

BambooHR

Applicant Custom Fields + Note

lossy
Fully supported

The 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

maps to

BambooHR

Custom Object (Interview Questions)

lossy
Fully supported

Recright'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

maps to

BambooHR

Custom Numeric Fields on Applicant

lossy
Fully supported

Reviewer-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

maps to

BambooHR

Custom Fields on Interview Question Bank

1:1
Fully supported

Individual 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

maps to

BambooHR

BambooHR User

1:1
Fully supported

Recright 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

maps to

BambooHR

Custom Applicant Fields

1:1
Mapping required

Customer-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

maps to

BambooHR

Application Status (custom field)

lossy
Fully supported

Recright 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

maps to

BambooHR

Source (custom field on Applicant)

1:1
Fully supported

Recright 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.

Gotchas + challenges

What specifically takes care here

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 logo

Recright gotchas

High

No public API for data export

High

Video files not exportable via API

Medium

Candidate PII embedded in interview records requires GDPR-aware handling

Medium

Interview guides map imperfectly to standard ATS assessment templates

BambooHR logo

BambooHR gotchas

High

Undocumented API rate limits can trigger 503 errors

High

Per-employee pricing model requires active record count verification

Medium

API credentials must be sent on every request to avoid extra round trips

Medium

Custom field schema varies per account and requires manual inventory

Low

Document and attachment exports are not covered by standard report exports

Pair-specific challenges

  • Recright has no public API for data export

    Recright does not publish a public REST API or documented bulk export endpoints. This means we cannot programmatically pull candidate records, interview data, or assessment scores. We work around this by coordinating a CSV export from Recright's admin UI, mapping it to our ingestion schema, and handling schema inconsistencies manually. Customers must request their full data export from Recright support before migration scoping begins. Any undocumented export formats may require additional parsing work, which we scope as a discovery-line item.

  • Video files cannot be migrated programmatically and BambooHR does not natively support them

    Recright video interview recordings are the core data asset but cannot be downloaded via any documented API. We coordinate a separate secure file transfer (SFTP share, encrypted drive, or Recright-assisted download) so video assets transfer alongside structured data. Critically, BambooHR's ATS does not natively support video attachments on Applicant records. We store a link or reference to the video file location in a custom field on the Applicant record, and the customer's admin must implement a document management strategy (BambooHR Files, external storage, or a linked HRIS integration) for accessing videos post-migration.

  • BambooHR's ATS lacks structured interview template objects

    Recright's structured interview guides (Prepare module) support ranked questions, time limits, and scoring rubrics applied uniformly across candidates. BambooHR's ATS does not expose a native interview template or structured assessment object—job application questions are basic text fields. We flatten Recright interview guides into a custom Interview Question Bank object with question text, order, and time limit fields, and store rubric descriptions as long-text notes. We document the full original structure in the migration validation report so the customer's HR team can manually rebuild the structured guide workflow using BambooHR's built-in hiring tools and task assignments.

  • Custom scoring rubrics require manual field creation and scale alignment

    Recright's per-question reviewer scores can use arbitrary numeric scales or qualitative labels tied to behavioral rubric descriptions. BambooHR supports custom numeric fields but not native rubric objects. We create custom numeric fields for each scored dimension, but the customer must confirm whether their scoring scale (e.g., 1-5, 1-10, or named levels like Needs Improvement to Exceptional) maps to integers or to picklist text. We validate scale ranges during reconciliation and flag any out-of-bounds values that require manual review.

  • BambooHR EEOC reporting uses aggregate-only candidate data

    If the customer collects voluntary disability, race, veteran status, and gender data as part of the application process, BambooHR stores this information only in aggregate for reporting purposes—for legal reasons it is not tied to individual candidate records. We flag this during scoping and ensure any candidate-level diversity data stored in Recright's custom fields is not imported into BambooHR's Applicant table (it would be unsupported there). We recommend the customer handle this data separately if legally required.

Migration approach

Six steps for a successful Recright to BambooHR data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Recright logo

Recright

Source

Strengths

  • Pre-recorded video interviewing enables asynchronous candidate screening across time zones without scheduling overhead.
  • Structured interview questions applied uniformly across candidates support consistent, defensible hiring decisions.
  • Multi-language support and global usage across 180 countries make it suitable for international talent acquisition.
  • Integration with Salesforce (CRM component in tech stack) suggests native sync capabilities for Salesforce-based recruiting stacks.
  • Candidate-facing interface doubles as an employer branding tool, projecting organizational professionalism.

Weaknesses

  • No publicly documented public API — any migration requires custom integration work or manual export/import, increasing migration complexity.
  • Small team size (14 employees per LinkedIn) may limit support bandwidth during complex migration projects.
  • Recright's data model is purpose-built for video interviewing; it does not function as a full ATS, meaning historical application data may be sparse outside of interview records.
  • Video files cannot be programmatically downloaded from Recright, requiring manual coordination for media transfer.
  • Absence of published API rate limits or bulk export endpoints means migration tooling must work around undocumented constraints.
BambooHR logo

BambooHR

Destination

Strengths

  • Single platform consolidating ATS, onboarding, HR records, payroll, and time-off reduces system sprawl for SMBs.
  • Fast implementation — BambooHR reports four to six weeks from kickoff to go-live for most customers.
  • Per-employee pricing with automatic volume discounts makes cost predictable as headcount grows.
  • Strong customer support reputation (Support Heroes) cited consistently across G2, Capterra, and direct testimonials.
  • Well-documented API with UTF-8 encoding, clear field types, and HTTPS-only access.

Weaknesses

  • Mobile application is significantly limited compared to the desktop experience, frustrating remote and field workers.
  • Companies above 150–200 employees frequently outgrow the platform's feature depth and customization surface.
  • Limited advanced reporting and analytics compared to enterprise HR platforms — custom report building is the ceiling.
  • PTO and profile customization are pain points — non-standard accrual policies and complex org structures require workarounds.
  • Document management and attachment handling lack the granularity of dedicated document-centric HR systems.

Complexity grading

How hard is this migration?

Standard HRMS migration. All 7 core objects map 1:1 between Recright and BambooHR.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Recright and BambooHR.

  • Object compatibility

    A

    All 7 core objects map 1:1 between Recright and BambooHR.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Recright: Not publicly documented.

  • Data volume sensitivity

    B

    Recright doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Recright to BambooHR migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Recright to BambooHR data migrations

Answers to the questions buyers ask most during Recright to BambooHR migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Recright to BambooHR migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 5,000 candidate records and no complex scoring rubrics. Migrations with custom assessment schemas (multi-reviewer rubrics, structured interview guides), large candidate databases (over 15,000 records), or active video file coordination move to six to ten weeks because of manual CSV parsing, custom field creation, scale alignment, and secure file transfer orchestration. Timeline depends on Recright export delivery speed and customer HR team availability for reconciliation sign-off.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Recright.
Land in BambooHR, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day