Migrate from Zimyo to Crelate

Zimyo candidate profiles (personal details, contact information, work history, education, skills, source attribution) map to Crelate People records. The candidate's email address serves as the dedupe key during import. Any candidate rating or ranking scores from Zimyo migrate to custom fields on the Crelate People record. If the candidate has been placed or is currently in an active application, we preserve the stage and the linked job posting reference.

Zimyo application records map directly to Crelate Application records. The application status (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Crelate's application stage values. Application submission timestamp migrates as the Created Date on the Crelate Application. Any application-specific notes or rejection reasons from Zimyo migrate as text fields on the Application record.

Zimyo job postings (title, description, requirements, location, employment type, department assignment) map to Crelate Job records. The job status (Draft, Active, Paused, Closed) migrates to Crelate Job status. Salary range and compensation details from Zimyo map to custom compensation fields in Crelate. We align any Zimyo department or cost center assignments with Crelate's Job Categories or Tags configuration.

Zimyo interview schedules (interview type, date and time, interviewer, location or meeting link, candidate reference, job reference) map to Crelate Activity records of type Interview or Event. We preserve the interviewer assignment by resolving Zimyo interviewer names or emails against Crelate User records. Calendar or video meeting link metadata migrates as Activity description or custom URL fields.

Zimyo interview scorecards (rating criteria, scores, interviewer feedback, recommendation) map to Crelate Scorecard records linked to the relevant Application and Activity. Competency rating scales vary by organization and require value mapping during scoping to ensure consistent scale application across migrated and future scorecards. Any overall recommendation (Strong Hire, Hire, No Hire, Strong No Hire) migrates as the Crelate Scorecard recommendation field.

Zimyo offer letter documents (PDF or file blob with offer terms, compensation, start date, candidate reference) migrate as Crelate Document records attached to the relevant Application and Person. We preserve the original filename, upload timestamp, and file integrity checksum. Offer terms (salary, equity, start date, contingencies) migrate as custom fields on the Crelate Application or as structured Activity notes if no dedicated offer object exists in the customer's Crelate configuration.

Zimyo's configurable hiring pipeline stages (typically: Applied, Screening, Interview, Assessment, Offer, Onboarding) map to Crelate Pipeline stages. We align the stage order and rename stage labels to match Crelate's terminology during environment setup. If Zimyo uses multiple pipelines per department or role type, each maps to a separate Crelate Pipeline with its own stage sequence.

Zimyo Employee records do not have a native Crelate equivalent because Crelate is an ATS, not an HRMS. Employee records that overlap with recruiting candidates (hired candidates who now appear as employees) can be stored as Crelate People records with a custom 'Employee Status' flag. Payroll, compensation history, bank details, emergency contacts, and benefits enrollments do not map to Crelate and require a parallel HRMS or payroll platform post-migration. We flag all employee fields that have no destination and provide a structured Employee Export package for the customer's chosen HRMS replacement.

Zimyo leave balances, accrual rules, carry-forward policies, and approval workflows have no Crelate equivalent. Crelate is a recruiting platform and does not track employee leave entitlements. We export leave balance snapshots as of the migration date and flag this module as requiring either retention in Zimyo (partial continued use), migration to a dedicated leave management platform, or manual reconciliation during HRMS cutover. Leave approval workflows do not migrate as automation; a written inventory of active approval rules is included in the deliverables.

Zimyo payroll history (earnings, deductions, tax withholdings, reimbursements, net pay) has no Crelate equivalent. Crelate does not process payroll. We export payroll run summaries and reconciliation files from Zimyo as structured CSV exports for the customer's payroll team to load into their replacement payroll platform. Individual earning codes and deduction categories are exported with full metadata for mapping into ADP, Rippling, Gusto, or whichever payroll system the customer selects post-migration.

Zimyo clock-in/clock-out timestamps, overtime calculations, and shift mappings do not map to Crelate. Attendance is an HRMS function, not an ATS function. We export the most recent 12 months of attendance summaries as a structured export file for the customer's HRMS replacement. Attendance data integrity is validated against Zimyo's own reports before export to ensure no silent truncation.

Zimyo performance review cycles, goals, competency ratings, self-assessments, and manager feedback have no Crelate equivalent. We export historical performance review data as structured records including cycle name, rating scores, competency framework mapping, and reviewer feedback text. The export package is formatted for import into the customer's selected performance management platform (Lattice, 15Five, BambooHR, or another HRMS). Active review cycles in progress are flagged for manual completion or HRMS transition handling.

Zimyo departments, cost centers, locations, and reporting hierarchies map partially to Crelate's Department and Tags configuration. We extract the full organization tree from Zimyo (departments, sub-departments, location codes, cost center IDs) and configure Crelate Departments and Tags to match. Reporting hierarchies (manager-employee relationships) are exported as a structured org chart export and are not built into Crelate's ATS data model; the customer's HRMS replacement maintains the official org structure post-migration.

Zimyo employee documents (contracts, ID proofs, certifications, offer letters) attached to employee records are not the same as Crelate's candidate documents. Candidate-related documents (resumes, cover letters, portfolio files) attached to Zimyo candidate profiles migrate as Crelate Document records attached to the relevant People record with original filename and upload timestamp preserved via file integrity checksum. HRMS documents (employment contracts, tax forms, ID scans) are exported separately as a document package for the customer's HRMS replacement.

Zimyo organization-specific custom fields added to candidate profiles, job postings, or applications map to Crelate custom fields. We discover the custom field schema during scoping, map field types (text, number, date, picklist, checkbox, multi-select) to their Crelate equivalents, and configure the destination fields in Crelate before migration. Custom fields that reference employee-specific data (e.g., employee ID, department assignment) are flagged as requiring either a custom integration or a separate HRMS data source post-migration.