Migrate from Easy Tech to Bullhorn ATS & CRM

Easy Tech candidate records map directly to Bullhorn's Candidate object. Bullhorn Candidate stores name, email, phone, address, employment history, education, skills, and status. Employment history migrates to Bullhorn's separate WorkExperience child object; education to CandidateEducation. Original create dates preserved as a custom field since Bullhorn's native CreatedDate reflects migration timestamp.

Easy Tech candidate status values (Active, Passive, Placed, Archived) map to Bullhorn's Candidate.status pick-list. Value-by-value mapping required because Easy Tech may use different status labels than Bullhorn's default options. FlitStack surfaces the value map before migration runs so your Bullhorn admin can add any missing status values to Bullhorn's pick-list.

Easy Tech client or company records map to Bullhorn ClientCorporation. Bullhorn ClientCorporation stores company name, address, industry, website, and tax ID. Client contacts associated with the company migrate as Bullhorn ClientContact records linked via clientCorporationID. Primary contact designated in Easy Tech becomes the primary ClientContact in Bullhorn.

Easy Tech contacts associated with a client map to Bullhorn ClientContact. Fields include firstName, lastName, email, phone, title, and notes. Each ClientContact links to a ClientCorporation via clientCorporationID. Multiple contacts per client are preserved — Bullhorn supports N client contacts per ClientCorporation.

Easy Tech job or order records map to Bullhorn JobOrder. JobOrder stores title, description, employmentType, payRate, startDate, and status. Bullhorn distinguishes between open, placed, and cancelled job statuses. Job requirements and skills from Easy Tech map to JobOrder's skillList or custom text fields depending on how Easy Tech stored requirements.

Easy Tech job status values (Open, Closed, Filled, On Hold) map to Bullhorn JobOrder.status. Bullhorn uses a different status vocabulary than most ATS platforms — 'New' and 'Open' are distinct, and 'Placed' indicates all positions on the order are filled. The value map ensures your Bullhorn job board reflects the same operational state as Easy Tech.

Easy Tech placement or deal records map to Bullhorn Placement. Placement links a Candidate to a JobOrder and ClientCorporation. Bullhorn Placement stores jobOrderID, candidateID, startDate, endDate, payRate, billRate, and status. Commission records associated with placements map to PlacementCommission — FlitStack identifies these from Easy Tech's data model during discovery.

Easy Tech may store commission data as fields on placement records or as a separate object. Bullhorn separates this into PlacementCommission as a child of Placement. If Easy Tech stores commission per placement as a flat record, FlitStack creates a custom mapping to the child commission structure. Custom configuration may be required if Easy Tech uses multi-tier commission splits.

Easy Tech notes and activity history attached to candidates, jobs, or placements migrate as Bullhorn Note records. Note stores body, actionType, and dateAdded. Original timestamps and owning user preserved. Bullhorn associates notes to the correct parent record (Candidate, JobOrder, or Placement) via parentID and parentType.

Easy Tech owner or recruiter IDs resolve by email match to Bullhorn User records. Unmatched owners flagged before migration — your Bullhorn admin must create User accounts for any recruiters not yet in Bullhorn. Records without a resolved owner assign to a default Bullhorn user specified in the migration plan. Owner resolution prevents orphaned records in Bullhorn.

Easy Tech custom fields attached to candidate records migrate as Bullhorn userDefinedFields on the Candidate object. Bullhorn requires these to be pre-created in the Bullhorn schema before migration. FlitStack delivers a custom field creation guide specifying fieldType, label, and valueSet so your Bullhorn admin can provision them before data loads.

Easy Tech custom fields on client or company records become Bullhorn userDefinedFields on ClientCorporation. Field types (text, number, date, pick-list) carry over with their definitions. Pick-list custom fields require value mapping if Easy Tech and Bullhorn use different option labels. FlitStack surfaces these during the mapping review phase.

Easy Tech custom fields on job orders become Bullhorn userDefinedFields on JobOrder. Common examples include internal job codes, branch office tags, or client-specific requirements fields. Bullhorn's JobOrder object supports custom fields of type string, integer, decimal, and pick-list. FlitStack creates the schema setup plan before migration runs.

Easy Tech resumes and file attachments associated with candidates migrate as Bullhorn CandidateAttachment records. Bullhorn stores attachments separately from the candidate record — each attachment links via candidateID and stores the file type, description, and original content. Bullhorn supports PDF, DOC, DOCX, and common image formats. File size limits apply per Bullhorn's upload constraints.