Migrate from ZingHR to Crelate

ZingHR employees in the Talent Acquisition module (candidates, applicants, and hire-stage records) map to Crelate Contact records. The ZingHR employee name, email, phone, and address fields map to Crelate's corresponding Contact fields. We distinguish between external candidates (new applicants) and internal candidates (existing employees applying for new roles) by evaluating the ZingHR EmployeeType and source fields. Internal candidates are flagged with a custom Crelate field internal_candidate__c for recruiter filtering. If ZingHR stores recruiting stage as a custom property, we map it to Crelate's tag-based pipeline stage.

ZingHR's department and cost-center structure does not map directly to Crelate Company records because Crelate Company represents a client organization in the recruiting context, not an internal department. For organizations using ZingHR to track client-candidate relationships (staffing agencies), we extract the ZingHR department name associated with each candidate as a reference string and create or match it against a Crelate Company record. For corporate HR teams migrating internal recruitment, the department is stored as a custom Contact field department__c rather than a Company lookup.

Active job postings in ZingHR map to Crelate Job records. The ZingHR job title, job code, job description, and location map to Crelate Job.Name, Job.Title, Job.Description, and Job.Location. We extract the ZingHR job status (open, closed, on-hold) and map it to Crelate Job.IsActive. Positions without a defined location in ZingHR receive a location value of TBD and are flagged for the recruiter to complete in Crelate before publishing.

ZingHR's recruitment pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) map to Crelate pipeline stages. Crelate uses a tag-based pipeline model rather than a fixed stage field. We create tag categories in Crelate matching the ZingHR stage names and assign the appropriate tag to each Contact record during migration. The customer selects the pipeline template (Standard, Technical, Executive, or custom) during scoping.

ZingHR onboarding tasks and checklists attached to a candidate map to Crelate Task records linked to the Contact. Each ZingHR onboarding task item becomes a Task with Body set to the task name, Status set to Open (or Completed if ZingHR marks it done), and ActivityDate set to the due date from ZingHR. Parent-record resolution links each Task to the migrated Contact ID in Crelate. Tasks without a due date receive a placeholder date and are flagged in the reconciliation report.

ZingHR recruitment activities including interview schedules, recruiter notes, and communication logs map to Crelate Activity records. Interview events map to Crelate Event with StartDateTime and Location. Recruiter notes and call logs map to Crelate Note or Task depending on whether a follow-up action is attached. We preserve the original ZingHR activity timestamp as Crelate's ActivityDate for timeline ordering. Communication-type activities from ZingHR map to Crelate Note attached to the Contact.

ZingHR's Attribute Master API exposes company-specific custom fields on employee records. We enumerate all custom attributes during scoping, map them to Crelate custom fields on the appropriate entity (Contacts, Companies, or Jobs), and handle Crelate field-type validation. Crelate requires that date fields cannot map to monetary fields; we validate type compatibility during the transform phase. The customer's admin confirms custom field creation in Crelate before migration so that target field IDs are available for the import.

ZingHR custom categories and tags on employee records (e.g., skill tags, source tags, clearance levels) map to Crelate Tags. The default tag category in Crelate is referenced with the key Default, and custom tag categories are created to match ZingHR's category names. Tags are stored as a tags object in Crelate's API with keys corresponding to category names and values as arrays of tag strings. We enumerate tag values during scoping and resolve them against Crelate's tag catalog during import.

ZingHR manager-employee associations on recruiting records (e.g., hiring manager on a job posting or recruiter assigned to a candidate) map to Crelate Contact records with a custom field hiring_manager__c holding the manager's name. Crelate's Contact object does not have a native manager lookup, so we use a custom Contact field rather than a native relationship. The customer's admin creates this field in Crelate before migration.

ZingHR employee documents (offer letters, ID proofs, experience letters) attached to candidate records in the Talent Acquisition module map to Crelate file attachments on the corresponding Contact record. We download documents from ZingHR's ESS export, store them with the migration artefacts, and attach them to the migrated Crelate Contact via ContentDocumentLink. File type preservation (PDF, DOCX, image) is maintained. If a document has no associated candidate in ZingHR, it is held in a documents-only queue for manual assignment.

ZingHR tracks candidate source (referral, job board, direct apply, agency) as a custom attribute. We map this to a Crelate custom field candidate_source__c on Contact or to a tag category called Source with individual tags for each source value. The customer chooses the strategy during scoping based on whether they plan to filter candidates by source in Crelate's search and reporting.

ZingHR employee records containing payroll history, attendance data, leave balances, performance reviews, and e-Separation data do not have a Crelate equivalent and are not migrated. Crelate is an ATS without payroll, attendance, or HRMS capabilities. We flag these record types during scoping and exclude them from the migration scope. The customer's ZingHR instance continues to operate as the HRMS of record for payroll, attendance, and compliance. If the customer requires a separate HRMS alongside Crelate, we can scope a parallel migration from ZingHR to a destination like BambooHR, Workday, or SAP SuccessFactors as a separate engagement.