Migrate from Worknice to Recruit CRM & ATS

Worknice People records map to Recruit CRM Candidate records. We map first name, last name, email, phone, work location, employment type (Employee, Contractor, Manager), and start date to their corresponding Candidate profile fields. The Worknice role assignment (Employee, Contractor, Account owner) is stored in a custom Candidate field for reference. Active People records with a recruitment or staffing context migrate as active Candidates; records with a historical (terminated) status migrate as inactive Candidates or are held for customer decision on archive strategy. Deduplication is applied on email address at import time.

Worknice Positions define job titles and reporting hierarchies. Since Recruit CRM uses Jobs as hiring requisitions rather than organizational position records, we map Worknice position names and department assignments to Candidate profile fields (Job Title, Department, Current Position). Position hierarchies and reporting relationships are flattened into a custom field or a candidate notes entry rather than recreated as structured org-chart data, because Recruit CRM does not have a native position hierarchy object. Bundle template associations on positions are exported as metadata and flagged for manual configuration in Recruit CRM.

Leave entitlements and accrual balances are tied to People and position start dates in Worknice. Recruit CRM has no native leave management module. We export leave type, current balance, and accrual method as separate fields from Worknice's leave export and map them to custom Candidate fields (e.g., Annual Leave Balance, Sick Leave Balance) or attach them as a structured notes entry per candidate. The accrual method itself (e.g., front-loaded vs. monthly accrual) is documented in migration notes for the customer's HR team to configure in their chosen HR or payroll system post-migration.

Worknice 360 reviews, customizable review forms, reviewer relationships, and completion status have no direct equivalent in Recruit CRM's ATS data model. We export review records per person including form question responses, overall ratings, and review period. These are mapped to a Candidate custom object (if Recruit CRM's custom field capacity is sufficient) or as structured notes attached to the Candidate record. Review form designs and question structures are not migratable and require a separate documentation pass for the customer to rebuild in their chosen review tool.

Worknice supports company-level OKRs and employee goals with parent-child alignment hierarchies. Recruit CRM does not have a native goals or OKR module. We export goal titles, descriptions, progress percentages, and alignment relationships as structured text entries attached to the relevant Candidate record. Goal hierarchy (parent-child) is preserved in the notes field textually. We flag in the migration inventory that goal and OKR management requires a dedicated tool outside Recruit CRM post-migration.

Worknice stores compliance documents, contracts, and onboarding paperwork per person. We export documents as binary files and recreate the attachment relationship in Recruit CRM by linking the file to the corresponding Candidate record. File naming conventions from Worknice may not carry over in a structured way; we apply a consistent naming pattern (CandidateName_DocType_Date) during import. The original Worknice folder or bundle context is documented but not reconstructable in Recruit CRM.

Worknice Bundles group templates (documents, onboarding tasks, review forms) assigned to positions or people during onboarding. Bundle names and template associations are exported as structured metadata. Recruit CRM has no bundle or onboarding template package concept. We document the bundle structure in the migration inventory and flag that onboarding task templates and checklist automation must be rebuilt in Recruit CRM's workflow builder or as a separate onboarding checklist process. This item is documented for rebuild, not migrated as functional data.

Worknice assigns roles at the person level (Employee, Manager, Account owner, Contractor). Role assignments migrate as a direct custom field on the Candidate record. The role value is preserved verbatim so the customer's recruiting team can filter candidates by their most recent Worknice role during the transition period.

Worknice's Connections feature maps individual People records to external systems such as ATS platforms, payroll providers, and timesheet tools via per-person integration IDs. These external references are specific to Worknice's integration broker and have no counterpart in Recruit CRM. We exclude these records from the migration set entirely and flag in the migration inventory that all downstream integrations (payroll, timesheet, HRIS) must be re-established in Recruit CRM or replaced with new integration connections after go-live.

Time tracking entries (available on Worknice Essential plan) are exported per person including hours, dates, and time category where this data exists. Recruit CRM does not have a native time tracking module. We map time entry summaries to structured notes on the Candidate record or flag them for export as a separate CSV for the customer's finance or operations team to ingest into their preferred time tracking system. Active time tracking integrations require reconfiguration in Recruit CRM's integration settings post-migration.