Migrate from AgileATS to Recruit CRM & ATS

AgileATS Candidates map directly to Recruit CRM Candidates. We extract all standard profile fields (name, email, phone, address, status, source) and map them to Recruit CRM's candidate object. Custom fields for clearance type, clearance status, and EEO flags require explicit mapping decisions during scoping because these are GovCon-specific fields that Recruit CRM stores as standard custom fields rather than native compliance objects. We flag any custom fields that cannot be represented in Recruit CRM without a custom object definition.

AgileATS Jobs (open requisitions with title, location, clearance requirements, and pipeline assignment) map to Recruit CRM Jobs. The job-to-candidate association migrates as a linked relationship so pipeline history carries over. We flag any clearance-level requirements stored as custom fields on the Job object for explicit mapping to Recruit CRM's custom field schema.

AgileATS Agile Recruiting stages are customer-configured with variable names and counts per instance. We extract the complete stage inventory during scoping, map each to a Recruit CRM pipeline stage, and create a stage mapping document. Stages with no direct Recruit CRM equivalent are flagged for the customer to define before migration. Stage ordering and probability percentages transfer where supported.

Offer records including compensation details, start dates, and status link to the migrated candidate record via the candidate's unique identifier. We preserve the offer-to-candidate relationship throughout the migration so that offer history remains accessible in Recruit CRM.

Security clearance level and status are stored as structured custom fields on candidate records in AgileATS. We preserve these values explicitly in Recruit CRM custom fields of the same type. Candidates with expired clearance or pending reinvestigation are flagged with a note so the recruiting team can follow up post-migration.

EEO compliance flags (race, ethnicity, gender, veteran status, disability status) migrate as read-only custom fields in Recruit CRM. These fields support compliance reconstruction but are not rendered as native compliance reports. We document the mapping from each AgileATS EEO field to its Recruit CRM equivalent so the compliance team can validate output after cutover.

AgileATS tracks partner user assignments as a separate billing class with distinct permissions. We extract partner assignments linked to candidate records and either map them to Recruit CRM Contacts (if the partner is a hiring manager or client contact) or flag them as a custom field requiring a permissions review in Recruit CRM because the platform does not have an equivalent partner user concept.

AgileATS stores candidate attachments in a separate file store. We export files alongside record data and re-attach them in Recruit CRM linked to the corresponding candidate record. We flag any files that exceed Recruit CRM's attachment size limits or use unsupported formats. Binary attachments require a separate pass after record import completes.

AgileATS User records include role, clearance level, and org assignment. We resolve users by email match to Recruit CRM users. Any AgileATS Recruiter without a matching Recruit CRM user is held in a reconciliation queue for the customer's admin to provision before record import resumes. Partner Users require a separate decision during scoping because Recruit CRM's permission model differs.

Recruiter notes and activity timestamps export from AgileATS with their original timestamps. We map these to Recruit CRM Notes linked to the candidate record. Activity ordering is preserved by setting the note creation date to the original AgileATS timestamp. Activity types (call, email, meeting) are noted in the note body where Recruit CRM does not support a native activity subtype.