Migrate from ApplicantStack to Recruit CRM & ATS

ApplicantStack Positions map to Recruit CRM Jobs. The job title, description, status, and opening count migrate directly. ApplicantStack's job board distribution settings (Indeed sponsored, JobTarget, custom branded boards) are configuration data that do not export; the job posting content migrates as rich-text fields, but the distribution channels must be reconfigured manually in Recruit CRM's job board settings. Custom employer-defined properties on the Position become Recruit CRM custom fields on the Job record.

ApplicantStack Candidate records map to Recruit CRM Candidates with a first-pass deduplication pass before import. ApplicantStack's duplicate detection is unreliable and consistently misses candidates who applied under different email addresses or slight name variations (G2, Capterra Cons filter). We run matching on email address, phone number, and normalized name strings, flagging likely duplicates for customer review before final import. Resume files and cover letters migrate as document attachments linked to the Candidate record in Recruit CRM.

ApplicantStack Questionnaires store responses as field-value pairs tied to the Candidate record. We extract every custom field response and map them to Recruit CRM custom fields on the Candidate object, pre-creating the destination fields during the schema phase. If ApplicantStack uses a custom form that Recruit CRM cannot natively represent as a single record field (e.g., repeating sections or conditional logic), we flatten the response data into the most granular available field structure and document the mapping for customer review.

ApplicantStack's configurable pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) migrate as Recruit CRM stage definitions. We replay each Candidate's stage history against the corresponding Recruit CRM stage so that the Kanban pipeline reflects the candidate's original progression. If ApplicantStack uses custom stage names beyond the standard set, we create custom stage values in Recruit CRM during the schema phase before any candidate data loads.

ApplicantStack user roles (Administrator, Recruiter, Hiring Manager) map to Recruit CRM user roles. We extract all active user accounts from ApplicantStack and match by email against Recruit CRM user provisioning. Note that ApplicantStack counts Administrators as Recruiters for billing purposes, so a customer paying for 3 Starter users may have fewer actual logins than the account suggests. We verify the active user count during discovery to avoid under-provisioning in Recruit CRM. Any ApplicantStack Hiring Manager without a Recruit CRM user account is held in a provisioning queue for the customer's admin to address.

When ApplicantStack Onboard is in scope, new hire records including I-9 data, tax form status, and custom onboarding document uploads migrate as Candidate records in Recruit CRM with custom fields capturing onboarding status and a separate document attachment set. The onboarding portal URL and document blob are preserved as structured data. Note that ApplicantStack Onboard can be purchased as a standalone SKU, so we confirm which module is active during discovery to calibrate scope; accounts using only Onboard without Recruit may have minimal candidate records beyond new hire entries.

ApplicantStack candidate tags and job labels export as flat tag arrays. We preserve all tags and apply them as Tag records in Recruit CRM linked to the corresponding Candidate or Job. Tag merge logic handles cases where identical tags appear under slightly different casing or spacing in ApplicantStack, consolidating them into a single Recruit CRM tag.

ApplicantStack email template content migrates to Recruit CRM Email Templates with variable placeholders mapped to Recruit CRM's template syntax. Automated trigger logic does not migrate because ApplicantStack's email automation sequences are not accessible as structured data through the CSV export. We deliver a written inventory of every email template with its trigger conditions and a recommendation for Recruit CRM's automation equivalent.

ApplicantStack's job board distribution settings (Indeed sponsored job configuration, JobTarget integration, custom branded board credentials) are connection-level configuration that do not export. The job posting content migrates; the distribution channel configuration must be recreated manually in Recruit CRM's job board settings page. We document the full list of active board integrations from ApplicantStack for the customer's admin to reconfigure.

ApplicantStack workflows and automated sequences do not migrate as code. ApplicantStack's automation capabilities are scoped differently from Recruit CRM's Kanban-based pipeline triggers and workflow automations, making a direct translation impossible. We deliver a written inventory of every active ApplicantStack workflow, email sequence, and automation trigger with its conditions, actions, and a recommended Recruit CRM equivalent for the customer's admin to rebuild.