HRMS migration
Field-level mapping, validation, and rollback between Deltek Talent Management and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.
Deltek Talent Management
Source
Crelate
Destination
Compatibility
5 of 12
objects map 1:1 between Deltek Talent Management and Crelate.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Deltek Talent Management and Crelate serve different layers of the talent lifecycle. Deltek is a full-suite HRMS covering recruiting, onboarding, performance management, compensation, and learning for A&E and professional services firms; Crelate is a recruiting-focused ATS and talent CRM that tracks candidates, jobs, and pipeline activity. The migration scope is therefore constrained to the recruiting layer: Candidates map to Crelate Persons, Requisitions map to Crelate Jobs, and recruiting activities (notes, calls, emails) map to Crelate Activities attached to Persons and Jobs. We flag that Deltek Employees, Performance Reviews, Compensation History, Onboarding records, and Learning Enrollments have no direct Crelate equivalent and are either omitted from migration scope or delivered as a supplemental data inventory for the customer's admin to handle manually. The Vantagepoint integration creates a high-risk dependency: if the customer is also retiring Vantagepoint, employee records sourced from that ERP must be reconciled against Deltek Talent Management records before any candidate migration begins to avoid duplicate Person records in Crelate.
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 Deltek Talent Management 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.
Deltek Talent Management
Candidate
Crelate
Person
1:1Deltek Candidates map directly to Crelate Persons. We extract the candidate's full name, email, phone, address, source, application status, and any status-change history from Deltek's candidate record. The candidate status pipeline in Deltek (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Crelate's pipeline stage values, which we configure before migration. Candidate notes and attachments migrate as Crelate Activities and linked Documents respectively. Custom fields on the Deltek Candidate record (managed via the Additional Information tab with text, radio button, and multi-select types) map to Crelate user-defined fields, which we create during schema setup.
Deltek Talent Management
Job Requisition
Crelate
Job
1:1Deltek Job Requisitions map to Crelate Jobs. The requisition status (Draft, Open, On Hold, Filled, Cancelled) maps to Crelate Job status. Department and location assignments from Deltek requisitions carry over as Crelate Job fields or tags. Candidates linked to a Requisition in Deltek create Candidate-to-Job associations in Crelate via the Crelate Job-Person relationship. Known performance issues on Deltek's Requisition page (which retrieves the form twice per load) do not affect migration; we pull data via API or direct database export rather than UI-based export.
Deltek Talent Management
Employee
Crelate
Person (limited)
lossyDeltek Employees represent the HRMS core record and include hire date, department, job title, compensation, manager assignment, and performance history. Crelate is an ATS and does not store employment records. We migrate the subset of Employee data relevant to recruiting: name, email, phone, and department. For terminated employees who previously sourced candidates or requisitions, we create Person records with an Inactive status in Crelate so that historical attribution (who created the requisition, who was the hiring manager) does not break. Full employment history, compensation rows, and performance data are not migrated to Crelate; we deliver a written inventory of these records for the customer's HR team to handle separately.
Deltek Talent Management
Onboarding Record
Crelate
Activity / Task (limited)
lossyDeltek Onboarding records store document completion status, checklist items, and the assigned Hiring Manager. Crelate does not have a native onboarding module. We migrate onboarding record metadata (completion percentage, checklist item names, document names) as Crelate Activity records attached to the corresponding Person record. The Hiring Manager assignment migrates as a tag or custom field on the Activity rather than a native owner assignment. The documented bug where notifications route to terminated Hiring Managers is handled by flagging any onboarding record where the assigned manager has a termination date and noting it in the migration report for manual verification.
Deltek Talent Management
Hiring Manager Assignment
Crelate
Recruiter / Owner Tag
1:1Deltek assigns a Hiring Manager to Requisitions and Candidates. Crelate uses a Recruiter/Owner field on Jobs and a Hiring Manager tag on Persons. We resolve Deltek Hiring Manager assignments by matching the manager's email to a Crelate User record (created from the Deltek Employee subset above). Where the Hiring Manager is terminated in Deltek and has no active Crelate User, we assign the record to the customer's designated migration admin in Crelate and flag it for reassignment post-migration.
Deltek Talent Management
Performance Review
Crelate
Not Migrated (written inventory)
lossyDeltek Performance Reviews include project-based appraisals, configurable 9-Box rating data, goal-setting, and continuous feedback. Crelate is a recruiting ATS and has no performance management module. Performance data is outside Crelate's schema and cannot be meaningfully mapped. We export the full review history from Deltek as a structured CSV inventory (review cycle, ratings, goals, comments, reviewer) and deliver it to the customer's HR admin for manual handling in their chosen performance management destination. No performance data moves into Crelate.
Deltek Talent Management
Compensation History
Crelate
Not Migrated (written inventory)
lossyDeltek Compensation History stores effective-dated salary rows, bonus amounts, equity details, pay grades, and the Rate Type field (Salaried vs Hourly, introduced in 18.1). Crelate does not store compensation data. We export the full compensation timeline from Deltek as a structured CSV inventory with Employee ID, effective date, salary, bonus, equity, pay grade, and Rate Type. This inventory is delivered to the customer's HR admin. Note that if the customer is also retiring Vantagepoint, compensation data should be migrated to the replacement ERP rather than Crelate.
Deltek Talent Management
Learning Enrollment
Crelate
Not Migrated (written inventory)
lossyDeltek Learning records include course enrollment, completion status, scores, certification tracking, and external certifications that sync to Vantagepoint for resource planning. Crelate is a recruiting ATS and has no LMS module. We export the full learning history as a structured CSV inventory (employee, course, enrollment date, completion date, score, certification expiry) and deliver it to the customer's HR admin for manual handling. The external certification sync to Vantagepoint is discontinued at migration; if certifications affect resource planning, the customer should migrate learning data to their replacement ERP or a dedicated LMS.
Deltek Talent Management
Custom Fields
Crelate
User-Defined Fields
lossyDeltek supports custom fields on most core objects via the Additional Information tab with field types including text, radio button, and multi-select list. We export all custom field data alongside standard fields during the Deltek extraction. In Crelate, we create matching user-defined fields before migration, mapping Deltek text fields to Crelate text fields, radio button options to Crelate single-select fields, and multi-select lists to Crelate multi-select fields. Custom field values are then imported as part of the standard object migration.
Deltek Talent Management
Location
Crelate
Location / Tag
1:1Deltek Locations store office and geographic data used in requisition placement and org structure. Locations export cleanly from Deltek and map to Crelate Location fields on Jobs or as Tags on Persons, depending on how the customer uses location data. We recommend using Crelate Tags for location to allow flexible multi-location tagging on both Jobs and Persons.
Deltek Talent Management
Document / Attachment
Crelate
Document
1:1Deltek stores onboarding documents, employee files, and uploaded attachments. We export document metadata (file name, document type, upload date, associated record) and binary files. In Crelate, documents attach to Persons and Jobs via the native document link feature. File storage limits and version retention settings differ between Deltek and Crelate; we flag any attachments exceeding Crelate's size limits during the migration audit for the customer to decide whether to archive or migrate them.
Deltek Talent Management
Groups and Permissions
Crelate
Not Migrated (role mapping)
lossyDeltek group-based permissions control access to Talent Management functions. Crelate uses a role-based permission model with Admin, Standard, and Limited roles. Deltek groups do not map 1:1 to Crelate roles. We deliver a written role-mapping matrix that lists each Deltek group, its permissions scope, and the recommended Crelate role or permission-set configuration. The customer's admin configures Crelate permissions post-migration based on this inventory.
| Deltek Talent Management | Crelate | Compatibility | |
|---|---|---|---|
| Candidate | Person1:1 | Fully supported | |
| Job Requisition | Job1:1 | Fully supported | |
| Employee | Person (limited)lossy | Fully supported | |
| Onboarding Record | Activity / Task (limited)lossy | Fully supported | |
| Hiring Manager Assignment | Recruiter / Owner Tag1:1 | Fully supported | |
| Performance Review | Not Migrated (written inventory)lossy | Fully supported | |
| Compensation History | Not Migrated (written inventory)lossy | Mapping required | |
| Learning Enrollment | Not Migrated (written inventory)lossy | Fully supported | |
| Custom Fields | User-Defined Fieldslossy | Mapping required | |
| Location | Location / Tag1:1 | Fully supported | |
| Document / Attachment | Document1:1 | Fully supported | |
| Groups and Permissions | Not Migrated (role mapping)lossy | Mapping required |
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.
Deltek Talent Management gotchas
Vantagepoint integration creates cross-system employee dependencies
Master token API authentication is site-wide and non-revocable per integration
Onboarding document status ties to terminated Hiring Manager records
Export runs extract all records with no incremental option
Known issue with deactivated candidate status appearing in bulk operations
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 Vantagepoint dependency audit
We audit the source Deltek Talent Management environment across modules in use (Talent Acquisition, Performance, Development, Compensation, Learning), active integrations, custom field count per object, and record volumes for Candidates, Requisitions, Employees, Onboarding records, Performance Reviews, Compensation History, and Learning Enrollments. We simultaneously identify whether Vantagepoint is being retired in parallel and audit the integration log for employee record sync history. The discovery output is a written migration scope that explicitly lists what migrates to Crelate, what migrates as a written inventory, and what requires a separate tool decision. We also confirm Crelate tenant access and user seat count.
Crelate schema setup and custom field creation
Before any data moves, we create the Crelate user-defined fields that correspond to Deltek custom fields on Candidate and Job records. We configure pipeline stage values in Crelate to match Deltek's candidate status pipeline (Applied, Screening, Interview, Offer, Hired, Rejected) and the requisition status values. We set up Crelate Locations or Tags for location data. We create Crelate Users for the Employee subset (name, email, department) that will serve as Hiring Manager and Recruiter assignments on Jobs and Persons. The Crelate admin grants the migration user API access and field-level permissions.
Vantagepoint employee deduplication
If the customer is retiring Vantagepoint alongside Talent Management, we extract the full Vantagepoint employee export and the full Deltek Talent Management employee export. We deduplicate by email and employee ID, identifying records that exist in both systems. The deduplicated Person records are created in Crelate first. All subsequent Deltek Candidate and Requisition records that reference a Hiring Manager or Recruiter use the deduplicated Crelate Person record as the owner or assignee. This step prevents the duplicate Person problem that occurs when the same employee exists in both source systems and both are migrated independently.
Sandbox migration and reconciliation
We run a full migration into Crelate using a sandbox or parallel environment with production-like data volumes. The customer's recruiting operations lead reconciles record counts (Candidates in, Persons out; Requisitions in, Jobs out), spot-checks 25-50 random Person and Job records against the Deltek source, and verifies that custom field values, pipeline stage assignments, and hiring manager tags are correct. Any mapping corrections are documented and applied before the production migration begins. Activity record counts (notes, emails, calls) are reconciled at this stage using Bulk API export logs.
Production migration in dependency order
We run production migration in dependency order: Crelate Users and Locations (lookup dependencies), Persons (from Deltek Candidates with custom fields), Jobs (from Deltek Requisitions with linked Persons), Activities (notes, emails, calls from Deltek engagement records), and Documents (from Deltek attachments). Onboarding metadata migrates as Activity records with a flagged note for records where the Hiring Manager is terminated. The Vantagepoint employee deduplication results are referenced throughout to resolve Hiring Manager and Recruiter assignments. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, data inventory delivery, and admin handoff
We freeze Deltek writes during cutover, run a final delta migration of any records modified during the migration window, then set Crelate as the system of record for recruiting. We deliver the written data inventories for Performance Reviews, Compensation History, and Learning Enrollments as structured CSV exports with field-level documentation. We deliver the role-mapping matrix for Deltek groups to Crelate roles. We support a one-week hypercare window where we resolve any reconciliation issues. Workflows, automations, and Deltek-specific onboarding task templates do not migrate; we document them in a separate rebuild guide for the customer's admin.
Platform deep dives
Deltek Talent Management
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 Deltek Talent Management 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
Deltek Talent Management: Not publicly documented in available documentation.
Data volume sensitivity
Deltek Talent Management 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 Deltek Talent Management to Crelate migration scoping. Not seeing yours? Book a call.
Walk through your Deltek Talent Management 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 Deltek Talent Management
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.