Migrate from Eddy to Recruit CRM & ATS

Eddy employee records map to Recruit CRM candidate profiles. We extract first name, last name, email, phone, job title, department, hire date, employment status, and work location as standard candidate fields. Eddy's employee directory hierarchy transfers as Recruit CRM candidate tagging by department. Employment status (active, on leave, terminated) migrates as a custom candidate field and is noted for admin review since it carries different meaning in a recruitment context.

Eddy's company-level settings including business name and locations map to Recruit CRM client records. The company name becomes the client organization name, and primary location becomes the client address. This is a structural simplification since Recruit CRM does not have an org-level settings object—company data lives as client records. We flag which fields require admin review after import.

Eddy departments have no direct Recruit CRM equivalent. We map department names to Recruit CRM tags on candidate and client records. During scoping, the customer selects whether departments map to candidate skills tags, client industry tags, or a dedicated custom picklist field. This is a configuration decision confirmed before production import.

Eddy employee documents (offer letters, contracts, signed agreements, certifications) migrate as Recruit CRM candidate attachments. We extract file blobs with original filenames and preserve upload timestamps. Document type classification from Eddy (offer letter, NDA, benefits form) is noted in the filename or a custom field since Recruit CRM attachments do not have a native type taxonomy.

Eddy onboarding step checklists and task assignments have no native Recruit CRM equivalent. We extract active onboarding tasks and completed steps as candidate notes with a timestamp and assignee, preserving what was done but not the workflow structure itself. The customer receives a written inventory of onboarding tasks requiring rebuild as Recruit CRM checklist items or a separate HR onboarding tool.

Eddy employment status changes, termination dates, and status change reasons migrate as candidate notes. We extract the status history timeline and attach it as a chronological note block on the candidate record so the full employment trajectory is visible to recruiters in Recruit CRM.

Eddy PTO policies, accrual rates, and carry-forward rules have no Recruit CRM equivalent. Recruit CRM is an ATS and does not include HR time-off tracking. We export PTO policy configurations as a structured CSV deliverable for the customer's HR team to enter into their chosen HRMS or payroll tool post-migration.

Eddy training completion records and certifications tied to employees have no Recruit CRM equivalent. Recruit CRM does not include training or certification tracking. We export training history as a structured CSV including employee name, training name, completion date, and expiration date for manual entry into the destination HR or compliance tool.

Eddy payroll data including pay run history, compensation amounts, and payroll integration records are not fully exportable via API. Reviewers consistently note incomplete integration between Eddy's HR and payroll modules. We extract any available payroll records via CSV export where accessible and flag which records require manual extraction or reconciliation before migration finalization.

Eddy company settings including locations, policy configurations, and org-level preferences have no dedicated Recruit CRM object. We map location data to Recruit CRM client address fields and deliver a written inventory of policy settings requiring manual reconfiguration in Recruit CRM or a companion HR tool.