Migrate from Apploi to Recruit CRM & ATS

Apploi Job postings with title, description, location, department, and employment type map directly to Recruit CRM Job records. We import active jobs 1:1 and flag any historical (filled or archived) jobs for optional import into Recruit CRM's job history. Apploi's multi-job-board posting configuration (Indeed, ZipRecruiter, LinkedIn) lives in account settings and is not candidate or job record data; we do not migrate posting credentials or board-level history.

Apploi Candidate records with contact information, employment history, and address data map 1:1 to Recruit CRM Candidate records. We use the candidate email address as the dedupe key and flag any duplicates for customer-side resolution before final import. Apploi does not have a separate Client object; candidate employer associations from Apploi's employment history map to Recruit CRM Client records if the employer exists as a contact, or are stored as a free-text field if no Client record is warranted.

Apploi Applications link a Candidate to a Job and capture the full application status history (Applied, Screening, Interview, Offer, Hired, Rejected) with stage-transition timestamps. We preserve the complete application history in Recruit CRM by setting the initial application status and adding status-change notes for each transition. If Apploi stored application notes or source attribution (referral, job board, direct), these migrate as Notes attached to the Candidate record.

Apploi Offer records include compensation details, start dates, and offer status. Compensation fields vary by customer Apploi configuration, so we map each one to a Recruit CRM Offer field and flag any non-standard fields for customer validation. Offer status (Pending, Accepted, Declined, Withdrawn) maps directly to Recruit CRM's offer status values. We do not migrate signed offer letter PDFs as structured records; these are delivered as a file inventory for manual re-upload by the customer admin.

Apploi onboarding task records track pre-hire compliance items including I-9 verification, background checks, and credential verifications. These map to Recruit CRM's Onboarding Management module tasks. Healthcare-specific compliance task templates (CNA skill checklists, RN license verification steps, continuing education tracking) do not have direct equivalents in Recruit CRM's generic onboarding model and are documented as a rebuild item for the customer admin post-migration.

Apploi employee records include hire date, job title, department assignment, and employment status. Once a candidate is hired in Apploi, the record transitions from Candidate to Employee status. We migrate employee records as Candidate records in Recruit CRM, setting the status to 'Placed' and preserving the hire date, job title, and department as custom fields. We do not migrate benefits, PTO, or payroll data as Apploi stores these in separate modules not used for ATS migration.

Certifications (CNA, RN, LPN), license numbers, expiration dates, and state of issuance are stored as Apploi custom fields on Candidate or Employee records. These do not map to a dedicated Recruit CRM credential object at the free or Growth tier. We map each credential to a Candidate custom field (text or date type as appropriate) and flag every credential field for manual validation by the customer's admin against original documentation. This step catches expired licenses and mis-typed certification codes before the data goes live.

Apploi interview evaluations and scorecard data exist as attachments or structured notes within the Application record. We export these as files or structured text and attach them to the corresponding Recruit CRM Application record. Scorecard rubric data (rating scales, competency fields) does not map to Recruit CRM's native interview format and is delivered as a structured note summary for manual entry if the customer's workflow requires it.

Apploi Owner records (recruiters and hiring managers assigned to Jobs, Candidates, Applications, or Offers) map to Recruit CRM User records. We resolve Apploi owners by email match. Any Apploi Owner without a matching Recruit CRM User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Apploi owners are mapped to inactive Recruit CRM users to preserve assignment history.

Apploi does not have a dedicated Client object; employer information appears in Candidate employment history or as custom fields on Candidate records. We extract distinct employer names from Candidate records, deduplicate them, and create Recruit CRM Client records for each unique employer. The employer name becomes the Client name, and any employer address or contact data found in Apploi maps to the Client address and contact fields. Client records are created before Candidate records so that the Client-Candidate association is satisfied at insert time.

Apploi's multi-job-board posting configuration (Indeed, ZipRecruiter, LinkedIn, healthcare-specific boards) is stored as account-level settings, not as job or candidate data. These credentials and posting histories do not migrate. We document the full Apploi job board configuration during scoping so the customer's admin can recreate the integrations in Recruit CRM's job distribution settings or re-authenticate board accounts there.

Apploi's shift scheduling module stores only active and recently completed schedules; historical shift data is purged on a rolling basis and is not available for export. We scope out shift history entirely and document this limitation in the migration inventory. Current and upcoming schedules are out of scope for Recruit CRM migration because Recruit CRM does not include a native shift scheduling module. The customer should treat shift data as a separate export and storage concern.