Migrate from Recruit ATS by HR Cloud to Crelate

Recruit ATS Candidate records map directly to Crelate Contact. We extract contact info (name, email, phone, address), work history, education, and the primary resume attachment. Knock-out question responses stored as custom fields migrate to Crelate custom fields on Contact. The Contact in Crelate is the primary person record; it can be linked to an Account (client company) once the Crelate CRM layer is configured.

Recruit ATS Job records map 1:1 to Crelate Job. We transfer title, description, location, department, employment type, and status (open/closed/archived). Custom request fields attached to the job posting migrate as Crelate custom fields on Job. Job status is preserved to avoid accidentally re-activating archived postings during migration.

The Application junction between Candidate and Job maps to Crelate's Application (job submission) record. We preserve the applied date, current pipeline stage, source channel (referral, job board, direct), and any rejection reason. Stage assignment requires remapping because HR Cloud stage IDs are system-generated and Crelate regenerates its own stage IDs at import time.

Recruit ATS Pipeline Stages are fully custom and ordered by ordinal position. We extract the stage name and ordinal position and create corresponding stages in Crelate's pipeline configuration before any Application records are imported. Stage IDs are regenerated in Crelate, so stage remapping is a configuration step, not a data transform. We document the ordinal mapping in a stage-translation table.

Tags in Recruit ATS are flat string labels applied to Candidates and Jobs. We export the full tag set as string arrays and apply them identically in Crelate. Multi-tag records migrate as arrays; the destination Crelate field supports multi-value tag input. Tag taxonomy is preserved exactly so that existing filter and segmentation logic that depends on tags continues to function post-migration.

Notes attached to Candidates in Recruit ATS migrate as Crelate Note records linked to the Contact. We preserve the note body as plain text, the original author name, and the original timestamp. Note thread structure (replies to notes) flattens into chronological entries in Crelate's note list, as Crelate does not support nested note threads natively. We flag this flattening in the migration report.

Resume files, cover letters, and uploaded documents attached to Candidates and Jobs migrate as binary blobs. We preserve the original filename and MIME type, and attach the file to the corresponding Crelate Contact or Job record. Large attachments (files over 10 MB) are chunked during API transfer to avoid timeout failures. We verify file integrity with a checksum after migration.

Non-entity-type custom fields on Candidate and Job records map to Crelate custom fields of equivalent type (text, number, date, picklist). We perform a type audit during scoping to ensure that picklist values in HR Cloud map to Crelate picklist options rather than free-text fields. Picklist value sets that do not exist in Crelate are pre-created during schema configuration.

Recruit ATS entity-type custom fields link a Candidate record to another Candidate or Job record. We detect these during the pre-flight audit, extract the source record IDs, and generate a re-linkage map. In Crelate, we create the equivalent custom lookup field but cannot pre-populate the relationship because destination record IDs are generated at import time. The re-linkage map lists every affected record pair (source_id, destination_id, relationship_field) so your team can re-establish links in Crelate's UI after migration. We include step-by-step re-linkage instructions in the handoff package.

Automation rules and SMS sequence configurations are not exposed via HR Cloud's API and cannot be migrated as code. During scoping, we run a rules audit and produce a written automation registry listing every active rule: its trigger, conditions, actions, and a recommended Crelate workflow equivalent. Your team uses this registry to rebuild automations in Crelate's workflow builder. We flag any compliance-critical automations such as auto-rejection thresholds separately so they are not missed in the rebuild.

Interview scorecards and evaluation templates are not exposed via HR Cloud's public API. We cannot migrate structured evaluation data. We recommend exporting scorecard responses as PDF exports from the HR Cloud UI before the migration window and attaching them as documents to the corresponding Candidate records in Crelate post-migration. The evaluation template structure (rating categories, scoring scales) is documented in our automation registry for manual recreation in Crelate's evaluation forms.

SMS interview invite sequences and automated messaging sequences in Recruit ATS are tied to automation rules that are not API-exportable. We document the active SMS sequences in the automation registry with their trigger conditions, message templates, and send sequences. Crelate's workflow automation supports SMS steps via integrations; the registry provides the template content and logic for your team to configure equivalent sequences in Crelate after migration.