HRMS migration

Migrate from Worknice to Crelate

Field-level mapping, validation, and rollback between Worknice and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.

Worknice logo

Worknice

Source

Crelate

Destination

Crelate logo

Compatibility

92%

11 of 12

objects map 1:1 between Worknice and Crelate.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Worknice logo

Worknice

What's pushing teams away

  • Some customers outgrow Worknice as they scale beyond 200 employees and require more granular role-based access controls across departments and legal entities.
  • Users requesting stronger mobile app functionality have cited limited mobile UX as a friction point when HR tasks need to be completed on the go.
  • Organizations needing deep payroll engine capabilities rather than payroll integrations find the platform's reliance on third-party payroll connections limiting.
  • Some teams report that advanced workflow automation features available in enterprise HR platforms are more limited in Worknice's tiered offering.

Choosing

Crelate logo

Crelate

What's pulling them in

  • Affordable per-seat pricing with transparent tiers makes Crelate accessible for small-to-mid staffing firms evaluating ATS platforms for the first time.
  • Fast implementation reported by customers—some describe getting live in a matter of minutes with support team assistance.
  • Unified ATS + CRM in a single product eliminates the need to buy and synchronize separate recruiting and sales tools.
  • Flexible custom fields across Contacts, Companies, and Opportunities allow recruiting teams to capture firm-specific data without developer involvement.
  • Positive reviews highlight the product's intuitive interface and functional breadth for teams that need recruiting workflows without enterprise overhead.

Object mapping

How Worknice objects map to Crelate

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

maps to

Crelate

Contact or Candidate

1:1
Fully supported

Worknice 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

maps to

Crelate

Contact (custom fields) or Job

1:1
Fully supported

Worknice 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

maps to

Crelate

Attachment to Contact

1:1
Mapping required

Worknice 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

maps to

Crelate

External documentation (no native equivalent)

1:1
Mapping required

Worknice 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

maps to

Crelate

External documentation (no native equivalent)

1:1
Mapping required

Worknice 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

maps to

Crelate

External documentation (no native equivalent)

1:1
Mapping required

Worknice 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

maps to

Crelate

Crelate task templates or workflow

lossy
Mapping required

Worknice 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

maps to

Crelate

External documentation (no native equivalent)

1:1
Mapping required

Worknice 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

maps to

Crelate

Contact (custom fields)

1:1
Fully supported

Worknice 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

maps to

Crelate

Task or Note (no native equivalent)

1:1
Mapping required

Time 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

maps to

Crelate

Not migrated

1:1
Not supported

Worknice 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

maps to

Crelate

User

1:1
Fully supported

Worknice 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.

Gotchas + challenges

What specifically takes care here

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 logo

Worknice gotchas

Medium

Minimum annual spend creates migration lock-in

High

No publicly documented REST API for bulk export

Medium

Position bundles do not migrate as structured bundles

Medium

Leave accrual methods require manual reconciliation

Low

Integration connections are person-level and non-transferable

Crelate logo

Crelate gotchas

High

120 req/min API rate limit throttles bulk migrations

High

20 custom field per-entity cap forces data model decisions

Medium

15,000-record export ceiling on single operations

Medium

Sequences and automation workflows do not migrate

Low

API key is a querystring parameter, not a header

