Migrate from EMP Trust HR to Recruit CRM & ATS

EMP Trust HR employee records map to Recruit CRM Candidate profiles. We extract standard fields: name, email, phone, address, employment type, start date, work location, and manager assignment. Custom employee properties map to Recruit CRM custom fields or notes. The hire's onboarding portal state (started, in-progress, completed) is documented as a note on the Candidate record since Recruit CRM does not have a native onboarding portal object.

Candidates that arrived in EMP Trust HR via Greenhouse or Lever webhooks are already in candidate form but may have incomplete fields because the integration only pushes fields mapped in the connector configuration. We document the integration field map during scoping, extract all available candidate fields from EMP Trust HR, and flag any original ATS fields not included in the integration mapping so the customer can re-extract those from the original Greenhouse or Lever export before migration.

EMP Trust HR's branded onboarding portal instances and portal completion state have no direct equivalent in Recruit CRM. We extract portal configuration metadata (portal ID, status, completion percentage, start date) as a structured note attached to the Candidate record. The portal's task set and task completion flags are migrated as individual task notes or checklist items on the Candidate if Recruit CRM's task module is used.

Completed forms (offer letters, NDAs, non-competes, tax withholding, direct deposit, beneficiary forms) with e-signature audit trail data migrate as tagged document records with e-signature metadata (signer ID, timestamp, IP address, certificate hash) written into the Candidate document description or a custom notes field. Form definitions themselves (the template structure) are not migrated; we deliver a written inventory of form templates requiring rebuild in Recruit CRM or via a third-party form builder.

I-9 Section 1 (employee completion) and Section 2 (employer/agent verification) records with E-Verify case status and USCIS verification results cannot be stored as native structured fields in Recruit CRM because Recruit CRM has no I-9 or E-Verify object. We export completed I-9 records as PDF artefacts with e-signature certificate chain metadata embedded in the document record. For in-progress I-9s (Section 1 complete, Section 2 pending due to third-party notary delays), we flag the incomplete state and document the outstanding verification action so the customer's HR team can initiate a new I-9 workflow post-migration.

E-Verify case status codes (Verified, Tentative Nonconfirmation, DHS/DOJ Query) are extracted from EMP Trust HR and written as structured text into the Candidate document artefact alongside the I-9 record. The E-Verify case number and USCIS verification date migrate as custom fields on the Candidate if Recruit CRM supports custom field creation; otherwise they are embedded in the document description.

Onboarding tasks assigned to new hires, managers, HR staff, and IT with status, due dates, assignees, and completion timestamps migrate as individual Recruit CRM tasks attached to the Candidate record. Task hierarchy within onboarding packages flattens to a task list; we preserve parent-child relationships as task grouping or as sequential task notes. Incomplete tasks at migration time are flagged with their due date and assignee so the HR team can reassign or recreate them in Recruit CRM.

Course completion records from EMP Trust HR's new hire learning portal (course name, completion date, score, assignment timestamp) migrate as structured notes on the Candidate record. Recruit CRM does not have a native learning management or training module. We flag any in-progress training assignments at migration time so the customer can plan for manual reassignment or external training tool re-enrollment.

Background check order summaries and status results sourced through EMP Trust HR's pre-built integrations (CastleBranch, AccurateBackground, BirdDogHR) migrate as PDF document artefacts attached to the Candidate record. Raw vendor reports (the full third-party screening package) do not migrate; these must be requested directly from the background check vendor if the customer requires them post-migration. Recruit CRM does not integrate natively with background check providers without Zapier or an API extension.

Benefits selections captured during onboarding in EMP Trust HR (plan choices, dependent information, beneficiary designations) migrate as structured historical notes on the Candidate record. EMP Trust HR stores benefits enrollment as a snapshot at the time of onboarding completion; it does not maintain a live connection to benefits carrier APIs. We flag that any active ongoing benefits changes must be captured separately from the HRIS export and manually reconciled at the destination.

If EMP Trust HR contains client or company records associated with a staffing or recruiting use case (EMP Trust HR supports staffing industry vertical per its partner page), those map to Recruit CRM Client records with company name, address, primary contact, and industry. EMP Trust HR does not typically store client records as a core object; we confirm during scoping whether any company records exist outside the employee data.

Pre-built integration connector configurations (ADP, Workday, Oracle, SAP, UKG, Greenhouse, Lever) and their sync schedules, credential mappings, and webhook endpoints do not migrate. EMP Trust HR does not export connector configuration state. We deliver a written inventory of each active integration with the destination endpoint, trigger condition, and recommended rebuild path (native Recruit CRM integration, Zapier chain, or manual re-configuration).