Migrate from Jobtrain to Recruit CRM & ATS

Jobtrain Vacancy records map to Recruit CRM Job records. We map vacancy title, reference number, job grade, department, cost centre, and advert sources. Jobtrain's vacancy status (active, on hold, filled, cancelled) maps to Recruit CRM's job status. Custom vacancy fields discovered during scoping map to Recruit CRM custom fields or become tagged properties on the Job record. Vacancies must import before Candidates and Applications because these are parent records that the candidate-job association requires at insert time.

Jobtrain Candidate profiles map to Recruit CRM Candidate records. We map contact details (name, email, phone, address), source attribution, and application history. The candidate unique identifier from Jobtrain is preserved as a custom field jt_candidate_id__c for reconciliation. Any custom candidate fields discovered in the Jobtrain schema map to Recruit CRM custom fields. Candidates import after Vacancies so that application associations can resolve at insert time.

Jobtrain Application records link a Candidate to a Vacancy at a specific stage. We map application date, current stage, stage history, and any application-specific notes. The Jobtrain application status maps to the equivalent Recruit CRM stage value. Applications import after both parent Vacancy and Candidate records are staged and validated. Stage history migrates as a JSON property or as a series of status-change entries on the application record.

Jobtrain vacancy templates define reusable vacancy structures including fields, approval routes, and advert content. Recruit CRM does not have a native template-of-templates feature; we map template content into the equivalent Recruit CRM job fields at import time rather than preserving a template object. Template-to-job apply is documented as a manual configuration step for the customer's Recruit CRM admin.

Jobtrain allows clients to define custom job grade and level hierarchies (e.g., Grade 5, Grade 6, Senior). We map grade names as a picklist or text custom field on the Recruit CRM Job record depending on what Recruit CRM supports at the customer's tier. If Recruit CRM does not support a dedicated grade field, grade information attaches as a tagged property on the Job.

Jobtrain Departments map to Recruit CRM Departments. We map department names and IDs and attach them to migrated Vacancy records. Department is a required reference on Vacancy in Jobtrain; we resolve the department lookup at import time by creating Departments first, then Vacancies. If Recruit CRM uses a different department hierarchy model (e.g., flat list versus nested tree), we flatten or restructure the topology accordingly.

Jobtrain Cost Centres are defined in platform settings and attached to Vacancies for budget tracking. Recruit CRM does not have a native Cost Centre object; we map cost centre codes and names to a custom text field on the Recruit CRM Job record. The customer configures this custom field during Recruit CRM setup before migration begins.

Jobtrain approval routes are configurable per vacancy or globally, with unlimited routing rules. These are not transferable as data objects because the routing logic is stored as workflow configuration, not as a record. We document the approval chain topology during scoping (approver names, route order, conditions) and deliver a written workflow reconstruction guide for the customer's Recruit CRM admin to rebuild in Recruit CRM's workflow settings. Approver email addresses are captured for manual re-provisioning.

Jobtrain stores email and letter templates used at specific recruitment stages. We export template content as structured text data and deliver a written template inventory with stage tagging so the customer's Recruit CRM admin can recreate them in Recruit CRM's email template editor. Template merge fields are mapped to Recruit CRM equivalent tokens where possible.

Jobtrain records advert sources including origin channels and associated costs for reporting. We map source names and attributions. Recruit CRM's candidate record includes a source field; we map Jobtrain advert source names to the Recruit CRM candidate source values. Any additional cost-tracking fields become custom fields on the Candidate or Job record.

Jobtrain allows super-users to create custom fields across vacancy, candidate, and application objects. Every Jobtrain installation has a unique custom field set. We discover the full custom field schema during scoping, map each to a Recruit CRM custom field of equivalent type (text, number, date, picklist, checkbox), and pre-create the destination schema before migration begins. Without this step, custom data would be lost or misaligned at the destination.

Attachments on vacancies, candidates, and applications in Jobtrain (CVs, cover letters, interview notes) are exported as files and associated with the corresponding Candidate record in Recruit CRM. We export from the Jobtrain interface, maintain the original filename, and upload to Recruit CRM's file storage attached to the correct record. File metadata (upload date, file type, size) migrates where available.