Migrate from Zimyo to Recruit CRM & ATS

Zimyo candidate profiles (name, email, phone, resume, skills, work history, source channel, availability status) map directly to Recruit CRM Candidate records. We preserve the original sourcing channel from Zimyo as a custom field on the Recruit CRM Candidate for reporting continuity. Resume files migrate as document attachments with original filenames preserved. Candidate availability dates and notice period data from Zimyo map to custom fields in Recruit CRM since the availability schema differs between platforms.

Zimyo job postings (title, department, location, employment type, description, requirements, salary range, hiring manager) map to Recruit CRM Job records. The job status lifecycle in Zimyo (draft, open, on hold, closed) maps to Recruit CRM job status values. We flag any multi-location job postings in Zimyo that may need to split into multiple Recruit CRM job records if the destination requires separate pipeline tracking per location.

Zimyo applications (candidate-to-job association, submission date, current stage, referred by, cover letter) map to Recruit CRM Application records linked to the corresponding Candidate and Job. Application stage names in Zimyo map to Recruit CRM pipeline stage values during schema discovery. We reconcile any custom application stages in Zimyo against Recruit CRM's configurable pipeline before import.

Zimyo interview schedules (interview type, scheduled date and time, interviewer, location or meeting link, interview duration) map to Recruit CRM Interview records. We resolve interviewer names in Zimyo to the corresponding user accounts in Recruit CRM. Meeting links from Zoom or Google Meet integrations in Zimyo carry forward as interview location details. We flag any interview feedback forms that may require a separate notes or scorecard migration step.

Zimyo interview scorecards with rating categories, scores, and evaluator comments map to Recruit CRM Candidate Notes attached to the relevant Application. Rating values are normalized if the scoring scale differs between platforms. We consolidate multi-evaluator scorecards into a single structured note per interview with evaluator attribution preserved in the note body.

Zimyo offer letters (offered role, compensation details, start date, offer status, signed document) migrate as document attachments on the Recruit CRM Candidate record. Offer status (accepted, rejected, pending, withdrawn) maps to a custom candidate status field. Compensation details migrate as a structured note to preserve the financial terms outside of Recruit CRM's standard fields.

Organizations using Zimyo for internal recruiting that have placed candidates (employee records that originated as candidates) may need to link placed employee records to the original Candidate in Recruit CRM for placement history tracking. We create a placement reference on the Candidate record pointing to the employee identifier for audit purposes. This mapping requires configuration review during scoping to confirm whether placed employees are in scope for migration.

Zimyo departments and cost centers used as job posting targets map to Recruit CRM Department values or to Client records if the organization structure in Zimyo includes client company records alongside internal departments. We resolve the mapping during scoping based on how the customer uses Zimyo's organization module.

Zimyo reporting hierarchies (hiring manager assignments, recruiter-to-team relationships) map to Recruit CRM User records and Candidate assignment rules. We resolve users by email match and flag any Zimyo users without a corresponding Recruit CRM seat for the customer's admin to provision before final import.

Employee documents in Zimyo (contracts, ID proofs, certifications, offer letters) that are associated with candidates who have active applications migrate as document attachments on the Recruit CRM Candidate record. We extract file blobs and metadata, preserve original filenames and upload timestamps, and run integrity checksums. Documents tied to purely HR records (payroll, benefits) without a recruitment context do not migrate.

Zimyo payroll runs (earnings, deductions, tax withholdings, net pay, payroll run dates) have no equivalent in Recruit CRM's ATS data model. These records are outside Recruit CRM's scope and are flagged as non-migrated in the handoff document. Organizations needing payroll data in a destination system should migrate payroll history separately to a dedicated payroll platform.

Zimyo attendance records (clock-in/clock-out timestamps, overtime, shift mappings) and leave management data (leave types, entitlement balances, accrual rules, carry-forward policies) do not map to Recruit CRM. Recruit CRM does not store attendance or leave data. These are flagged in the handoff document with a recommendation to migrate attendance and leave history separately if required for HR compliance or archival purposes.