Migrate from RESUMate to BambooHR

RESUMate Candidates map to BambooHR Applicant records. During migration we preserve the full candidate name, email, phone, address, parsed resume text (mapped to the Work Experience and Education sections of the BambooHR Applicant), and any unstructured notes. When a Candidate from RESUMate is hired, the BambooHR Applicant converts to an Employee through BambooHR's native onboarding flow, which we coordinate with the customer's HR admin. We preserve the original RESUMate candidate ID in a custom field resumate_candidate_id__c on the Applicant for audit trail.

RESUMate Client records (employer or company entities) map to BambooHR Companies in the HRIS directory. RESUMate's Client Name becomes the BambooHR Company name; Client address and contact details map to the Company address fields. The Client-ClientContact relationship in RESUMate has no direct BambooHR equivalent — we map primary contacts to the Employee record under that Company if they exist in the HRIS. RESUMate Clients that represent staffing agencies or vendors rather than employers may need to be stored as Companies with a custom tag or department designation.

RESUMate Job Orders map to BambooHR Jobs. The Job Order title, description, requirements, and status map to BambooHR Job title, description, and status. RESUMate's job status (Active, Filled, On Hold, Cancelled) maps to BambooHR Job status values. The link between RESUMate Job Order and its Client is preserved as the BambooHR Job's Company association. We do not migrate RESUMate's Active Jobs filtered views as separate records; we extract the pipeline stage assignments from Active Jobs and apply them as Job status values or internal tags in BambooHR.

RESUMate Send-outs (tracking when a Candidate is submitted to a Job Order) map to BambooHR Applications. The Send-out date, status, and the Candidate-to-Job-Order link all transfer. The Candidate-to-Job-Order association is resolved during migration by matching the Candidate email and Job Order title against the newly created BambooHR Applicant and Job records. Send-out notes migrate as Application notes in BambooHR.

RESUMate Groups (named lists of Candidates, Clients, or Job Orders) map to BambooHR Tags applied to the relevant record type. Group membership is preserved as individual TagAssignment records in BambooHR. We ask the customer during scoping whether specific Groups should instead become BambooHR Departments (for Candidates who are also Employees) or should remain as Tags for recruiting segmentation.

RESUMate Calendar events (interviews, meetings, calls tied to Candidates or Job Orders) do not have a direct equivalent in BambooHR ATS. We extract event date, type, and notes, and create BambooHR Tasks or Notes on the relevant Applicant record. Customers who need interview scheduling migrate to BambooHR's built-in scheduling or a third-party calendar integration post-migration.

RESUMate stores resume files as binary attachments (Word, PDF, plain text). We extract these as binary files and upload them to the corresponding BambooHR Applicant record as a Document attachment. The parsed resume text that RESUMate generates is mapped into the Work Experience, Education, Skills, and Licenses sections of the BambooHR Applicant. File encoding issues (RESUMate Desktop sometimes stores files in legacy Windows code pages) are handled with encoding normalization before upload.

RESUMate Notes (free-text entries per Candidate record) migrate to BambooHR Notes on the Applicant or Employee record. We preserve the note date, author (mapped to the Employee if a match exists), and full note body. Notes are imported in chronological order per Candidate to preserve the review history.

RESUMate's unlimited custom fields require a mapping strategy in BambooHR. Standard text, number, and date custom fields map to BambooHR Employee Fields (available from Core plan). Dropdown and list-type custom fields in RESUMate map to BambooHR custom list fields. We cap the mapping at the customer's BambooHR plan limit: Core includes a set number of custom fields; Pro and Elite offer additional capacity. During scoping we audit the full RESUMate custom field schema and present a prioritized mapping plan, storing lower-priority fields as Notes if the BambooHR field budget is exhausted.

RESUMate Owner (the recruiter assigned to a Candidate, Client, or Job Order) maps to the BambooHR Employee record for the same person by email address. If the Owner is not a BambooHR user, we set the Applicant owner to the Employee record after conversion. Unmatched Owners are held in a reconciliation queue for the customer's HR admin to provision.