Migrate from Employ to Crelate

Employ Candidates map directly to Crelate Contacts. The mapping uses the Candidate's primary email as the dedupe key. We extract and write AI interview scores to a custom Contact field (ai_interview_score__c) that we create in Crelate during schema preparation. Any other metadata on the Candidate record (source, current stage timestamp, rating) migrates as additional custom fields. FirstName, LastName, Email, Phone, and Address fields map by name.

Employ Jobs map to Crelate Jobs. Both platforms use Job as a core entity with Name, Description, Department, Location, and Status. The Job Name is the required attribute in Crelate's API, matching Employ's title field. Status values (Open, Closed, Draft, On Hold) map to Crelate's job status picklist. Department and Location migrate as text fields unless Crelate's organization has configured lookup fields for these.

Employ Applications link a Candidate to a Job and track pipeline stage. Crelate does not have a native Application object; instead, candidate-job associations and stage history migrate as Activity records (Notes or Tasks) attached to the Contact, with the Job referenced via the WhatId lookup. Stage timestamps and stage names migrate as custom fields on the Activity record. We flag any Application records with no matching Candidate or Job in Crelate during reconciliation before the load phase.

Both Employ and Crelate allow customizable pipeline stages per Job, with no universal stage name schema. We extract the complete list of active stage names from Employ during discovery and map each to the corresponding Crelate Job's pipeline stage. Stages with no direct equivalent are flagged for manual assignment before migration to prevent Candidates from landing in a null stage. Any stage probability or order values migrate as configuration metadata.

Employ AI Recruiter scores are stored as metadata on the Candidate rather than as a standalone object. We extract these as structured numeric or text values and write them to a custom ai_interview_score__c field on the Crelate Contact. If multiple interview rounds exist, we create additional fields (ai_interview_score_round1__c, ai_interview_score_round2__c) or write a JSON object to a long-text custom field, depending on the scoring structure in Employ.

I-9 and E-Verify records are sensitive compliance documents associated with the hired Employee in Employ. We transfer these as encrypted file attachments linked to the corresponding Crelate Contact record. We do not re-trigger a verification workflow in Crelate because Crelate does not have native I-9/E-Verify automation. The customer's HR or compliance team must review the transferred documents and confirm acceptance; if Crelate requires manual re-entry, we document the fields requiring completion to avoid compliance gaps.

Employ Employee records (post-hire with employment details, start date, department, manager, employment status) map to Crelate Contacts with additional custom fields for employment metadata. We create fields for start_date__c, department__c, manager_name__c, employment_status__c on the Contact record. Manager resolves to a Contact lookup if the manager exists as a Contact in Crelate; otherwise it stores as a text reference name.

Employ Users with roles (Recruiter, Hiring Manager, Admin) map to Crelate Users. We resolve by email match against the destination Crelate organization's User table. Any Employ User without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes, since OwnerId references are required on most standard records. Role mappings (Recruiter to Crelate Recruiter role, Hiring Manager to Hiring Manager role) transfer as text in a custom role field until the admin assigns the correct Crelate role.

Employ supports custom fields on Jobs, Candidates, and Applications. We discover these during the scoping phase by querying the Employ data export for fields not in the standard schema. Each custom field maps to a Crelate custom field of the closest matching type (text, number, date, picklist, checkbox). Crelate's Advanced Custom Fields limit is 10 on the Business tier, 20+ on Business Plus and Enterprise; we verify the customer's Crelate tier supports the required custom field count before migration.

Job postings distributed to third-party job boards in Employ are tracked as configuration settings rather than as data records. We do not migrate these configurations because they are destination-specific and Crelate has its own job distribution settings that the customer's admin rebuilds manually. We document the list of active distributions (Indeed, LinkedIn, Monster, etc.) in the migration inventory so the admin can reconfigure them post-migration.

Attachments on Employ Applications (resumes, cover letters, portfolio files) transfer as file attachments linked to the corresponding Crelate Contact record. We preserve the original filename and file type, and map the attachment to the Contact record that resulted from the Candidate migration. Large file attachments (over 25 MB per Crelate's API limits) are flagged for the customer to upload manually via Crelate's interface.

If Employ uses Tags on Candidates for segmentation or sourcing attribution, these migrate to Crelate Tags on the Contact record. Crelate's API supports Tags with category keys; we map Employ tags to the Default category unless the customer's Crelate organization has configured named tag categories during setup.