Migrate from JobAdder to Crelate

JobAdder Candidates map to Crelate Contacts. The central profile fields (name, email, phone, skills, work history) map directly. We preserve the JobAdder candidate status, sourcing channel tags, and any rating as custom fields on the Crelate Contact. Where Candidates share an email with existing Crelate records, we apply email-based deduplication during scoping. JobAdder custom fields on Candidates map to Crelate Contact custom fields created in Settings/Core Records before migration.

JobAdder Job Orders map to Crelate Jobs with status, description, requirements, and assigned consultant preserved. JobAdder's internal workflow stages map to Crelate Job stages. We transfer the posting history attached to each Job Order as a text array noting board and date; the live job board posting configuration must be rebuilt in Crelate's job distribution settings post-migration.

JobAdder Client records map to Crelate Companies. Company details, industry, website, and address fields transfer directly. The primary Contact on the JobAdder Client becomes the primary Contact on the Crelate Company record. Client Portal associations are noted in a custom field for manual reconfiguration in Crelate's Client Portal settings.

JobAdder Contact records on the client side (distinct from Candidate records) map to Crelate Contacts. We preserve email, phone, role, and the owning consultant. If a Contact shares an email with a migrated Candidate record, we flag the duplicate for the customer's review before inserting.

JobAdder Placements (placed candidate tied to a Job and Client) map to Crelate Placements with start date, end date, and status preserved. Temp and contract placements carry bill rate, pay rate, markup percentage, and timesheet period fields that do not map 1:1 to Crelate's standard schema. We create custom fields on the Placement record in Crelate to carry these billing values and document every temp billing field in the field map.

JobAdder's Opportunity Pipeline (business development activity object) maps to Crelate Opportunities. We transfer Opportunity name, stage, estimated value, expected close date, and owning consultant. JobAdder's BD stage statuses map to Crelate Opportunity stages. If the customer uses multiple Opportunity pipelines in JobAdder, we create corresponding Crelate Opportunity categories.

JobAdder custom field schemas vary by tenant and must be discovered during scoping. We request a full read-only test export from the customer to enumerate the complete custom field list. Each discovered custom field is created in Crelate with a matching logical name for API use, and the field type is mapped from JobAdder to the nearest Crelate equivalent (text, number, date, picklist). The customer's admin approves the custom field list before migration begins.

JobAdder User accounts (consultants/recruiters) are migrated as inactive Crelate User records to preserve assignment history on Candidates, Jobs, and Placements. Active user provisioning happens separately in Crelate's user management settings. We map by email match and flag any JobAdder user without a corresponding Crelate User for the customer's admin to provision before record import.

Task records linked to Candidates, Jobs, or Clients migrate to Crelate Tasks with due dates, statuses, assignees, and body preserved. Completed tasks carry a historical record; open tasks migrate as open. We resolve the Task assignee by email match against the Crelate User table. Tasks without a resolved assignee go to a reconciliation queue.

File attachments on Candidate profiles (CVs, cover letters, certifications) migrate as binary blobs associated with the Crelate Contact record. Original filenames and MIME types are preserved. Attachment migration is processed after the parent Contact record is inserted to satisfy the record linkage. File size limits in Crelate are checked during scoping and oversized attachments are flagged for manual handling.

Tags applied to Candidates and Jobs in JobAdder migrate as flat label arrays preserved in a custom field on the Crelate Contact or Job record. The semantic meaning of tags (sourcing channel, vetting status, client tier) is preserved in the data but the tag taxonomy must be recreated in Crelate's labeling system. The customer chooses during scoping whether tags migrate as a single multi-value text field or as discrete custom picklist values.

Temp placements in JobAdder carry bill rate, pay rate, timesheet period, and invoice reference fields. These require explicit mapping because Crelate does not have a native temp/contract billing module. We create custom fields on the Crelate Placement object for each billing attribute and preserve the values during placement migration. The customer is responsible for configuring Crelate's billing display settings if they intend to use the placement data for temp payroll downstream.