Migrate from Easy Tech to Recruit CRM & ATS

Easy Tech's candidate data lives in a named custom object (e.g., 'Talent', 'Candidate', 'Person') that varies per installation. We identify the object via the discovery audit before mapping it to Recruit CRM's Candidates object. All candidate properties map to Candidate record fields — built-in or custom.

Easy Tech stores skills, source, rating, and status as custom properties per installation. Built-in Recruit CRM fields (source, rating) take those values directly. Non-standard custom properties create Recruit CRM custom fields (Candidate__c.Custom_Skill_Tags__c, Candidate__c.Compliance_Status__c) with type-aware mapping — pick-lists become Recruit CRM pick-lists, text becomes text, numbers become number.

Easy Tech's client or company data maps to Recruit CRM's Clients object. Parent-company hierarchies in Easy Tech (if present) map to the Client.Parent_Client__c custom field in Recruit CRM. Multi-contact client accounts collapse to a primary client record with associated client contacts.

Client contacts in Easy Tech map to Recruit CRM Client Contacts. The link to the parent Client record is preserved via the Client__c lookup. Primary contact designation in Easy Tech becomes the primary flag on the Recruit CRM Client Contact record. Additional phone numbers beyond the first map to custom phone fields.

Easy Tech job data maps to Recruit CRM Job Orders. The Job Order object in Recruit CRM includes Title, Description, Requirements, Status, Skills, Location, Salary fields. Easy Tech's custom job fields (e.g., 'Department', 'Employment Type', 'Clearance Level') become custom fields on the Job Order in Recruit CRM.

Easy Tech job pipeline stages are custom status values defined per installation — no standard stage model. We map each Easy Tech status value to Recruit CRM's Job Order Status pick-list (Open, Closed, On Hold, Cancelled) by reviewing the live values in the Easy Tech instance during discovery. Any Easy Tech statuses without a Recruit CRM equivalent create a custom status value before import.

Easy Tech applications link a candidate to a job as a custom junction object or through association properties. In Recruit CRM, the candidate record is linked to the Job Order via the standard Job Order lookup on the candidate. Application status maps to a Candidate__c.Job_Application_Status__c custom field with value mapping applied per the Easy Tech status values present in the instance.

Placements in Easy Tech map to Recruit CRM Placements. The Placement links to the Candidate record (Candidate__c) and the Job Order (Job_Order__c), preserving the company, start date, and any placement-specific custom fields. Compensation details (base salary, bill rate, margin) store as custom fields on the Placement record since Recruit CRM does not enforce a compensation schema at the object level.

Easy Tech activity records — notes, call logs, email threads, and calendar events — map to their corresponding Recruit CRM activity types. Note content maps to Recruit CRM Notes with body text, timestamp, and owner preserved. Call logs carry duration, outcome, and call type. Email threads map to Recruit CRM's email activity with subject, body, and timestamp. Meeting records carry start/end time, location, and participants.

Any Easy Tech custom objects beyond Candidates, Jobs, Clients, and Placements (e.g., compliance documents, timesheets, skill assessments) map to Recruit CRM custom objects. We create the destination custom object schema in Recruit CRM during the pre-migration setup phase, define the field types and pick-list values, and then import the records via Recruit CRM's custom object bulk import endpoint.

Easy Tech attachments stored as external URLs (Google Drive, Dropbox, S3) require re-upload to Recruit CRM's document management. We download files referenced by URL, rename them to reflect the associated record (e.g., [CandidateName]_Resume.pdf), and upload to the corresponding Recruit CRM record. Original upload timestamps are preserved as a custom metadata field where the source provides that data.

Easy Tech user IDs map to Recruit CRM users by email address match. Unmatched users — those in Easy Tech but not yet invited to Recruit CRM — are flagged before migration. The migration plan requires either inviting those users to Recruit CRM first or assigning their records to a fallback recruiter. No record lands without an owner assignment.