HRMS migration
Field-level mapping, validation, and rollback between Screenloop and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.
Screenloop
Source
BambooHR
Destination
Compatibility
8 of 10
objects map 1:1 between Screenloop and BambooHR.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Screenloop to BambooHR is a transition from a dedicated AI-native ATS to an HRIS where recruiting sits as one module among many. Screenloop's core objects (Candidates, Jobs, Pipeline Stages, Scorecards, Interview Records, References, Background Checks, Training Modules) have partial equivalents in BambooHR, but BambooHR flattens applicants as records attached directly to job openings rather than as a separate Candidate object with a separate Application record. We extract Screenloop data through CSV-based admin exports, map each object to BambooHR's employee and applicant schema, and load through BambooHR's documented REST API with API key authentication. Screenloop's Interview Intelligence layer (audio recordings and AI-generated transcripts) cannot be programmatically pulled due to the absence of a documented export endpoint; we export transcript text and structured scorecard fields while flagging audio files for direct export through Screenloop support. Scorecard templates, background check summaries, reference survey results, and training module completion records map to BambooHR's custom fields and notes, but BambooHR's API does not support Information fields, section headers, or multiple-selection list fields, which constrains how rich the destination schema can be.
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 Screenloop 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.
Screenloop
Candidate
BambooHR
Applicant
1:1Screenloop Candidates (name, email, phone, location, source, application date) map to BambooHR Applicant records. Screenloop's Candidate represents a person with a persistent profile across multiple job applications; BambooHR flattens each application into an Applicant record tied directly to a Job Opening. We preserve the candidate's application history by linking multiple BambooHR Applicant records to the same Employee record after hire, and we carry forward the original Screenloop application date as a custom field. Custom fields on Screenloop Candidates map to BambooHR custom fields, but BambooHR's API cannot pass Information fields, section headers, or multi-select lists, so these require pre-migration configuration or manual post-migration entry.
Screenloop
Job
BambooHR
Job Opening
1:1Screenloop Job postings map directly to BambooHR Job Openings. Title, department, location, employment type, and job description transfer as-is. Active versus closed status preserves. We flag any job-specific custom fields and note that BambooHR's job pipeline stages are configurable per job opening through the Job Pipeline step added in August 2024, allowing the customer's HR admin to arrange status ordering to match Screenloop's pipeline stage sequence.
Screenloop
Pipeline Stage
BambooHR
Job Opening Status
lossyScreenloop's configurable pipeline stages (Applied, Screening, Interview, Offer, etc.) map to BambooHR Job Opening status values. We extract the full stage ordering and stage-specific rules from Screenloop during the audit phase and provide a mapping spreadsheet for the customer to align stage labels with BambooHR's status field. BambooHR's automated email triggers (associated with candidate movement to a specific status, added in August 2024) require manual recreation after migration as they do not migrate as automation code.
Screenloop
Scorecard
BambooHR
Custom Fields + Notes
1:1Screenloop scorecards contain structured ratings, free-text feedback, and AI-generated notes from the Interview Intelligence layer. We export the structured rating criteria as numeric or text custom fields on the BambooHR Applicant record, and we attach the free-text feedback and AI-generated notes as Note records linked to the Applicant. The rating categories themselves (criteria names, weighting) must be recreated as BambooHR custom field names by the customer's admin since BambooHR does not have a native scorecard template object. We provide a scorecard mapping document during scoping.
Screenloop
Interview Record
BambooHR
Applicant Notes + Custom Fields
1:1Screenloop Interview Records include scheduled date, interviewer assignment, interview type, duration, and outcome. We map interview date to a custom date field, interviewer to a custom text or employee lookup field, and interview outcome to a custom picklist or text field. The transcript text generated by Screenloop's Interview Intelligence layer exports as a Note record attached to the Applicant. The raw audio file cannot be pulled programmatically due to the absence of a documented download endpoint; we flag this for direct export via Screenloop support if audio is required for compliance or legal retention purposes.
Screenloop
Reference
BambooHR
Custom Fields + Notes
1:1Screenloop's Modern Referencing feature collects automated referee survey responses with soft-skill feedback, referee name, and relationship to candidate. We export reference data as custom fields on the Applicant record (referee name, relationship, submission date, feedback summary) and attach detailed survey responses as Note records. BambooHR has no native referencing module, so the data lands as structured text rather than a formal reference object. We flag any third-party reference check providers (Checkr, GoodHire, etc.) whose raw PDF reports cannot be imported through the API and must be handled separately.
Screenloop
Background Check
BambooHR
Custom Fields + Notes
1:1Background check records in Screenloop include check type, provider, status, and outcome summary. We export the structured result data as custom fields on the BambooHR Employee record (post-hire) or Applicant record (pre-hire), including check type, provider name, status, and outcome summary as text. Raw supporting documents such as PDF reports from third-party providers cannot be imported through BambooHR's API and must be transferred manually or through document management tooling. We flag this gap in the audit report and advise the customer on document retention options.
Screenloop
Training Module
BambooHR
Custom Fields + Notes
1:1Screenloop's Interviewer Training library contains module completion records per user with assessment scores. We export which modules each user has completed and their assessment scores as custom fields on the BambooHR Employee record (module name, completion date, score). The actual training content (video, slides, assessments) does not transfer; BambooHR has no native LMS and training content would need to be sourced from a separate LMS platform or rebuilt. We provide a training completion mapping spreadsheet so the customer can align Screenloop module names with any future LMS they deploy.
Screenloop
User
BambooHR
Employee
1:1Screenloop User accounts (Admin, Hiring Manager, Recruiter, Interviewer) map to BambooHR Employee records. We preserve name, email, and role assignment where BambooHR supports equivalent role structures (Full Access, Manager, Employee). Screenloop's team assignments map to BambooHR department or custom fields. Owner-to-candidate associations that persist interview attribution in Screenloop transfer as custom fields on the Applicant record since BambooHR does not have a native interviewer assignment object.
Screenloop
Custom Field
BambooHR
Custom Field
lossyScreenloop custom fields on Candidates, Jobs, and Interviews export with their data types (text, number, date, single-select, multi-select). We apply a field-level mapping step to align types with BambooHR's supported custom field types: short answer (text), long answer (text area), single answer (dropdown), multiple answers (note: BambooHR's API cannot pass multi-select list fields, so these convert to text fields or require manual post-migration entry). We coordinate custom field creation through BambooHR's self-service Custom Field Builder (accessible via Settings > Custom Fields, added in 2024) or through a support ticket for fields requiring tab placement.
| Screenloop | BambooHR | Compatibility | |
|---|---|---|---|
| Candidate | Applicant1:1 | Fully supported | |
| Job | Job Opening1:1 | Fully supported | |
| Pipeline Stage | Job Opening Statuslossy | Fully supported | |
| Scorecard | Custom Fields + Notes1:1 | Fully supported | |
| Interview Record | Applicant Notes + Custom Fields1:1 | Fully supported | |
| Reference | Custom Fields + Notes1:1 | Fully supported | |
| Background Check | Custom Fields + Notes1:1 | Fully supported | |
| Training Module | Custom Fields + Notes1:1 | Fully supported | |
| User | Employee1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | 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.
Screenloop gotchas
No documented public API complicates automated migration
Interview Intelligence recordings and AI notes require special handling
Scorecard templates are Screenloop-native and need remapping at destination
No documented bulk export endpoint for historical transactions
Platform maturity and audit trail gaps for compliance migrations
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 CSV extraction coordination
We audit the Screenloop account across all active objects: Candidates, Jobs, Pipeline Stages, Scorecards, Interview Records, References, Background Checks, Training Modules, Users, and Custom Fields. Since Screenloop has no documented API, we coordinate with the customer's Screenloop account admin to generate CSV exports from each object type through the admin UI. We assess candidate volume, job count, pipeline stage complexity, scorecard template variety, and the scope of Interview Intelligence data requiring export. The discovery output is a written migration scope, a data completeness assessment, and a list of any gaps where data cannot be extracted through available UI exports.
BambooHR schema preparation and field mapping design
We design the destination schema in BambooHR based on the extracted Screenloop data. This includes creating custom fields for scorecard ratings, interview outcomes, reference data, background check summaries, and training completion records. We use BambooHR's self-service Custom Field Builder for standard field types and escalate to BambooHR support for complex placements. We flag any Screenloop fields that map to BambooHR's API-restricted types (Information fields, section headers, multi-select lists) and advise the customer on pre-creation or alternative mapping. We also configure Job Opening pipeline stages to match Screenloop's stage ordering, using BambooHR's Job Pipeline step introduced in August 2024.
Staged CSV extraction and data transformation
We extract Screenloop data in dependency order: Jobs first (since BambooHR applicants attach directly to job openings), then Candidates mapped to Applicants, then Scorecards and Interview Records as notes and custom fields, then References and Background Check summaries as structured notes, then Training Module completions as employee custom fields. Each extract undergoes a transformation step to align field names, data types, picklist values, and date formats with BambooHR's expected schema. We preserve stage history as timestamped custom fields and attach interview transcripts as Note records. We flag any orphaned records or references that cannot be resolved through available export data.
Sandbox validation and reconciliation
We load the transformed data into a BambooHR test environment to validate record counts, field mappings, and attachment integrity. The customer's HR lead spot-checks 25-50 applicant records against the Screenloop source, confirms that scorecard ratings and interview dates appear correctly, and verifies that reference and background check data landed in the expected format. Any mapping corrections (field name mismatches, picklist value gaps, custom field type issues) happen in this phase before production migration begins. BambooHR's API uses a {companyDomain}.bamboohr.com/api/ format adopted in July 2025, which we use for all production API calls.
Production migration in dependency order
We run production migration into BambooHR in record-dependency order: Job Openings first (established as the parent record for all applicants), then Employees (for users who are also employees in BambooHR's HRIS), then Applicants (mapped from Screenloop Candidates), then Notes and custom fields attached to Applicants. Interview transcripts attach as Note records; scorecard ratings and reference data attach as structured custom fields. Background check summaries and training completion records attach to Employee records for post-hire data. Each phase emits a row-count reconciliation report before the next phase begins. We handle BambooHR API rate limits with exponential backoff and chunked batch processing.
Cutover, validation, and handoff documentation
We freeze Screenloop writes during cutover and run a final delta migration of any records modified during the migration window. We enable BambooHR as the system of record for applicant tracking and HR data. We deliver a written inventory of scorecard template schemas requiring manual recreation in BambooHR, a list of Interview Intelligence audio files requiring manual export from Screenloop support, and a reference and background check document handoff checklist. We support a one-week hypercare window for reconciliation issues. We do not rebuild Screenloop automations (if any exist), interview scheduling workflows, or reference survey sequences in BambooHR as part of the migration scope.
Platform deep dives
Screenloop
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 Screenloop 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
Screenloop: Not publicly documented.
Data volume sensitivity
Screenloop 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 Screenloop to BambooHR migration scoping. Not seeing yours? Book a call.
Walk through your Screenloop 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 Screenloop
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.