Migrate from AgileATS to BambooHR

AgileATS Candidate records map directly to BambooHR Applicant records. The mapping preserves name, email, phone, address, candidate status, and source. Custom fields on the AgileATS Candidate (clearance level, clearance type, clearance expiry date, partner assignment, EEO flags) migrate to BambooHR custom Applicant fields that we configure before import. We flag any AgileATS custom fields that have no direct BambooHR equivalent and document them in a field-gap addendum.

AgileATS Job records map to BambooHR Job requisitions. Job title, location, department, employment type, and job description migrate directly. Any AgileATS pipeline assignment or job status flags map to BambooHR's job status values. Active jobs and closed jobs migrate separately so the customer's BambooHR admin can set final open/closed status after review.

AgileATS structured Agile Recruiting pipeline stages (which vary by customer configuration) map to BambooHR's configurable hiring pipeline. BambooHR's standard stages (Applied, Phone Screen, Interview, Offer, Hired, Rejected) serve as the base. Any AgileATS stages beyond this set require Pro or Elite plan and custom stage configuration. We create the full stage mapping document during scoping so the customer's BambooHR admin configures the pipeline before import begins.

AgileATS Offer records (compensation, start date, offer status) attach to the corresponding Candidate record. We map the offer as structured fields on the BambooHR Applicant record. BambooHR's ATS stores offer data as part of the applicant record rather than as a standalone object, so we flatten the offer schema into the applicant import. The offer-to-candidate relationship is preserved through applicant ID resolution during import.

AgileATS User and Recruiter records map to BambooHR Employee records for users who will have system access. We resolve by email match. Any AgileATS Recruiter without a matching BambooHR Employee is held in a user reconciliation queue for the customer's admin to provision before record import. Partner Users (a separate billing class in AgileATS at $20/month each) are flagged separately because BambooHR does not have an equivalent partner user concept; they are migrated as standard BambooHR Employees with appropriate access scoped by the customer's admin post-migration.

AgileATS Partner and Subcontractor records (distinct from full Recruiter seats) have limited permissions and are billed separately. BambooHR does not have a native partner user model. We migrate partner records as BambooHR Employee records, preserving partner assignment references on candidate records where applicable. We flag which candidates have a partner assignment and provide a written remapping plan so the customer's admin can configure appropriate access levels in BambooHR post-migration.

AgileATS stores security clearance level and status as structured fields on Candidate records. These fields have no direct BambooHR ATS equivalent, so we create custom fields on the BambooHR Applicant object: clearance_level__c (picklist), clearance_type__c (text), clearance_expiry_date__c (date). We flag any candidates whose clearance status may have expired or requires renewal verification during the migration window. This is a high-value pair-specific migration concern because clearance data is central to the AgileATS value proposition and must transfer accurately.

AgileATS custom fields (commonly used for clearance types, partner assignments, EEO flagging, EEO-1 categories, hiring manager assignments, and GovCon-specific tracking) require explicit field-level review. We extract all AgileATS custom field definitions during scoping, map them to BambooHR custom Applicant fields by type (text, picklist, date, checkbox), and flag any AgileATS field types that exceed BambooHR's custom field capabilities. Fields that cannot map 1:1 are documented in the field-gap addendum with a recommended BambooHR workaround.

AgileATS stores candidate attachments (resumes, certifications, security clearance forms, background check documents) in a separate file store. We export these files alongside record data and re-attach them to the corresponding BambooHR Applicant record. We note any file size limits enforced by BambooHR (typically 10 MB per file) and flag any AgileATS attachments that exceed this limit for manual re-upload after migration.

Recruiter notes and activity timestamps export from AgileATS as structured records. We map these to BambooHR Notes attached to the corresponding Applicant record. Activity ordering is preserved where BambooHR's note creation timestamp allows. The BambooHR ATS also stores activity in the application's activity feed; we prefer the structured Notes object for compliance-relevant activity and use the activity feed for informal recruiter commentary.

AgileATS OFCCP, DoL, and EEO compliance data lives in candidate fields (EEO flags, hire dates, job categories, pay ranges, veteran status, disability status) rather than as standalone report objects. We migrate the underlying compliance data fields to BambooHR custom Applicant fields and deliver a written Compliance Field Map document that maps each AgileATS compliance field to the corresponding BambooHR field name and to the report line item it populates. The compliance team uses this document to validate OFCCP and EEO reporting output in BambooHR post-migration. BambooHR's Compliance Intelligence module (Pro and Elite) provides reporting tools; the compliance team rebuilds any automated report generation they relied on in AgileATS.