Migrate from CareerBuilder Applicant Tracking to Crelate

CareerBuilder Jobs map directly to Crelate Jobs. Each Job holds title, description, department, location, and pipeline stage assignments. We preserve the job opening date and any internal job ID from CareerBuilder as a custom field for cross-reference. Jobs without active pipeline stages are migrated as draft jobs in Crelate with the original stage configuration noted for your admin to complete. Positions flagged near the 10-13 applicant cap are documented separately with the original cap status so your team can decide whether to reopen sourcing in Crelate.

CareerBuilder Candidates migrate to Crelate Contacts. We preserve all standard fields (name, email, phone, address, source attribution) and flag records where the resume date is older than 18 months as stale for your review before inclusion. Candidates that were sourced from CareerBuilder's resume database are tagged with the original source field preserved as a Crelate tag. The candidate's profile completeness score (if available) maps to Crelate's contact quality indicators.

CareerBuilder Applications link Candidates to Jobs with status, submission date, and routing history through pipeline stages. These map to Crelate Applications with the Contact and Job lookups resolved at migration time. Application status from CareerBuilder maps to Crelate's Application status values based on a stage mapping table we build during scoping. Rejection reasons and withdrawal reasons migrate as application notes.

CareerBuilder talent pools (talent network members) are distinct from active job applications. We map these to Crelate Talent Pools preserving the original pool name as the Crelate pool name. Candidates in multiple CareerBuilder talent pools are added to corresponding Crelate Talent Pools with their membership date preserved. Pool-level tags (skills, source campaign, engagement status) migrate as Crelate tags on the Contact record.

CareerBuilder's configurable pipeline stages (Applied, Screening, Interview, Offer, etc.) vary by customer configuration and job type. We extract the full pipeline schema from CareerBuilder during scoping and map each stage to a Crelate Pipeline Stage. Stage names and order are preserved; stage probability percentages (if configured in CareerBuilder) map to Crelate stage weights. If CareerBuilder has per-job pipeline overrides, we document them as Crelate pipeline-specific stage configurations for your admin to apply post-migration.

Recruiter-assigned numeric ratings and structured scorecards from CareerBuilder migrate as custom numeric fields on the Crelate Contact record. We create the destination custom fields during schema setup, mapping each CareerBuilder rating category to a named Crelate field. Scorecard values from structured evaluations migrate to a Crelate custom form with field mappings configured per Crelate's field mapping documentation.

Email threads and recruiter notes attached to candidates migrate as Crelate Activities. Email activities map to Crelate Email activity type with sender, timestamp, and body text preserved. Recruiter notes migrate as Crelate Note activities with the note author and creation date. Attachment filenames are mapped but full binary files require Crelate's document storage configuration; we flag any attachments exceeding Crelate's file size limits for manual handling.

Resumes are stored as binary attachments per candidate in CareerBuilder. We extract resume files and attach them to the corresponding Crelate Contact record during migration. Large volumes of resume files are chunked for reliable transfer. Crelate's AI resume parser can re-parse uploaded resumes after migration to populate structured contact fields automatically; we recommend triggering a re-parse on migrated contacts to take advantage of Crelate's enrichment capabilities rather than relying on legacy CareerBuilder-parsed data.

Some CareerBuilder customers configure custom fields on candidate profiles, particularly those with Luceo-era configurations. We extract all custom field definitions and values, then create equivalent custom fields in Crelate. Field types are mapped (text to text, numeric to number, date to date, picklist to picklist) and validated against Crelate's supported field types. Fields with no Crelate equivalent are documented as requiring manual entry or a custom field workaround post-migration.

Recruiter and hiring manager user accounts from CareerBuilder are mapped to Crelate Users by email match. Owner assignments on candidates and jobs translate to Crelate User assignments on the Contact and Job. Permissions structures vary between platforms and we do not migrate role hierarchies; we deliver a user assignment map documenting the original CareerBuilder owner for each record and recommend your Crelate admin configure permissions post-migration based on the documented assignments.

CareerBuilder's job board distribution logs (which boards received each job, posting dates, spend per board) are not exposed in any customer export. This data is not migratable. We document the existence of this reporting and recommend capturing it manually before the migration cutover date if historical ROI analysis by board is required.

CareerBuilder's reporting data (time-to-fill, source effectiveness, recruiter performance) is calculated dynamically from live data and not stored as exportable objects. Historical reports cannot be migrated. We deliver a written inventory of all CareerBuilder reports the customer actively uses so that equivalent Crelate reports or dashboard configurations can be built post-migration.