Migrate from Eddy to Crelate

Eddy employee records migrate to Crelate Contact with Person type classification. Employment context from Eddy—job title, department, hire date, employment status, location, and salary range where available—maps to custom Contact fields (eddy_title__c, eddy_department__c, eddy_hire_date__c, eddy_employment_status__c, eddy_location__c). The employee's Eddy email becomes the Crelate Contact email for deduplication. Eddy's HR fields have no native Crelate equivalent, so custom fields carry the employment context into the ATS for reference and reporting.

Eddy company records (employers, clients, or organizations stored in the directory) map directly to Crelate Company. The company name, website, address, and phone migrate as typed Crelate Company fields. Companies are migrated first because Contacts in Crelate carry a Company lookup, and that reference must exist before Contact insert to satisfy the foreign key.

Job postings created in Eddy Hire migrate to Crelate Job Order. Job title, description, status (open/closed/draft), location, employment type, and department transfer to Crelate Job Order fields. The Eddy Hire pipeline stage (applicants, screening, interview, offer) maps to the corresponding Crelate submission pipeline stage.

Candidates tracked in Eddy Hire migrate to Crelate Candidate. Name, email, phone, resume, work history, education, and skills migrate directly. Custom candidate fields from Eddy Hire map to Crelate Candidate custom fields. Resume blobs migrate as Crelate resume attachments. Email and phone are used as the Crelate deduplication key to prevent duplicate Candidate records.

Applications in Eddy Hire represent the junction between a Candidate and a Job Opening at a specific stage. Each application migrates as a Crelate Submission record linking the Candidate and Job Order with submission date, status, source, and stage. A candidate with multiple active applications in Eddy Hire produces multiple Submission records in Crelate. The submission history is preserved as a Crelate Activity record on the candidate timeline for audit.

Eddy departments do not have a native Crelate ATS equivalent. Department names migrate as a custom picklist field on the Crelate Contact record (eddy_department__c). For organizations requiring department-level reporting in Crelate, we recommend creating departments as Crelate Companies with a department classification tag and linking Contacts to those department-Company records via a custom lookup.

Eddy location records (office addresses, work sites, geo-locations) migrate to the address fields on Crelate Company. For location-based filtering on Candidates and Job Orders, location maps to a custom text or picklist field on the respective Crelate object (eddy_location__c). Eddy's geo-location tracking from mobile time clocks is not portable to Crelate's ATS model.

Employee documents (offer letters, signed agreements, certifications) stored per employee in Eddy migrate as Crelate Attachments linked to the corresponding Contact record. PDF and standard document formats are supported. File names and upload timestamps are preserved. Documents without an associated employee contact record (org-level policies, company handbooks) are migrated as Attachments on the primary Company record.

PTO balances and accrual records in Eddy have no equivalent in Crelate ATS. Crelate does not track time-off balances or manage HR leave policies. We extract a CSV snapshot of current PTO balances for the customer's HR team to retain outside the ATS. If the customer uses a separate HRIS post-migration, the PTO data should be imported into that system. We flag this gap during scoping and recommend the customer export current balances before the migration freeze window.

Payroll records (pay runs, direct deposit details, tax withholdings) in Eddy have no Crelate ATS equivalent and are not migratable. Reviewers consistently note that Eddy's HR and payroll modules are not fully integrated, and pay run history requires manual extraction. We extract available payroll records as a CSV for the customer's finance team and recommend that payroll data be imported into a dedicated payroll platform post-migration rather than into Crelate.

Eddy onboarding workflows and step checklists have no direct Crelate ATS equivalent. Crelate does not include an onboarding module or new-hire task management tool. We audit active onboarding workflows in Eddy, document the step structure, responsible parties, and completion criteria for each active workflow, and deliver a written inventory that the customer's admin uses to rebuild onboarding steps manually in Crelate or a dedicated onboarding platform.

Eddy's employee directory is derived from employee records and does not exist as a separate data object. The directory structure (organizational hierarchy, reporting chains) migrates implicitly through the Contact records via manager lookup fields where the customer elects to populate them. Crelate does not include an org chart or employee directory feature; if the customer requires a visual directory post-migration, we recommend a separate HR directory tool or a custom Experience Cloud implementation.

Training completion records in Eddy migrate as structured data linked to the Contact record. We extract training name, completion date, certification status, and expiry date, and map these to Crelate Contact custom fields (eddy_training_name__c, eddy_training_date__c, eddy_certification_expiry__c). For organizations with extensive training histories, we recommend exporting the full training log as a CSV reference and using it to configure multi-select picklists or related record structures in Crelate as needed.

Eddy org-level settings including departments, locations, and policy configurations do not have a dedicated Crelate ATS equivalent. Department names migrate as custom Contact or Company fields; location addresses migrate to Company address fields. Leave policies, PTO rules, and org-wide settings are documented in a written inventory for the customer's admin to rebuild as internal documentation or in a dedicated HR platform. We explicitly flag policy configuration as out-of-scope for ATS migration.