Migrate from Apploi to Crelate

Apploi Job records map to Crelate Job. We extract title, description, location, department, and employment type from Apploi's admin CSV export and map these to Crelate's corresponding Job fields. Active Jobs migrate as published; closed or archived Jobs migrate with their status preserved so the hiring history is complete. Apploi's multi-job-board posting configuration (Indeed, ZipRecruiter, LinkedIn) does not migrate because it is stored as account-level settings rather than per-Job data.

Apploi Candidate records map to Crelate Candidate. We extract contact information, employment history, and availability data. Healthcare credential custom fields (CNA, RN, LPN license numbers and expiration dates) are Apploi custom properties stored on the Candidate record; we map each to a corresponding Crelate custom field and flag every credential for manual validation against the original documentation before the migration window closes. Candidate status and source attribution migrate from Apploi's application tracking properties.

Apploi Application records link a Candidate to a Job and capture stage transitions (Applied, Screening, Interview, Offer, Hired, Rejected). We map each Application to a Crelate Candidate Job Assignment record with the Apploi stage mapped to the corresponding Crelate status. Application timestamps for each stage transition are preserved as activity entries on the Candidate record in Crelate.

Apploi Offer records include compensation details, start dates, and offer status. Compensation fields in Apploi vary by customer configuration, so we map them to Crelate Offer fields or custom fields on the Candidate record depending on the customer's Crelate setup. Offer status (Accepted, Declined, Pending) migrates as a picklist value. We flag any non-standard compensation fields during scoping for manual field creation in Crelate before migration.

Apploi Onboarding Task records track pre-hire compliance items (I-9, background checks, credential verifications). We map these to Crelate Tasks or custom checklist fields on the Candidate record. Apploi's automated onboarding packet configuration does not migrate because it is a workflow rule rather than data. Apploi's compliance alert rules for expiring credentials are documented separately as a handoff item for the customer's admin to rebuild in Crelate's task reminder system.

Once hired, Apploi Employee records include hire date, job title, department, and employment status. We map these to Crelate Candidate records with an Employee record type, preserving the hire date and job assignment. Benefits, PTO, and payroll data are not Apploi data and are not in scope for migration.

Apploi stores certifications and license numbers as custom fields on Candidate or Employee records rather than a dedicated credential object. During scoping, we inventory every Apploi credential custom field per customer configuration, create equivalent custom fields in Crelate (License Number, License State, Expiration Date, Credential Type), and run a pre-migration validation pass to flag expired licenses, missing values, and formatting inconsistencies before the data is imported. This is a manual review step that requires the customer's HR or compliance team to validate against source documentation.

Apploi interview evaluations and scorecard data exist as attachments or notes within the Application record. We export these as files and attach them to the corresponding Crelate Candidate record. Structured scorecard data (rating values, rubric scores) that exists as structured Apploi fields migrates to Crelate custom fields on the Candidate record.

Apploi Owner records map to Crelate User. We resolve by email match against the Crelate destination tenant's user list. Any Apploi Owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId is a required reference on Job and Candidate assignments.

Apploi's multi-job-board posting configuration (Indeed Platinum Partner status, ZipRecruiter, LinkedIn, healthcare-specific job sites) is stored as account-level settings. These do not migrate because they are platform credentials and integration configurations rather than candidate or job data. We document the existing posting configuration for the customer's admin to reconfigure in Crelate's job distribution settings post-migration.

Apploi shift scheduling data is operational and not retained historically. Current and upcoming schedules are available during the Apploi subscription window, but historical shift data is purged on a rolling basis and is not available for export. We do not migrate shift schedules. If the customer requires scheduling in Crelate, third-party scheduling tools such as Calentras or ShiftAdmin integrate with Crelate via its API.

Apploi automated workflows (candidate prescreening, stage-triggered messages, compliance alerts) do not migrate as code. We document every active Apploi automation with its trigger conditions, actions, and affected objects, and deliver this as a written handoff inventory for the customer's admin to rebuild in Crelate's task reminder and email automation system. This is outside the data migration scope per FlitStack AI standard terms.