Migrate your JobAdder data

Candidates is the central object in JobAdder, holding all profile data, skills, work history, and attachments. We migrate Candidates with all standard fields and preserve their association to Job Orders, Placements, and custom tags. Candidate records without a placement are migrated as active candidates.

Job Orders represent active or archived job postings with status, description, requirements, and assigned consultants. We map Job Order statuses to the destination pipeline stages and preserve the job-board posting history linked to each Job.

Client records hold company details, contacts, and the business development pipeline association. We migrate Client records with their primary contact and preserve any Client Portal associations that will need to be re-established in the destination system.

Contact records on the client side are distinct from Candidate records. We migrate all Contact fields including email, phone, role, and the owning consultant. Where contacts share an email with a candidate record, we flag the overlap during scoping.

Placements are the placed candidate records tied to a Job and Client, often carrying bill rate, pay rate, and start/end dates. We preserve all placement details and link them to their corresponding Candidate and Job. Temp placements include additional billing fields that require field-level mapping to the destination schema.

Opportunities represent the business development pipeline for new client work. JobAdder's Opportunity Pipeline is a distinct object managing BD activity. We migrate Opportunity records including status, estimated value, and stage — but the Opportunity-to-Job linkage requires explicit mapping as naming conventions vary by implementation.

JobAdder's job board integrations (Indeed, SEEK, Reed, and 200+ others) are managed as posting configurations rather than standalone objects. The posting history attached to a Job Order is preserved as a text log, but the integrations themselves cannot be migrated — they must be reconfigured in the destination ATS.

JobAdder supports custom fields on Candidates, Jobs, and Clients. Custom field schemas vary by tenant. We discover the full custom field list during discovery and generate field-level mappings; any custom field that has no destination equivalent is flagged as a manual-review item.

User accounts (consultants/recruiters) are migrated as inactive placeholder records to preserve assignment history, rather than as active user accounts. Active user provisioning must be handled separately in the destination system.

Task records linked to Candidates, Jobs, or Clients are migrated with their due dates, statuses, and assignees. Completed tasks carry a historical record; open tasks are migrated as open. We flag any task templates that reference JobAdder-specific automation rules.

File attachments on Candidate profiles (CVs, cover letters, certifications) are migrated as binary blobs associated with the Candidate record. We preserve original filenames and MIME types. Attachments stored in external integrations (e.g., LinkedIn Recruiter) are not available for export.

Tags applied to Candidates and Jobs are migrated as flat label arrays. The semantic meaning of tags (e.g., sourcing channel, vetting status) is preserved but the tag taxonomy must be recreated in the destination system.

The Client Portal stores submission history and interview feedback tied to the portal view. This activity log is not exported via standard JobAdder data exports. We migrate the underlying Submission records but not the portal-visible feedback thread, which must be manually captured or reconstructed.

Temp placements carry bill rate, pay rate, timesheet periods, and invoice references. These billing fields require explicit mapping because JobAdder's temp workflow fields do not map 1:1 to most destination ATS platforms. We include all fields but flag which require destination-side configuration.