Crelate to BambooHR migration
We migrate Crelate's Contacts, Companies, and Jobs into BambooHR as Employees and open Positions, resolving the ATS-to-HRIS schema transformation upfront, reconciling Crelate's custom field inventory against BambooHR's limited custom field allowance, and flagging the recruiting-centric objects that have no direct BambooHR equivalent before any data moves.
FlitStack AI migrates employees, company module or custom fields, positions, applicant / employees and not migrateds from Crelate to BambooHR, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Crelate to BambooHR?
Moving from Crelate to BambooHR is an ATS-to-HRIS migration, not a record copy.
Read the full summary
Crelate's data model centers on recruiting workflows: Candidates linked to Companies and Job orders, with Opportunities tracking revenue and Placements capturing placed candidates. BambooHR's data model centers on the employment lifecycle: Employees with their HR records, Benefits, and Performance history, with a separate lightweight ATS layer for open Positions. The migration requires a structural transformation: Crelate Contacts and Candidates map to BambooHR Employees; Crelate Companies map to BambooHR Company fields (if enabled) or get dropped; Crelate Jobs map to BambooHR open Positions; Opportunities, Placements, and the CRM revenue layer do not have a BambooHR equivalent and are excluded or documented for manual re-entry. We flag the ATS module add-on cost on BambooHR during scoping since many Crelate teams using its recruiting features need the BambooHR Advantage plan to access them post-migration.
Contact → Employee
Crelate Contacts (candidates and client contacts) map to BambooHR Employee records.
How it maps
Standard name, email, phone, and address fields map directly. If the Contact type is a candidate, the BambooHR hire date, job title, and employment status fields apply. If the Contact is a recruiting client contact without an employment relationship, it may not fit BambooHR's employee-centric model and requires a manual decision during scoping.
Company → Company module or custom fields
Crelate Companies map to BambooHR's Company module if the customer subscribes to it (separate module in BambooHR, not available on all tiers).
How it maps
If BambooHR's Company module is not in scope, Crelate Company records are documented in the migration inventory and optionally re-entered manually. Company fields like address, industry, and phone map to corresponding BambooHR Company module fields if the module is active.
Job → Position (Job Opening)
Crelate Jobs map to BambooHR Job Openings (Positions).
How it maps
The Job title, description, status, and department link to BambooHR Position fields. BambooHR's ATS functionality includes Job Openings, but the number of open positions allowed depends on the plan tier—Crelate's Business Plus offers unlimited job publication while BambooHR's Advantage plan has documented limits (5, 25, or 50 openings depending on sub-tier). We verify the destination plan's opening count during scoping.
Candidate → Applicant / Employee
Crelate Candidates (a subset of Contacts with candidate-specific fields like source, status, and resume) map to BambooHR Applicants tied to a Job Opening.
How it maps
If the candidate was previously hired, their BambooHR Applicant record can be linked to an Employee record post-hire. Crelate's candidate pipeline stages map to BambooHR applicant status values (Applied, Screening, Interview, Offer, Hired, Rejected). Resume files migrate as document attachments to the Applicant record.
Opportunity → Not migrated
Crelate Opportunities track revenue-generating business development activity in the CRM layer.
How it maps
BambooHR is an HRIS and has no revenue tracking or sales pipeline functionality. Opportunities are excluded from migration scope. We document the active Opportunity count, stage distribution, and associated monetary values in a written handoff so the customer's team can re-enter them in their preferred CRM or accounting tool post-migration.
Placement → Not migrated
Crelate Placements record placed candidates with salary, pay rate, start date, and fee percentage.
How it maps
BambooHR has no fee or placement tracking equivalent. Placements are excluded from migration scope. The placement data is documented in the migration inventory as a separate CSV for the customer's admin to review.
- ContactEmployee1:1
- CompanyCompany module or custom fieldstransformed
- JobPosition1:1
- CandidateApplicant1:1
- OpportunityNot migratedpartial
- PlacementNot migratedpartial
+ 5 more in the mapping below
How Crelate and BambooHR differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Crelate | BambooHR |
|---|---|---|
| Primary data model | Recruiting CRM: Candidates, Companies, Jobs, Placements, Opportunities | HRIS: Employees, Benefits, Performance, Time Off, with ATS as an add-on layer |
| ATS functionality | Core to the product; unlimited job postings on Business Plus | Additional ATS module; Advantage tier required for more than 5 job openings |
| Custom field model | 20 custom fields per entity (Contacts, Companies, Opportunities) | Custom fields on Employees and Jobs, count varies by plan; no per-entity cap documented publicly |
| Pricing model | Per-seat at $119-$144/user/month; add-ons (Activities, custom training) cost extra | Per-employee per-month (PEPM) at $10-$25 base; ATS and performance are tiered add-ons |
| Automation | Sequences (automated cadences) and stage-triggered automations | Workflows available in Pro and Elite; different trigger and action model |
| Revenue tracking | Opportunities with stages, amounts, and probability; core to CRM layer | No revenue tracking; billing lives in BambooHR Payroll (separate product) |
| Document management | Documents attached to Contacts, Companies, Jobs, and Placements via API | Employee document storage (offer letters, I-9s, performance reviews) built in |
What to watch for in a Crelate to BambooHR migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
BambooHR ATS module costs extra beyond base HRIS
BambooHR's core product is an HRIS for employee records, onboarding, time-off, and benefits tracking.
How we handle it
Applicant tracking is a separate ATS module available on the Advantage plan. Teams using Crelate's full recruiting functionality (job postings, candidate pipelines, applicant tracking) may discover post-migration that their BambooHR plan does not include ATS or limits the number of active job openings (5 on lower tiers). We verify the destination plan's ATS inclusion during scoping and flag any ATS feature gaps against the customer's current Crelate recruiting volume before migration begins.
Crelate custom fields exceeding 20-field cap need consolidation
Crelate enforces a 20 custom field per entity limit on Contacts, Companies, and Opportunities.
How we handle it
Teams with complex recruiting schemas frequently approach or exceed this cap. Before migrating to BambooHR, we audit the customer's custom field inventory, rank fields by usage frequency, and surface any that must be dropped or consolidated. BambooHR's custom field allowance is plan-dependent and not always unlimited; we verify the destination field count ceiling during scoping to avoid a second migration correction.
Crelate API rate limit throttles bulk exports
Crelate's API enforces 120 requests per minute.
How we handle it
For databases with thousands of Contacts, Companies, and Job records, a sequential export can take significant time. We handle this by batching requests, distributing export operations across off-peak windows, and implementing exponential backoff when the rate limit is hit. The export ceiling of 15,000 records per operation also requires segmented runs for larger databases, which we automate by sequencing ID-range filters and merging result sets.
Recruiting CRM objects have no BambooHR equivalent
Crelate's Opportunities, Placements, and the CRM revenue layer have no direct mapping in BambooHR's HRIS model.
How we handle it
These objects are excluded from the migration scope. We deliver a written inventory of all active Opportunities (stage, amount, probability, owner) and Placements (candidate, job, salary, fee) so the customer's team can re-enter them in their chosen CRM or billing tool. Sequences and recruiting-specific automations also do not migrate; we document them for manual rebuild in BambooHR Workflows.
How the migration runs
Discovery and plan verification
We audit the source Crelate account: Contact and Candidate count, Company count, active Job count, Opportunity pipeline volume, Placement records, custom field inventory per entity, document attachment count, and active user count.
What this step covers
We pair this with a BambooHR plan review to verify ATS module inclusion, employee record limits, custom field allowance, and performance management tier. The discovery output is a written migration scope that explicitly lists what migrates, what is documented for manual re-entry, and any plan upgrades required in BambooHR before migration begins.
Custom field audit and consolidation
We extract Crelate's full custom field inventory per entity (Contacts, Companies, Jobs, Opportunities) and cross-reference against BambooHR's custom field structure for Employee and Job Opening.
What this step covers
Any Crelate custom field approaching the 20-field cap is flagged with usage frequency data so the customer can make an explicit keep-or-drop decision. Fields with no BambooHR equivalent are documented for exclusion. This step resolves the most common post-migration data integrity issue: fields silently dropped because they were not surfaced during scoping.
Sandbox migration and record reconciliation
We run a test migration into BambooHR using a subset of production-like data (typically the most recent 500 records per object) to validate field mapping, character encoding, date format handling, and picklist value matching.
What this step covers
The customer's HR lead spot-checks 25-50 Employee records, 10-20 Position records, and any document attachments against the Crelate source. Schema corrections, field type adjustments, and picklist value additions happen in the test environment before production migration begins.
User provisioning and owner reconciliation
We extract every distinct Crelate User and Owner referenced on Contacts, Companies, Jobs, and Placements and match by email against the BambooHR destination account's user list.
What this step covers
Any Crelate user without a matching BambooHR user is held in a reconciliation queue for the customer's admin to provision. Owner assignment on records (which Crelate stores as a User reference) maps to BambooHR's employee manager relationship or stays as a custom field if no direct BambooHR equivalent exists.
Production migration in dependency order
We run production migration in record dependency order: Employees (from Crelate Contacts and Candidates), Positions (from Crelate Jobs), Company module data (if the destination plan includes it), document attachments per Employee and Position, and custom field values mapped in the consolidation step.
What this step covers
Opportunities and Placements are exported as a separate documented CSV and excluded from live import. Each phase emits a row-count reconciliation report showing records attempted, records succeeded, and records skipped with reason codes.
Cutover, validation, and handoff documentation
We freeze writes to Crelate during the cutover window, run a final delta migration for any records modified during the migration run, then declare BambooHR the system of record.
What this step covers
We deliver the migration inventory document containing the excluded Opportunities and Placements CSV, the Sequence and Automation rebuild guide for BambooHR Workflows, and the custom field decisions log. We support a five-business-day hypercare window for reconciliation issues raised by the customer's team. We do not rebuild Crelate Sequences or automations in BambooHR as part of the migration scope.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count requiring reconciliation, and whether the BambooHR ATS module is included in scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Crelate to BambooHR →Why teams move from Crelate to BambooHR
- Crelate's per-seat pricing at $119-$144 per user per month exceeds BambooHR's per-employee model for teams where the recruiting headcount (Crelate users) differs from the HRIS headcount (BambooHR employees). Small staffing firms moving their internal operations to BambooHR's HRIS layer can reduce cost if recruiting-specific seats are no longer needed post-migration.
- Crelate's ATS and CRM features require staff to operate a recruiting-specific tool for general HR tasks like onboarding, PTO tracking, and performance management. BambooHR consolidates these into a single HRIS with employee self-service, reducing the tool sprawl that Capterra reviewers flagged when evaluating BambooHR as an all-in-one alternative.
- BambooHR's employee self-service portal and onboarding workflow tools are purpose-built for HR operations, whereas Crelate's onboarding features are secondary to recruiting. Reviews on Capterra and G2 note BambooHR's cleaner employee experience for document management, onboarding packets, and e-signatures compared to recruiting-centric alternatives.
- Crelate's API rate limit of 120 requests per minute creates throughput constraints that BambooHR's API does not impose in the same way for HRIS record operations. Teams managing high-volume HR data (frequent onboarding batches, benefits updates) find BambooHR's integration approach less constrained for HR-specific use cases.
- Customer service and billing support receive consistent negative feedback for Crelate, with reviewers on G2 and Capterra citing responsiveness issues. BambooHR's support model, while tiered (Elite gets dedicated training and data integrity hours), is reviewed more favorably for small-to-mid-market HR teams making the transition.
Questions, answered
Crelate to BambooHR migration questions
How long does a Crelate to BambooHR migration take?
Most migrations land between three and five weeks for databases under 5,000 Contacts, 500 Companies, and 200 Jobs with a clean custom field inventory. Migrations with large document attachment libraries, custom field inventories approaching Crelate's 20-field cap requiring consolidation decisions, active Companies needing BambooHR Company module setup, or Opportunities and Placements requiring manual re-entry documentation move to eight to twelve weeks. The BambooHR plan verification and ATS module confirmation adds up to one week to scoping.
Do Crelate Sequences and automations migrate to BambooHR Workflows?
No. Crelate Sequences encode automated outreach cadences with templated emails, tasks, and timing rules that are platform-native and cannot be exported as portable artifacts. BambooHR Workflows operate on a different trigger model (time-based, approval-based, and record-change-based) and cannot be directly converted from Crelate Sequences. We do not migrate automation logic. We deliver a written inventory of every active Crelate Sequence and Automation with its step definitions, timing rules, and recommended BambooHR Workflow equivalents so the customer's admin can rebuild them. This is a separate admin task or a workflow rebuild engagement.
Can we keep Crelate for recruiting and move only HR data to BambooHR?
This is a common hybrid configuration. Crelate continues as the recruiting-specific ATS for candidate sourcing, job orders, and placements; BambooHR handles HRIS functions (onboarding, benefits, performance, time-off) for the internal employee population. We do not recommend this for all teams because it creates data duplication between systems, but it is feasible for staffing firms or in-house recruiting teams that need deep ATS features unavailable in BambooHR's ATS module. If the customer pursues this path, we recommend a shared candidate identifier between systems and a documented sync protocol for hired candidates moving from Crelate to BambooHR as Employees.
What happens to Crelate's Opportunities and Placements during migration?
Opportunities and Placements are excluded from the live migration because BambooHR has no revenue tracking, placement fee, or sales pipeline functionality. We export these records as a structured CSV during the migration discovery phase, preserving Opportunity stage, amount, probability, owner, and close date, plus Placement salary, pay rate, start date, and fee percentage. The customer's team re-enters this data in their chosen CRM (Salesforce, HubSpot, Pipedrive) or billing tool. We do not charge for the export documentation of these objects, but re-entry is an admin task outside migration scope.
Will our Crelate documents and resumes migrate to BambooHR?
Yes. We export documents and resumes attached to Crelate Contacts, Companies, and Jobs via the Crelate API or bulk export tool, then upload them to the corresponding BambooHR Employee record or Job Opening. BambooHR supports PDF, DOC, DOCX, and common image formats for document storage. We validate that each document's file size is within BambooHR's attachment limits and flag any that exceed the limit for manual handling. We do not migrate Crelate's document version history.
Does BambooHR's ATS module handle the same recruiting volume as Crelate?
Not at the same level for all use cases. Crelate's Business Plus plan includes unlimited job publication and sourcing integrations. BambooHR's ATS is an add-on module with documented limits on active job openings per plan tier (5 on lower Advantage sub-tiers, 25-50 on higher). Teams with high recruiting volume (hundreds of active job orders, high candidate throughput, advanced sourcing integrations) may find BambooHR's ATS module insufficient for their recruiting workflow. We verify the destination plan's ATS limits against the customer's current Crelate recruiting volume during scoping and flag any constraints before migration.
How do we handle Crelate's 20 custom field cap during migration?
We audit the customer's full custom field inventory during discovery, including usage frequency data for each field. Any field exceeding Crelate's 20-field cap is flagged with a ranked recommendation (keep, consolidate, or drop) based on the customer's stated priorities. BambooHR's custom field allowance varies by plan and we verify it during scoping. Fields that cannot map to BambooHR's structure are documented in the migration inventory for exclusion. This is an explicit scoping decision, not a mid-migration surprise.
Related migrations
Sources: official documentation
- Import Tool Training — BambooHR Partners
- Custom Dashboards: Import CSV Data — BambooHR Product Updates
- Importing Data into BambooHR — BambooHR Support
- Field Types — BambooHR Documentation
- Import Data+ — Crelate, Inc. Help Center
- What is an ATS Data Migration? — Crelate
- Crelate Professional Services — Customer Success
Get a quote
Moving from Crelate to BambooHR?
Tell us roughly how many records and objects you have. We scope the mapping and the BambooHR setup with you, then send a quote.
Get a quote