HRMS migration
Field-level mapping, validation, and rollback between Worknice and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.
Worknice
Source
Crelate
Destination
Compatibility
11 of 12
objects map 1:1 between Worknice and Crelate.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Worknice and Crelate serve fundamentally different use cases. Worknice is an Australian-hosted HRMS covering the full employee lifecycle from onboarding through performance reviews and leave management. Crelate is a recruiting ATS and agency CRM built for staffing firms, placement agencies, and in-house talent acquisition teams to manage candidates, job orders, and client relationships. Migrating between them is a partial record migration: People and Positions from Worknice map to Crelate's Contact and Candidate records, but performance reviews, leave balances, goals, OKRs, surveys, and bundle templates have no native Crelate equivalent and are exported as flat data for manual re-entry or abandonment. Worknice has no documented public API, so all source extraction uses Worknice's built-in CSV export via the admin data tables. We do not migrate workflows, automations, or integration connections as code. We deliver a written inventory of Worknice bundle configurations and workflow rules requiring manual rebuild in Crelate's task templates and workflow builder post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Worknice object lands in Crelate, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Worknice
People
Crelate
Contact or Candidate
1:1Worknice People records (employees, contractors, managers, account owners) map to Crelate Contact records at minimum. If the Worknice People include active candidates in a hiring pipeline, those records map to Crelate Candidate. Role assignments (Employee, Contractor, Manager) from Worknice become custom fields on the Crelate Contact record. Position and pay details attach as structured fields. We extract via Worknice's People data table export and import via Crelate's bulk import tool or REST API, resolving any required Crelate fields (Name, Email, Phone) as the dedupe key.
Worknice
Positions
Crelate
Contact (custom fields) or Job
1:1Worknice Position records define job titles, hierarchies, and reporting relationships. We export Position name, department, and reporting manager as structured fields and attach them to the mapped Contact record in Crelate as custom fields. If the customer uses Crelate's Job object to represent open roles, Worknice Positions that correspond to active openings map to Crelate Job records. Position bundle assignments are exported as metadata and attached to the relevant Position record, not as structured bundle objects.
Worknice
Documents / Paperwork
Crelate
Attachment to Contact
1:1Worknice stores compliance documents, contracts, and onboarding paperwork per People record. We export documents as binary blobs and recreate the attachment relationship in Crelate by linking each document to the corresponding Contact record. File naming conventions may change during export; we document original Worknice file names and their corresponding Crelate attachment IDs in the migration notes. Binary blob attachments migrate as-is; document content is not parsed or restructured.
Worknice
Leave balances
Crelate
External documentation (no native equivalent)
1:1Worknice leave entitlements and accrual balances have no native equivalent in Crelate's ATS schema. We export leave type, current balance, accrual method, and last balance update date as structured fields and deliver them as a CSV inventory to the customer. The customer's HR team re-enters leave balances manually in Crelate's Notes or a custom field, or maintains them in a separate leave management tool. We document the accrual method per leave type so the HR team can configure equivalent rules in any third-party leave tool they adopt.
Worknice
Performance Reviews
Crelate
External documentation (no native equivalent)
1:1Worknice performance reviews include reviewer relationships, form question responses, completion status, and review cycle metadata. Crelate has no native performance review module. We export review records as structured data (reviewer, reviewee, form responses, rating, date, status) and deliver them as a CSV inventory. For organizations that need to preserve review history for compliance or HR records, we recommend re-entering summary data manually or retaining the export as an HR document archive. Custom review form fields require field-level mapping to the export CSV.
Worknice
Goals and OKRs
Crelate
External documentation (no native equivalent)
1:1Worknice supports company-level OKRs and employee goals with parent-child alignment hierarchies. We export goal titles, descriptions, progress percentages, alignment relationships, and owner assignments. Crelate's ATS schema has no goals or OKR module. We deliver goal data as a structured CSV inventory with parent-child relationship preserved as separate fields, for the customer's HR or strategy team to re-enter in a dedicated goals platform or as notes on the relevant Contact record.
Worknice
Bundles and templates
Crelate
Crelate task templates or workflow
lossyWorknice Bundles group onboarding task templates, document templates, and review forms assigned to Positions or People. Crelate has no bundle-equivalent object. We export bundle names and associated template types as structured metadata and deliver them as a configuration inventory document. The customer maps bundle task items to Crelate task templates or workflow rules manually post-migration. This is a manual rebuild scope documented in our handoff deliverable, not an automated migration.
Worknice
Surveys and feedback
Crelate
External documentation (no native equivalent)
1:1Worknice continuous feedback and engagement survey responses are exportable per person. Crelate has no native survey or feedback module. We export survey response records as structured CSV with respondent, survey name, question, response, and date fields. Survey design and question structures are documented separately for the customer's HR team to re-create in a dedicated survey tool (Culture Amp, Lattice, or similar) post-migration.
Worknice
Roles
Crelate
Contact (custom fields)
1:1Worknice assigns roles at the person level (Employee, Manager, Contractor, Account owner). We preserve role assignments as direct values in custom fields on the Crelate Contact record. Role assignments are extracted from the People data table export as a flat field and mapped to a Crelate custom field of picklist or text type.
Worknice
Time tracking entries
Crelate
Task or Note (no native equivalent)
1:1Time tracking entries in Worknice (available on the Essential plan) are exported as records per person with hours, dates, and time category. Crelate has no native time tracking module. We export time entries as structured CSV and deliver them as an inventory for the customer's HR team to re-enter in a dedicated time tracking tool or as notes on the relevant Contact record. If Crelate's Task object is used for billing or client work tracking, time entries may map to Task with hours and date preserved.
Worknice
Integration connections
Crelate
Not migrated
1:1Worknice maps per-person connections to external systems (ATS, payroll, timesheet integrations) via its Connections feature. These integration IDs are external references specific to Worknice's integration broker and have no counterpart in Crelate. We exclude these records from the migration set entirely and flag during scoping that the customer must re-establish integration connections in Crelate's integrations settings post-go-live. MYOB payroll connections require re-configuration in Crelate's integrations or as a separate payroll tool.
Worknice
Owner
Crelate
User
1:1Worknice Owners (employees with account-level roles) map to Crelate User records by email match. We extract all distinct Owner values from People and Engagement records and match against the Crelate User table by email. Any Worknice Owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes.
| Worknice | Crelate | Compatibility | |
|---|---|---|---|
| People | Contact or Candidate1:1 | Fully supported | |
| Positions | Contact (custom fields) or Job1:1 | Fully supported | |
| Documents / Paperwork | Attachment to Contact1:1 | Mapping required | |
| Leave balances | External documentation (no native equivalent)1:1 | Mapping required | |
| Performance Reviews | External documentation (no native equivalent)1:1 | Mapping required | |
| Goals and OKRs | External documentation (no native equivalent)1:1 | Mapping required | |
| Bundles and templates | Crelate task templates or workflowlossy | Mapping required | |
| Surveys and feedback | External documentation (no native equivalent)1:1 | Mapping required | |
| Roles | Contact (custom fields)1:1 | Fully supported | |
| Time tracking entries | Task or Note (no native equivalent)1:1 | Mapping required | |
| Integration connections | Not migrated1:1 | Not supported | |
| Owner | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Worknice gotchas
Minimum annual spend creates migration lock-in
No publicly documented REST API for bulk export
Position bundles do not migrate as structured bundles
Leave accrual methods require manual reconciliation
Integration connections are person-level and non-transferable
Crelate gotchas
120 req/min API rate limit throttles bulk migrations
20 custom field per-entity cap forces data model decisions
15,000-record export ceiling on single operations
Sequences and automation workflows do not migrate
API key is a querystring parameter, not a header
Pair-specific challenges
Migration approach
Discovery and export coordination
We audit the Worknice account scope: People count by role (employee, contractor, manager), active Positions, Leave types and balances, performance review cycles, goal and OKR sets, survey records, document attachment counts, and bundle configurations. We coordinate with the customer's Worknice admin to extract all entities via Worknice's built-in CSV data tables, batched by entity and date range where export size limits apply. We validate row counts against the customer's internal headcount reports to confirm export completeness before any transformation work begins. We also confirm which Worknice data represents active recruiting candidates (versus employed staff) so that the correct split to Crelate Candidate versus Contact is applied during mapping.
Crelate schema design and custom field provisioning
We design the destination schema in Crelate based on the Worknice entities confirmed during discovery. This includes provisioning custom fields on the Contact object for Worknice Role, Position, Department, Reporting Manager, and employment type. If Crelate's Candidate object is used for active recruiting records, we design the Candidate field mapping parallel to Contact. We configure Crelate's Custom Forms settings to expose the required fields and verify that custom field types (text, picklist, date, number) match the source data format. Crelate's field mapping documentation is referenced to ensure custom fields are accessible via both the UI and REST API for bulk import.
Data extraction, validation, and transformation
We ingest the Worknice CSV exports and run a structured transformation pass: deduplicate People records by email, split by role into Contact and Candidate maps, extract Position metadata and attach to the relevant Contact record, transform leave balance records into a flat inventory CSV, transform performance review records into a review inventory CSV with reviewer and form response fields. We flag any Worknice records with missing required fields (Name, Email) for the customer's admin to resolve before import. Documents are extracted as binary blobs with original filenames preserved in a manifest spreadsheet linking each blob to its Crelate attachment target.
Sandbox migration and reconciliation
We run a full migration into Crelate's staging or test environment using the extracted and transformed data. The customer's recruiting or HR lead reconciles record counts (Contacts in, Candidates in, Jobs in), spot-checks 25-50 random records against the Worknice source, and validates that custom field values match the original Worknice data. Document attachments are spot-checked for readability. Leave balance and performance review inventories are reviewed for completeness. Any mapping corrections or data quality issues are resolved before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Users (reconciled against Crelate User table by email), Contacts (primary People migration), Candidates (active recruiting records), Jobs (if Worknice Positions map to open job orders), custom fields populated, document attachments linked, and leave and review inventories delivered as CSVs. Integration connection records and bundle configurations are excluded from import and documented in the handoff. Any records modified in Worknice during the migration window are delta-migrated before cutover.
Cutover, validation, and workflow rebuild handoff
We freeze Worknice writes during cutover and run a final delta migration of any records modified during the window. Crelate becomes the system of record for recruiting and candidate data. We deliver the bundle configuration inventory, workflow rule rebuild guide, and integration re-connection checklist to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild Worknice workflows, bundles, or automations as Crelate task templates or workflows inside the migration scope; that is a separate configuration engagement or an internal admin task.
Platform deep dives
Worknice
Source
Strengths
Weaknesses
Crelate
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Worknice and Crelate.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Worknice: Not publicly documented.
Data volume sensitivity
Worknice doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Worknice to Crelate migration scoping. Not seeing yours? Book a call.
Walk through your Worknice to Crelate migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Worknice
Other ways to arrive at Crelate
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.