Migrate from Applicant Starter to Recruit CRM & ATS

Applicant Starter Candidate records (name, email, phone, resume URL, stage, source, tags) map directly to Recruit CRM Candidate records. We extract every standard field and any custom candidate-level fields identified during scoping. The candidate's original Applicant Starter record ID is preserved as a reference field for audit purposes. Resume files are downloaded as binary blobs, renamed to a consistent convention (LastName_FirstName_CandidateID.pdf), and reattached to the candidate record in Recruit CRM via the platform's attachment API.

Applicant Starter Job records map to Recruit CRM Jobs. We preserve the original job title, department, hiring manager (mapped to the Recruit CRM User lookup by email), open/closed status, and job description. The original Applicant Starter job ID is retained as a reference field. Job Requisition is created before Candidate import so that any application-to-job association resolves at migration time.

Application records link a Candidate to a Job Requisition with a stage value and a timestamp. We map the application record to Recruit CRM's Application object, preserving the stage history and application date. If Applicant Starter stores multiple applications per candidate, each application migrates as a separate record in Recruit CRM tied to the corresponding Job.

Applicant Starter pipeline stages are user-defined and vary per account. One account might use Applied/Screening/Interview; another might use Open/Qualified/Closed. We extract the full stage schema during scoping and map each to a Recruit CRM stage or create a new stage in Recruit CRM if no equivalent exists. Stage sequence order is preserved in Recruit CRM's pipeline configuration. Any stage with no Recruit CRM equivalent is flagged for the customer to resolve before migration begins.

Applicant Starter tags are user-defined and used inconsistently across accounts. We extract the full tag taxonomy during scoping and map tags to Recruit CRM tags. Where tags represent evaluation criteria or skill keywords, we evaluate whether they map better to Recruit CRM's skills field or remain as tags. The customer confirms the tag strategy during scoping.

Applicant Starter activity logs (email content, call summaries, notes) migrate to Recruit CRM's activity timeline on the corresponding Candidate record. We reconstruct the activity stream by linking each entry to the candidate and setting the timestamp from the original Applicant Starter activity date. Older activities may lack precise timestamps; we flag these and set them to the nearest available date or the candidate creation date as a fallback.

Resume files and binary attachments download from Applicant Starter, are renamed to a consistent convention (LastName_FirstName_CandidateID_Resume.pdf), and reattached to the corresponding Candidate record in Recruit CRM. We verify that each attachment maps to the correct candidate record using the candidate's email address or Applicant Starter record ID as the dedupe key. Any attachment without a resolvable candidate is held in a reconciliation queue.

Custom fields on Candidate or Job records require explicit mapping. We extract the full field schema during scoping, including field type, picklist values, and whether the field is required. Each custom field is matched to an equivalent Recruit CRM custom field or created as a new custom field in Recruit CRM before migration. Field type mismatches (e.g., Applicant Starter stores a date as text) are resolved during the transform step with the customer's confirmation.

Scorecard data in Applicant Starter is stored in a proprietary format not accessible via the export API. We notify customers before migration begins and advise a manual export. Scorecards do not migrate as part of our standard scope. The customer's admin can recreate scorecard templates in Recruit CRM's evaluation tools post-migration.

Applicant Starter records where a job was posted (LinkedIn, Indeed, etc.) in job distribution logs. This data exists but is inconsistently recorded across accounts. We export available distribution records and map them to a Recruit CRM custom field on the Job record (e.g., job_distribution_channels__c) as a comma-separated list or multi-select field if Recruit CRM's schema supports it. Distribution data is migrated on a best-effort basis; the customer is advised to verify distribution settings in Recruit CRM after migration.