Migrate from E-Staff to Recruit CRM & ATS

E-Staff Candidate records map to Recruit CRM Contacts in candidate mode. The E-Staff candidate status (active, placed, archived) maps to Recruit CRM's candidate workflow stages. Candidate source, skills, and availability dates migrate as custom fields on the Contact. Any user-defined candidate fields in E-Staff are audited during scoping and mapped explicitly to typed Recruit CRM fields.

E-Staff Placements carry the core staffing transaction: the candidate placed, the client company, job order details, pay rate, bill rate, start date, and end date. We split this into Recruit CRM's Job Order (the open requisition) linked to a Candidate, with pay/bill rate details stored as custom fields or in Recruit CRM's timesheet module if available on the plan. Placement history migrates as a completed Job Order record with placement metadata.

E-Staff client Companies map to Recruit CRM Organizations. The company name, address, industry, and primary contact details migrate directly. Client-specific notes, billing terms, and any custom company fields from E-Staff are mapped to Organization custom fields in Recruit CRM.

E-Staff Employee records (internal staff at the agency) map to Recruit CRM Users when the employee is a recruiter using the system, or to Contacts in internal-mode if the agency tracks internal employees as candidate records. The mapping depends on how E-Staff uses the Employee object versus the Candidate object for internal agency staff.

E-Staff stores compensation history as effective-dated rows (start date, end date, pay rate, benefits) that are independent inserts preserving audit trails. Recruit CRM does not have a native effective-dated compensation object. We map these as structured custom fields on the Placement or Candidate record (most recent effective row as current values, prior rows as notes or as a separate compensation history custom object if the customer's plan supports it).

E-Staff allows user-defined fields with no enforced naming convention, so each custom field must be audited and explicitly mapped during scoping. We determine the field type (text, number, date, picklist, checkbox), map it to an equivalent Recruit CRM custom field, and flag any E-Staff custom fields that have no direct Recruit CRM equivalent for customer decision during scoping. Recruit CRM's per-plan field limits are checked against the total custom field count before migration.

E-Staff's organizational structure and department hierarchy map to Recruit CRM's Team or Branch structure if available on the customer's plan. Branch and team assignments on candidates and job orders migrate as lookup fields. Recruit CRM's team-based user permissions map to E-Staff's org-level access controls.

E-Staff timesheet data (hours worked by placed candidates) maps to Recruit CRM timesheet entries if the destination plan includes timesheet functionality. Timesheet records are linked to the Placement and Candidate. If Recruit CRM's timesheet module is not available on the customer's plan, timesheet history is flagged during scoping as a candidate for archival or a separate payroll system.

E-Staff document attachments (resumes, contracts, onboarding paperwork) attached to Candidate, Placement, or Company records migrate as Recruit CRM file attachments linked to the equivalent record. File naming conventions are preserved. Large attachments (over 10 MB) are flagged for the customer to upload manually post-migration if Recruit CRM's plan has storage limits.

E-Staff Owner records (the recruiter or staff member assigned to a Candidate, Placement, or Company) map to Recruit CRM Users by email match. Any E-Staff Owner without a matching Recruit CRM User is held in a reconciliation queue for the customer's admin to provision before record import resumes.