HRMS migration
Field-level mapping, validation, and rollback between EMP Trust HR and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.
EMP Trust HR
Source
Crelate
Destination
Compatibility
10 of 12
objects map 1:1 between EMP Trust HR and Crelate.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from EMP Trust HR to Crelate is a schema reshape, not a record copy. EMP Trust HR structures its data around a Hire record driving the New Hire Portal, Forms, I-9 compliance records, and onboarding task assignments. Crelate is an ATS-first platform with onboarding, talent management, and compliance document storage built for recruiting teams and HR departments at staffing agencies and mid-market companies. We extract employee profiles, I-9 Section 1 and Section 2 records with E-Verify case status, completed onboarding form definitions and responses with e-signature metadata, training completion flags, and benefits enrollment snapshots from EMP Trust HR; then we map them to Crelate's Contact, Candidate, Onboarding, Document, and Custom Fields structures. I-9 e-signature audit trails stored in EMP Trust HR's proprietary format are extracted, wrapped in a standard envelope schema, and written as tagged document records in Crelate. Integration configurations, ATS connector settings, and payroll sync schedules do not migrate; we deliver a written inventory of every active connector for the customer's admin to re-establish in Crelate 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 EMP Trust HR 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.
EMP Trust HR
Employee
Crelate
Contact (Person) or Candidate
1:1EMP Trust HR Employee records map to Crelate Contacts representing the employed individuals. The employee profile fields (name, email, phone, address, employment type, location assignment) migrate to Crelate Contact fields. We resolve the department and job title from EMP Trust HR's location and title assignment into Crelate's department and job_category fields. If the employee originated from an ATS candidate via Greenhouse or Lever integration in EMP Trust HR, we document the original candidate fields that were not mapped by the integration for reconciliation against Crelate's candidate source data.
EMP Trust HR
I-9 Record (Section 1 and Section 2)
Crelate
Document (tagged I-9)
1:1I-9 Section 1 (employee self-completion) and Section 2 (employer or third-party notary agent verification) records migrate as tagged Document records in Crelate. EMP Trust HR stores these as compliance artefacts within the Forms module, not as structured fields in the export API. We extract the form completion record, reconstruct the e-signature envelope (signer ID, timestamp, IP address, certificate hash) from EMP Trust HR's audit trail metadata, and write it as a tagged I-9 document with a compliance flag in Crelate. We flag any I-9 records where the e-signature certificate chain cannot be fully reconstructed so the customer can plan for re-signing if required.
EMP Trust HR
E-Verify Status
Crelate
Custom Field (E-Verify_Case_Number, E-Verify_Status)
lossyE-Verify case status codes (Verified, Tentative Nonconfirmation, DHS/DOJ Query) from EMP Trust HR migrate to Crelate custom fields on the Contact record. We preserve the E-Verify case number, verification date, and USCIS response as structured fields alongside the I-9 document. If Tentative Nonconfirmation records exist, we flag them with a compliance-warning status for the customer's HR team to resolve post-migration.
EMP Trust HR
New Hire Portal
Crelate
Onboarding Workflow
1:1EMP Trust HR New Hire Portal instances migrate to Crelate Onboarding workflows. We extract the portal configuration (branding, welcome message, task set, completion state) and map it to Crelate's onboarding checklist and task list structures. Portal completion status (started, in-progress, completed) migrates as onboarding progress. Any incomplete portals at migration time are flagged with a status of 'in-progress at migration' so the customer's Crelate admin can resume the onboarding sequence.
EMP Trust HR
Task Assignments
Crelate
Onboarding Tasks or Activity Tasks
1:manyEMP Trust HR task assignments (to new hires, managers, HR staff, IT) split into Crelate onboarding tasks scoped to the onboarding workflow and activity tasks on the Contact record for HR-manager action items. We preserve task status, due dates, assignees (resolved by email to Crelate users), and completion timestamps. Task hierarchy within EMP Trust HR onboarding packages is flattened into a sequential task list in Crelate.
EMP Trust HR
Forms (Onboarding Packages)
Crelate
Documents (tagged form)
1:1Completed EMP Trust HR onboarding forms (offer letters, NDAs, non-competes, policy acknowledgements, tax withholding, direct deposit, beneficiary forms) migrate as tagged Document records in Crelate. Form definitions (the template) are documented in the migration inventory; the completed responses with e-signature audit trails migrate as the document content. Form logic and conditional branching are not preserved; we flag every form with conditional logic for the customer's admin to rebuild in Crelate's form builder post-migration.
EMP Trust HR
Custom Forms
Crelate
Custom Fields and Documents
1:1Employer-defined custom forms migrate as Document records in Crelate with a custom field set capturing the form field responses. Custom form definitions with conditional logic are not preserved as executable forms; we deliver a written inventory of each custom form with its field structure, conditional rules, and response data for the customer's admin to rebuild in Crelate's form builder. E-signature metadata from custom forms is wrapped in the standard envelope schema.
EMP Trust HR
Training Records
Crelate
Training Module or Custom Fields on Contact
1:1Courses assigned via the EMP Trust HR new hire learning portal with completion flags, scores, and assignment timestamps migrate to Crelate's training module (if the customer's Crelate tier supports it) or to a structured set of custom fields on the Contact record (course name, completion date, score, status). We preserve the course assignment timestamp as the completion date for audit. Training course content (videos, documents) does not migrate; we deliver a course inventory document for the customer's L&D team to reload into Crelate's training module or a third-party LMS.
EMP Trust HR
Background Check Results
Crelate
Document (tagged background_check)
1:1Background check results sourced through EMP Trust HR's pre-built integrations (CastleBranch, AccurateBackground, BirdDogHR) migrate as tagged Document records in Crelate with a summary status field (cleared, pending, adverse action). Raw vendor report files (PDFs from the screening provider) migrate as attached documents. EMP Trust HR stores only the result summary; the raw report content depends on what the integration captured. We flag any records where the raw report file was not retained in the EMP Trust HR export for manual follow-up with the screening vendor.
EMP Trust HR
Benefits Enrollment Snapshot
Crelate
Custom Fields (Plan, Coverage, Dependents)
1:1Benefits selections captured during onboarding (plan choices, dependent information, beneficiary designations) migrate as a structured set of custom fields on the Contact record. EMP Trust HR stores these as enrollment snapshots at the time of onboarding completion, not as a live feed from a benefits carrier. Active ongoing benefits changes (life events, deduction updates) are not captured in the EMP Trust HR export and must be reconciled manually against the carrier's system at migration cutover. We flag all contacts with benefits data for the customer to confirm active coverage status with their benefits administrator before Crelate go-live.
EMP Trust HR
Integration Configurations (ADP, Workday, UKG)
Crelate
Not Migrated
1:1Pre-built integration connectors and related sync configurations do not migrate. EMP Trust HR does not export sync schedules, credential mappings, or webhook configurations. We deliver a written inventory of every active EMP Trust HR connector (ADP, Workday, UKG, Oracle, SAP, Greenhouse, Lever, background check providers) with the integration type, data flows, and destination endpoint for the customer's admin to re-establish in Crelate post-migration. Any ATS-triggered candidate-to-hire transitions are documented separately.
EMP Trust HR
ATS Candidate Records (via Greenhouse/Lever Integration)
Crelate
Candidate or Contact (source preserved)
1:1Candidates transitioned from Greenhouse or Lever to EMP Trust HR via the integration fire as new hire profiles in EMP Trust HR. Only fields mapped by the integration configuration are pushed into the employee record; original ATS candidate fields not included in the mapping are not available in EMP Trust HR. We document the integration field map during scoping and flag any candidate source fields that should be preserved from the original ATS export for manual reconciliation against Crelate's candidate import.
| EMP Trust HR | Crelate | Compatibility | |
|---|---|---|---|
| Employee | Contact (Person) or Candidate1:1 | Fully supported | |
| I-9 Record (Section 1 and Section 2) | Document (tagged I-9)1:1 | Fully supported | |
| E-Verify Status | Custom Field (E-Verify_Case_Number, E-Verify_Status)lossy | Fully supported | |
| New Hire Portal | Onboarding Workflow1:1 | Fully supported | |
| Task Assignments | Onboarding Tasks or Activity Tasks1:many | Fully supported | |
| Forms (Onboarding Packages) | Documents (tagged form)1:1 | Fully supported | |
| Custom Forms | Custom Fields and Documents1:1 | Mapping required | |
| Training Records | Training Module or Custom Fields on Contact1:1 | Fully supported | |
| Background Check Results | Document (tagged background_check)1:1 | Mapping required | |
| Benefits Enrollment Snapshot | Custom Fields (Plan, Coverage, Dependents)1:1 | Fully supported | |
| Integration Configurations (ADP, Workday, UKG) | Not Migrated1:1 | Fully supported | |
| ATS Candidate Records (via Greenhouse/Lever Integration) | Candidate or Contact (source preserved)1:1 | 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.
EMP Trust HR gotchas
I-9 e-signature audit trails use proprietary storage
Third-party notary delays for I-9 Section 2
Greenhouse/Lever candidate-to-hire data mapping is partial
Benefits enrollment is a snapshot, not a live feed
API rate limits and export methods are undocumented
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 scoping audit
We audit the source EMP Trust HR tenant across employee headcount, I-9 record volume, onboarding package count, form library size (including custom forms with conditional logic), training record history, benefits enrollment snapshots, background check result volume, and active integration connectors. We pair this with a Crelate edition assessment (Standard, Plus, or Enterprise) based on the customer's feature requirements (onboarding workflows, custom fields, document storage limits, API access). The discovery output is a written migration scope document covering record counts, compliance artefact inventory, and integration handoff list.
I-9 compliance extraction and e-signature reconstruction
We extract all I-9 records (Section 1 and Section 2) and custom compliance forms with e-signature audit trail metadata. For each record, we reconstruct the e-signature envelope (signer ID, timestamp, IP address, certificate hash) from EMP Trust HR's proprietary storage and apply a standard schema before writing to Crelate as tagged documents. We identify all incomplete I-9 records (mid-process hires with outstanding Section 2) and flag them with a migration status. We also extract E-Verify case numbers and status codes to structured custom fields on the Contact record.
Onboarding package disaggregation and Crelate schema provisioning
We disaggregate EMP Trust HR's Hire-driven onboarding packages into separate Crelate records: Contact profiles, Onboarding Workflow instances, Document records (for completed forms), and Task items (for onboarding and HR manager action items). We provision custom fields in Crelate for E-Verify status, benefits enrollment snapshots, training completions, and background check summaries before any data import. Any custom forms with conditional logic are inventoried separately for rebuild in Crelate's form builder.
Sandbox migration and reconciliation
We run a full migration into Crelate's sandbox environment (or a test workspace if sandbox is not available on the customer's tier) using production-like data volume. The customer's HR lead reconciles record counts (Contacts in, Documents in, Onboarding Workflows in, Tasks in), spot-checks 25-50 random employee records against the EMP Trust HR source, and verifies I-9 document completeness and e-signature readability. Any mapping corrections happen in this phase before production migration begins.
Integration inventory and admin handoff
We compile a written inventory of every active EMP Trust HR connector (ADP, Workday, UKG, Oracle, SAP, Greenhouse, Lever, background check providers) with the integration type, data flows, and recommended Crelate replacement (native integration, Zapier, or manual reconfiguration). We document ATS-triggered candidate-to-hire field mappings from Greenhouse and Lever that were used to create EMP Trust HR employee records, so the customer's admin can configure equivalent mappings in Crelate or reconcile against the original ATS export. Integration endpoints, credentials, and schedule settings are not migrated and must be re-established in Crelate post-migration.
Production migration and cutover
We freeze EMP Trust HR writes during cutover, run a final delta migration of any records modified during the migration window, then enable Crelate as the system of record. We deliver the integration inventory document, custom form rebuild checklist, and any incomplete I-9 flags to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild EMP Trust HR onboarding logic, conditional form branches, or integration connectors as part of the migration scope; those are separate engagements or internal admin tasks.
Platform deep dives
EMP Trust HR
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 EMP Trust HR 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
EMP Trust HR: Not publicly documented..
Data volume sensitivity
EMP Trust HR exposes a bulk API — large-volume migrations stream efficiently.
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 EMP Trust HR to Crelate migration scoping. Not seeing yours? Book a call.
Walk through your EMP Trust HR 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 EMP Trust HR
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.