Migrate from Jobtoolz to Recruit CRM & ATS

Jobtoolz Candidates map directly to Recruit CRM Candidate records. We export the candidate list via Jobtoolz's built-in CSV download from the Candidates list view, chunking exports by date range or pipeline stage for databases exceeding 2,000 records. Each row maps to a Recruit CRM Candidate with fields including name, email, phone, current role, location, and source. Custom candidate fields from Jobtoolz are preserved as typed custom properties in Recruit CRM, with any date-format mismatches corrected during the transform step.

Jobtoolz Application records link a Candidate to a Vacancy and store the full stage history. We map the Application status to Recruit CRM's candidate pipeline stage field, noting that Jobtoolz stages are tenant-defined and may exceed Recruit CRM's named stage categories. Stage history timestamps migrate as custom date fields on the Candidate record if the destination supports them, or are preserved in a notes field for manual entry by the recruiter.

Jobtoolz Vacancy objects map to Recruit CRM Job records. Fields mapped include job title, department, location, employment type, job description, and salary range. Custom vacancy fields migrate as custom properties on the Recruit CRM Job object. The Vacancy status (active, paused, closed) maps to Recruit CRM's job status field with direct value transfer.

Jobtoolz allows arbitrary custom stage names and counts per pipeline. Recruit CRM uses a named stage model per pipeline with configurable stage values. We capture the full custom stage sequence during scoping, generate a stage mapping table that collapses Jobtoolz stages into the nearest Recruit CRM stage equivalent, and submit this table for customer approval before migration. Stages that cannot map directly are merged into a single catch-all stage with a note field capturing the original stage name.

Jobtoolz custom fields on candidate records are exported as additional columns in the candidate CSV. We recreate each custom field as a typed custom property in Recruit CRM (text, number, date, or picklist depending on the detected format), populate the values during candidate import, and flag any type mismatches for manual correction. Fields that exist in Jobtoolz but have no Recruit CRM equivalent are added as text custom properties.

Resume and cover letter attachments associated with Jobtoolz candidates are downloaded from the authenticated Jobtoolz session and reattached to the corresponding Candidate record in Recruit CRM. We process attachments in batches of 50 to avoid session timeouts, verify file integrity via MD5 checksum against the source, and re-upload to Recruit CRM using the candidate attachment API endpoint. Files exceeding Recruit CRM's attachment size limit are flagged for the customer to re-upload manually.

Jobtoolz's employer branding assets, career site content, and job ad templates are accessible via the authenticated Content API with Bearer token authentication. We export this content as structured JSON including company logo, brand colors, careers page copy, and job posting templates, then import it into Recruit CRM's careers page builder and branding settings. Job ad templates map to Recruit CRM's job description templates.

Jobtoolz team member accounts are mapped to Recruit CRM User records. Role and permission structures differ between platforms; we assign default recruiter roles in Recruit CRM and flag any accounts with elevated permissions (admin, billing) for the customer's admin to configure post-migration. Active status migrates directly; inactive accounts in Jobtoolz are recreated as inactive in Recruit CRM pending the admin's decision.

Jobtoolz tracks candidate sourcing channels (LinkedIn, referral, job board, direct application). Source data is stored as a field on the Candidate record and migrates to Recruit CRM's source field with direct value transfer. If the source value does not exist in Recruit CRM's picklist, we add it as a new source option during setup.

If Jobtoolz stores client or customer organization records separate from vacancies (some SME configurations track this), we map them to Recruit CRM Client records. Client name, contact person, industry, and notes migrate as fields. Address and billing information migrates to the Client's address fields or custom properties as applicable.