Migrate from Apex Human Capital Management to Crelate

Apex Hire On The GO candidate records map directly to Crelate Candidate records. We extract first name, last name, email, phone, address, source channel, and application date. The Apex candidate status (applied, screening, interview, offer, hired, rejected) maps to Crelate pipeline stage based on the customer's configured Hire On The GO stage values. Any Apex candidate rating or score migrates to Crelate's custom rating field on the Candidate record.

Apex Hire On The GO job postings map to Crelate Job records. We extract job title, department, location, employment type (full-time, part-time, contract), and posting date. The Apex job status (open, paused, closed, filled) maps to Crelate Job status. Job description text migrates as the Crelate Job description field; any structured fields in Apex (requirements, benefits) map to Crelate custom fields or job notes.

Apex Hire On The GO pipeline stages are client-configured and do not map 1:1 to Crelate's default stage set. During discovery we extract the customer's Apex stage configuration and design a Crelate pipeline with matching stage names, ordering, and probability values. Crelate supports unlimited custom stages per pipeline, so the Apex stage structure translates without loss. Stage mapping is reviewed by the customer's recruiting lead before migration.

Apex Hire On The GO applications (the association between a Candidate and a Job Opening) map to Crelate Candidate Job Activity records, which represent the candidate's journey through the hiring pipeline for a specific job. We preserve the application date, current stage, and any stage-change timestamps as Crelate Activity entries with type = Stage Change.

Apex stores resumes, cover letters, and supporting documents as binary blobs or linked URLs attached to candidate records. We extract the files, associate them with the correct Crelate Candidate record, and preserve the original filename and file type. Crelate displays these in the Candidate's Talent Card under the Documents section. Binary files use Crelate's document attachment endpoint with proper MIME type handling.

Apex Hire On The GO interview records map to Crelate Activity records with Activity Type = Interview. We preserve interview date, interviewer name (mapped to Crelate User or contact), interview type (phone screen, on-site, panel), and any notes or feedback scores stored in Apex. Interview-to-candidate association uses the Crelate Candidate Job Activity lookup.

Apex offer letter documents stored as attachments on candidate records migrate as Crelate document attachments on the Candidate record. If Apex stores structured offer fields (salary, start date, offer status), we create a Crelate Activity Note with the offer details for audit trail purposes. The offer letter PDF migrates as a binary attachment.

For organizations using Apex HCM for both recruiting and ongoing HR, existing employee records may need to be available in Crelate for internal mobility and future hiring. We create inactive Candidate records in Crelate for each Apex employee, preserving name, email, department, and job title. The records are flagged inactive so they do not appear in active recruiting pipelines but remain searchable for internal talent programs. This is optional scope confirmed during discovery.

Apex employee self-service portal settings, role assignments, and delegated proxy configurations do not have a Crelate equivalent. Crelate does not expose an employee-facing portal; it is a recruiter and hiring-manager tool. We document these Apex configurations in the automation inventory for the customer's IT team to evaluate against Crelate's permission model (Crelate Roles: Admin, Recruiting Manager, Recruiter, Sourcer, Hiring Manager, Observer).

Apex onboarding document checklists, new-hire task lists, and I-9 workflow configurations are documented for rebuild in Crelate Hire. Crelate Hire automates hiring workflows, credential tracking, compliance tasks, and candidate onboarding but uses its own workflow builder. We deliver a written map of every Apex onboarding step and its recommended Crelate Hire equivalent, with task assignments, due dates, and document collection requirements.

Apex benefits elections, health plan selections, and retirement plan assignments do not migrate to Crelate. Crelate is an ATS and recruiting CRM; it does not store benefits data. We flag every benefits-related object in the Apex export and direct the customer to their HRIS or benefits administration platform for this data. If the organization is also moving payroll to a separate platform, benefits elections are in scope for that parallel migration.

Apex payroll registers, earnings, deductions, and tax withholdings do not migrate to Crelate. Crelate's data model does not include payroll, compensation, or tax withholding fields. Organizations requiring payroll functionality after switching to Crelate for recruiting must implement a separate payroll platform. We do not migrate payroll data as part of an Apex-to-Crelate scope; that work is separate.

Apex PTO accrual balances, carryover rules, and earning-rate logic do not migrate to Crelate. Crelate does not track time-off balances. We extract a snapshot of current PTO balances from Apex as a reference document for the customer's HR team to configure in their HRIS or standalone time-off platform if one is selected alongside Crelate.

Apex 1095-C records and coverage measurement data do not migrate to Crelate. ACA reporting is an HR and payroll function outside Crelate's scope. We flag ACA-related records in the Apex export and note that these require a separate HRIS platform if the customer is moving away from Apex HCM entirely for payroll and compliance.