Migrate from Workday HCM to Crelate

Workday Workers (employees, contractors, contingent workers) map to Crelate People records. We extract the primary legal name, preferred name, contact information, and employment type. Worker's effective-dated job history (multiple job changes, promotions, transfers) requires flattening: only the current or most recent job assignment migrates as the active record in Crelate because Crelate does not maintain temporal employment history semantics. Historical job data that must be preserved is appended as a structured note block on the Person record.

Workday Organizations in a hierarchical graph (Supervisory Organizations, Cost Centers, Business Units, Regions) map to Crelate Companies. We collapse the multi-level org tree into a flat Crelate Company record, preserving the top-level and second-level org names as Company fields. If the customer requires org hierarchy visibility in Crelate, we create Crelate Companies for each Workday org node and link them via a self-referential Company relationship or a custom parent_company__c field. Cost center codes migrate as a custom text field on the Company record.

Workday Positions (the organizational role boxes independent of the person holding them) map to Crelate Job Orders. Position title, working hours, and location migrate to the Job Order's title, employment type, and location fields. We exclude position-specific attributes that only make sense within Workday's position-based staffing model, such as supervisory or in-scope position relationships. Job Order status is set to match the position's active/inactive flag.

Workday Job Profiles define the qualifications, skills, competencies, and experience required for a Position. We map profile attributes to Crelate Skills (as comma-separated text or Crelate's native skills taxonomy) and to the Job Order's requirements text block. Crelate does not have a structured competencies model, so profile sub-sections migrate as free-text formatted into the requirements field. Job Profiles without an active Position are not migrated as standalone records.

Workday Supervisory Organizations define manager-to-worker chains and reporting hierarchy. We extract the supervisor-worker relationship and map it to the Crelate Person record's reporting_to field by resolving the supervisor's Worker ID to the corresponding Crelate Person. If the supervisor is not a Crelate user, the reporting relationship is stored as a text field until the customer provisions the manager as a Crelate user.

Workday compensation entries (pay changes, bonuses, stock grants) are effective-dated and tied to a Worker. Crelate has no compensation module. We flag this object as out of scope and note it in the written migration inventory. If the customer requires placement compensation tracking, we map the most recent base salary as a static custom currency field on the Crelate Person record, with a clear field label indicating it is a snapshot rather than a history.

Workday Benefits Enrollment records (plan elections, coverage levels, dependents) have no Crelate equivalent. Crelate is a recruiting ATS, not an HRMS. We exclude this object from migration scope and document it in the written inventory. Organizations that need benefits data in Crelate must note that Crelate does not have a benefits schema; any such tracking requires a custom object with explicit field design.

Workday leave accruals, current balances, and pending absence requests are excluded from migration scope. Crelate has no absence management module. We document this in the written inventory with a recommendation that the customer's HR admin maintain absence tracking in a separate system or a Crelate custom object if the customer chooses to build one post-migration.

Workday payroll summaries (gross pay, deductions, taxes, net pay, pay period registers) require payroll-specific API credentials and have no Crelate equivalent. Crelate stores placement fee and commission information on placements, not employee payroll. We exclude payroll data from the migration scope entirely and flag that payroll data migration requires a separate engagement with a payroll-focused data service.

Workday Custom Objects extend the delivered Worker and Position schema with tenant-specific fields. Crelate supports custom fields (Text, Number, Money, Date, and other types) on Person and Company records. We discover every Workday Custom Object via WQL API or tenant report schema before migration, map each custom field to a Crelate custom field of equivalent type, and pre-create the destination fields before data load. Custom Objects with complex multi-level relationships that cannot be represented as flat fields on a Crelate record are documented as requiring post-migration admin review.

Workday Worker documents (offer letters, contracts, performance reviews) attach as binary blobs to the Worker record. Crelate supports file attachments on Person records. We export each document with its original filename, MIME type, and document category, then attach it to the corresponding Crelate Person record. Document category labels migrate as a Crelate custom field (document_type__c) for filtering. Large document archives exceeding 1 GB total require pre-scoping for export and upload timing.

If the customer uses Workday Recruiting, candidate applications and requisitions map to Crelate Candidates and Job Orders. Application status (applied, screening, interview, offer, hired, rejected) maps to the corresponding Crelate pipeline stage. Workday requisition approval chains do not migrate; we document them for the customer's admin to rebuild in Crelate's workflow automation.