Migrate from JobAdder to Recruit CRM & ATS

JobAdder Candidate records map to Recruit CRM Candidate with all standard profile fields, skills, work history, and source attribution preserved. We map the candidate status (active, archived, placed) and preserve the primary tag array as a flat label list for the customer's admin to reapply in Recruit CRM's tagging taxonomy. Attachments (CVs, cover letters, certifications) migrate as binary blobs with original filenames and MIME types preserved.

JobAdder Job Orders map to Recruit CRM Job with status (open, filled, on-hold, cancelled) translated to Recruit CRM job status values. Job Adder pipeline stages map to Recruit CRM pipeline stages, and we document the stage-to-stage mapping in the field map. The job description, requirements, and assigned consultant migrate as custom fields where Recruit CRM does not have native equivalents. Job board posting history attached to the Job Order migrates as a structured note documenting the board name and posting date.

JobAdder Client records map to Recruit CRM Client with company details, industry, size, and contact information preserved. The primary contact on the Client record maps to a linked Contact record in Recruit CRM. Client portal associations are documented as a pre-migration capture task because JobAdder's portal activity threads are not exportable and must be manually captured by the customer.

JobAdder Contact records on the client side (distinct from Candidate) map to Recruit CRM Contact with email, phone, role, and owning consultant preserved. Where a Contact shares an email address with a Candidate record, we flag the potential duplicate during scoping and the customer chooses a dedupe strategy before migration.

JobAdder Placement records (placed candidates tied to a Job and Client) map to Recruit CRM Placement with start date, end date, and status preserved. Temp and contract placement billing fields (bill rate, pay rate, markup percentage, timesheet period) require explicit mapping because JobAdder's native temp billing module does not map 1:1 to Recruit CRM's billing fields. We preserve these as custom properties on the Placement record and document every billing field in the field map.

JobAdder Opportunity records representing the business development pipeline map to Recruit CRM Deal with status, estimated value, expected close date, and owning consultant preserved. The Opportunity pipeline name maps to a Recruit CRM pipeline name, and stage probabilities migrate from JobAdder to Recruit CRM stage configuration.

JobAdder custom fields on Candidates, Jobs, and Clients vary by tenant. We discover the full custom field list during discovery by requesting a read-only test export from the customer, generate field-level mappings to Recruit CRM custom fields, and pre-create the destination schema before any data import. Any custom fields that reference plan-gated JobAdder features (e.g., AI matching fields available only on Pro) are flagged as requiring Recruit CRM equivalent configuration post-migration.

JobAdder user accounts (consultants and recruiters) are migrated as inactive placeholder records to preserve assignment history on Job Orders, Placements, and Opportunities. Active user provisioning in Recruit CRM must be handled separately by the customer's admin; we cannot create active user accounts as part of the data migration scope. We document every user mapping with their email, name, and JobAdder role for the admin to provision.

JobAdder Task records linked to Candidates, Jobs, or Clients migrate to Recruit CRM Task with due dates, statuses (open, completed), and assignees preserved. Completed tasks carry a historical record; open tasks migrate as open. We resolve the assignee by matching JobAdder user email to Recruit CRM user email, with any unresolved assignees documented for the admin to reconcile.

File attachments on Candidate profiles (CVs, cover letters, certifications) migrate as binary blobs associated with the Candidate record in Recruit CRM. We preserve original filenames and MIME types. Attachments are the last object imported in the dependency chain because they require a parent Candidate record to exist first. Attachment migration is chunked for large volumes to avoid timeout issues.

Tags applied to Candidates and Jobs in JobAdder migrate as flat label arrays in Recruit CRM. The semantic meaning of tags (e.g., sourcing channel, vetting status, role type) is preserved, but the tag taxonomy is not — Recruit CRM's tagging taxonomy must be rebuilt by the customer's admin post-migration. We deliver a full tag inventory with frequency counts as part of the migration package so the admin can prioritise which tags to recreate.

Temp placements in JobAdder carry bill rate, pay rate, markup percentage, and timesheet period fields that have no direct 1:1 equivalent in Recruit CRM's standard schema. We preserve these fields as custom properties on the Placement record using Recruit CRM's custom field capability. We document every billing field in the field map and call out which display configurations (e.g., custom placement detail views) the admin must enable to surface the data correctly after migration.