Migrate from Crelate to BambooHR

Crelate Contacts (candidates and client contacts) map to BambooHR Employee records. 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.

Crelate Companies map to BambooHR's Company module if the customer subscribes to it (separate module in BambooHR, not available on all tiers). 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.

Crelate Jobs map to BambooHR Job Openings (Positions). 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.

Crelate Candidates (a subset of Contacts with candidate-specific fields like source, status, and resume) map to BambooHR Applicants tied to a Job Opening. 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.

Crelate Opportunities track revenue-generating business development activity in the CRM layer. 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.

Crelate Placements record placed candidates with salary, pay rate, start date, and fee percentage. 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.

Crelate's custom fields (up to 20 per entity) map to BambooHR custom fields on Employee and Job Opening records. BambooHR's custom field model differs from Crelate's; picklist values, date fields, and numeric fields map to equivalent BambooHR field types. Any Crelate custom field exceeding Crelate's 20-field cap is flagged during scoping and prioritized by the customer before migration. Fields with no BambooHR equivalent are documented for exclusion.

Crelate Activities (recruiter calls, emails, notes, and tasks linked to Contacts and Companies) have a limited mapping in BambooHR. Crelate Activities tied to recruiting outreach map to BambooHR's Employee Notes or general logging features if the customer uses them, but BambooHR does not have a native activity timeline for candidate interactions. Activities tied to an employment relationship (e.g., performance check-ins) map to BambooHR's Performance Review feature if the customer subscribes to the relevant module.

Documents attached to Crelate Contacts and Jobs (resumes, cover letters, job descriptions) migrate to BambooHR Employee Files or Job Opening attachments. We export via Crelate's API or bulk export, then upload to the corresponding BambooHR Employee record or Position. File types supported are PDF, DOC, DOCX, and image formats compatible with BambooHR's document storage.

Crelate Users (team members who own records) map to BambooHR User accounts. We match by email address and map Crelate role assignments to BambooHR role-based permissions. Crelate's admin vs standard user roles map to BambooHR's administrator vs employee permission levels. Inactive Crelate users who no longer have an active employment relationship are mapped to inactive BambooHR users.

Crelate tags applied to Contacts, Companies, and Jobs map to BambooHR custom fields where the field type is multi-select picklist, or to tagging categories if BambooHR supports them for the destination object. The customer chooses the tag strategy during scoping based on which BambooHR fields are active in their plan tier.