Migrate from E-Staff to Crelate

E-Staff Candidates map to Crelate Contacts. The candidate name, email, phone, address, and resume URL fields migrate as typed Contact fields. E-Staff candidate status (active, passive, placed, etc.) maps to a Crelate custom picklist field candidate_status__c. Candidate source and tags from E-Staff migrate as multi-select picklist fields on Contact. We preserve the original E-Staff candidate ID in a custom field estaff_id__c for reconciliation.

E-Staff Companies (client organizations in the staffing context) map directly to Crelate Companies. Company name, address, industry, and contact email migrate as typed Company fields. The estaff_id__c custom field is set on the Company for reconciliation. If E-Staff stores multiple contacts per company, the additional contacts migrate as Crelate Contacts linked via the Company lookup.

E-Staff Placements are the central staffing object linking a Candidate to a Client Company with pay rate, bill rate, start date, end date, and job title. We map Placements to Crelate Opportunities with the Contact (candidate) as the primary WhoId and the Company (client) as the WhatId. Job title, position description, and staffing type (temp, temp-to-hire, direct-hire) migrate to custom Opportunity fields. E-Staff Placements that span multiple roles for the same candidate-company pair generate separate Opportunity records.

E-Staff stores pay rate and bill rate as date-stamped rows with effective start and end dates, meaning the same field holds multiple historical values. We model these as Crelate custom fields with a date range suffix (pay_rate_effective_2024_01_01__c) or as individual Opportunity custom fields capturing the most recent compensation pair. The customer chooses the strategy during scoping. We flag any placement with more than three effective-dated rows as a complexity item and document the full history in the migration notes.

E-Staff Job Orders (open requisitions) map to Crelate Opportunities with a job_order__c flag, or to a custom Job object if the customer uses Crelate's custom object capability. Job Order status (open, filled, cancelled) maps to Opportunity Stage. Open submissions in E-Staff become Crelate Activities (Tasks) on the related Opportunity.

E-Staff Submissions (candidate submitted to a job order) map to Crelate Tasks linked to the Opportunity. Submission status (submitted, interview, offer, rejected) migrates as a custom picklist field submission_status__c. Submission notes and feedback from the hiring manager migrate as Task description and custom comment fields.

E-Staff HR records (standard employee profile fields beyond staffing contact info) map to Crelate Contacts with a department__c, hire_date__c, and employee_id__c custom field set. If the staffing agency runs concurrent HR operations, we recommend a custom Employee object in Crelate to separate HR and candidate data. If E-Staff stores payroll history, we migrate the current pay rate and last-pay-date as Contact custom fields and flag payroll data for the customer's payroll system admin to reconcile separately.

E-Staff recruiter and admin user accounts map to Crelate Users by email match. We resolve estaff_owner_id references on Candidate, Placement, and Company records to the corresponding Crelate User. Any E-Staff user without a Crelate match goes to a reconciliation queue for the customer's admin to provision before record import resumes.

E-Staff notes attached to Candidate, Placement, or Company records migrate to Crelate Note records linked via ContentDocumentLink to the parent Contact, Opportunity, or Company. Note body and timestamp preserve. If notes contain HTML formatting from E-Staff, we strip to plain text during transform to avoid Crelate rendering issues.

E-Staff engagement history (call logs, email threads, meeting records) attached to Candidates or Placements migrates to Crelate Tasks (TaskSubtype = Call for calls) and Events. We resolve the parent Contact and Opportunity references at migration time using the contact_id and placement_id lookups. ActivityDate and Duration preserve for timeline ordering.

E-Staff custom fields carry no enforced naming convention and may have inconsistent types across records. We audit every distinct custom field during scoping, resolve its data type (text, number, date, currency, picklist), and create a matching Crelate custom field on the appropriate Core Record before migration. Custom fields with mixed data types in E-Staff (a known E-Staff behavior) are flagged as data-quality items and mapped to Crelate text fields to avoid import rejection. The full custom field inventory is delivered as a written document at scoping.

E-Staff tags and categories used to classify Candidates and Placements migrate to Crelate multi-select picklist fields on Contact and Opportunity. Tag values that do not yet exist in Crelate are created during migration. If tags exceed 500 distinct values, we recommend a Crelate Topic-based tagging strategy instead.