Pair-specific challenges

  • Worknice has no public API — extraction relies on CSV exports from the admin UI

    Worknice does not publish a REST API for programmatic data extraction. All source data must be pulled through Worknice's built-in CSV export via the admin data tables. Large organizations may need to batch exports by entity (People, Leave, Reviews) or date range to stay within export size limits. We coordinate with the customer's Worknice admin during scoping to extract all required entities, validate row counts, and flag any data that cannot be exported through the standard UI tool. If the customer has data stored in archived or inactive Worknice accounts, those exports require separate admin access and may not be batched with active account exports.

  • Leave balances, reviews, and goals have no Crelate destination and require manual re-entry

    Worknice's HRMS data model includes leave balances, performance reviews, goals, OKRs, surveys, and engagement feedback that have no native equivalent in Crelate's ATS schema. We export these as structured CSV inventories, but the records cannot be loaded as functional objects in Crelate. The customer must decide during scoping whether to re-enter summary data manually (for compliance or HR audit purposes) or abandon the records as an HRMS migration rather than a recruiting migration. We document the scope of this gap in the migration handoff and include a data dictionary for each exported entity.

  • Bundle configurations require manual rebuild as Crelate task templates

    Worknice Bundles group onboarding task templates, document templates, and review forms into reusable configurations assigned to Positions or People. Crelate has no bundle-equivalent object. We export bundle names and associated template types as structured metadata, but the customer must manually rebuild bundle logic as task templates or workflow rules in Crelate's task management and workflow builder post-migration. This is a documented rebuild scope with a configuration inventory delivered at handoff, not an automated migration. Teams that rely heavily on bundle automation for onboarding should expect additional post-migration configuration time.

  • Integration connections and MYOB payroll links are not transferable

    Worknice's Connections feature maps individual People records to external systems including ATS integrations, payroll providers, and timesheet tools. These integration IDs are specific to Worknice's integration broker and have no counterpart in Crelate or any other ATS. MYOB payroll connections in particular require re-configuration from scratch in Crelate's integrations settings or through a separate payroll tool. We exclude all connection records from the migration set and flag that the customer's IT or HR admin must re-establish integrations post-go-live. Any active payroll sync running at cutover must be paused before migration to avoid data divergence between systems.

Migration approach

Six steps for a successful Worknice to Crelate data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Worknice logo

Worknice

Source

Strengths

  • Consolidated employee lifecycle covering onboarding through performance in one platform
  • Essential plan includes time tracking, task management, and document sharing at a low per-employee price
  • Native integrations with ANZ payroll systems (MYOB) and common ATS platforms
  • Award-winning customer support with help documentation and training programs
  • Annual billing model keeps total cost predictable for budget planning

Weaknesses

  • Minimum annual commitment of $6,000 locks organizations into a 12-month agreement
  • No public API documentation found in research — integration and migration rely on Worknice's managed data import tools
  • Limited mobile app functionality compared to modern HR platforms
  • No free tier or low-cost trial for organizations under 50 employees to evaluate fit
  • Advanced workflow automation features are constrained relative to enterprise HR suites
Crelate logo

Crelate

Destination

Strengths

  • Unified ATS and CRM in a single platform reduces data synchronization overhead for recruiting teams.
  • Fast setup with guided implementation reported as a significant time saver for small teams.
  • Transparent per-seat pricing without surprise fees at the base tier.
  • Flexible custom field configuration across core objects without developer dependency.
  • Export capability supports up to 15,000 records per operation for Contacts, Companies, and Opportunities.

Weaknesses

  • API rate limit of 120 requests per minute restricts bulk migration throughput.
  • Custom field cap of 20 per entity requires field consolidation for complex recruiting schemas.
  • All advanced features (Activities, Activity Forms, Core Record Field customization) are tier-gated add-ons.
  • Customer service responsiveness receives consistent negative feedback in reviews.
  • Resume parsing quality trails competitors and generates support requests.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Worknice and Crelate.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Worknice: Not publicly documented.

  • Data volume sensitivity

    B

    Worknice doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Worknice to Crelate migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Worknice to Crelate data migrations

Answers to the questions buyers ask most during Worknice to Crelate migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Worknice to Crelate migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for organizations with fewer than 1,000 People records and no complex leave or performance data to document. Migrations with larger People counts (over 5,000), document attachment re-hosting, multiple bundle configurations to inventory, and parallel leave balance documentation for compliance move to seven to ten weeks. The primary driver of timeline variance is Worknice's lack of a public API: all source extraction relies on coordinating CSV exports with the customer's Worknice admin, which adds a dependency that API-based migrations do not have.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Worknice.
Land in Crelate, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day