Migrate from Nextal to Recruit CRM & ATS

Nextal Job postings map to Recruit CRM Job Orders. We extract Job records including title, description, department, location, status, and any multilingual content variants. Each Nextal Job may have multilingual content tied to its Career Portal page; we preserve all language variants in Recruit CRM's job description fields and set the locale metadata. Job Order status (Active, Paused, Closed) maps directly to Recruit CRM's job status values.

Nextal Candidate profiles map to Recruit CRM Candidate records. We extract name, email address, phone, location, source attribution (LinkedIn, Indeed, direct application), and resume attachments. Source attribution from Nextal migrates as a custom field in Recruit CRM since the sourcing attribution model differs slightly between platforms. Any Nextal Candidate without a valid email address is flagged in the reconciliation report for the customer's review before load.

Nextal Applications link Candidates to Jobs and carry stage history. We map Applications to Recruit CRM Applications with CandidateId and JobOrderId resolved at migration time. The Kanban stage assignment from Nextal is preserved by mapping the stage name to the corresponding Recruit CRM pipeline stage via the customer-reviewed stage mapping table. Stage history timestamps migrate as custom fields where the target schema supports them.

Nextal uses a Kanban-style pipeline with configurable stage names that vary per organization. We build a stage mapping table that pairs each Nextal stage name with the equivalent Recruit CRM pipeline stage, reviewed and approved by the customer's admin before migration. Stage ordering is preserved based on the position index from Nextal. Recruit CRM pipeline stages are pre-created or mapped to existing stages during the schema setup phase.

Nextal User accounts (recruiters, hiring managers, admins) migrate to Recruit CRM User records with names, email addresses, and role assignments. We resolve users by email match against Recruit CRM. Any Nextal User without a matching Recruit CRM account is held in a reconciliation queue; the customer's admin provisions missing users before record import resumes. Passwords do not transfer; users receive Recruit CRM setup emails upon first login.

Nextal's per-organization custom fields on Jobs, Candidates, and Applications require field-level mapping. We extract the Nextal field schema (label, data type, object association) and match each to a Recruit CRM custom field of equivalent type (text, number, date, dropdown, checkbox). Any Nextal custom field without a matching Recruit CRM field is pre-created in Recruit CRM before data load. The customer reviews and approves the custom field mapping table during scoping.

Resume and document attachments on Nextal Candidate records migrate as downloadable files linked to the corresponding Recruit CRM Candidate record. We preserve the original file format (PDF, DOCX) and file name. Large attachments (over 10 MB) are flagged for manual review. Recruit CRM's file storage limits are checked during scoping against total attachment volume.

Nextal stores multilingual email templates tied to job stages. We extract templates as HTML blobs with their language variants and import them as email templates in Recruit CRM, preserving the HTML structure and language tag metadata. Stage-specific template associations are noted in the handoff document for manual reassignment in Recruit CRM's template editor.

Nextal department assignments on Jobs map to Recruit CRM Departments or Teams. We extract distinct department values from Job records, map them to existing Recruit CRM department structures, and create any missing departments before Job import. Department mapping is reviewed by the customer during scoping.

Nextal tracks candidate source (LinkedIn, Indeed, direct application, referral). We map these to Recruit CRM's Source field on Candidate records. Any Nextal source value without a direct Recruit CRM equivalent is mapped to a custom Source value created during schema setup.